Projects
![]()
No projects found
Investors
New
DAO Treasuries
DATs
Lend / Borrow APRs
Chains
Categories
Spaces
PDP Is Live: Unlocking Filecoin’s Hot Storage Era!
Recorded: June 18, 2025 Duration: 0:46:12Space Recording
Short Summary
The recent launch of the Proof of Data Possession (PDP) protocol by the Filecoin team introduces a revolutionary approach to data storage, enhancing accessibility and usability for developers. With the integration of on-chain payments through the Pandora service, Filecoin is positioning itself as a competitive player in the decentralized storage market, aiming to bridge the gap with traditional services.
Full Transcription
Music Thank you. Thank you. Hey everybody, we'll just wait a few moments for everybody to filter in and then we'll
get started.
Okay, let's get going. Hi everybody, I'm James from the PhilOz team and today we are going
to be talking about PDP or Proof of Data Possession which is now live. What is PDP? Well, it introduces
verifiable hot storage to Farcoin, enabling fast, secure and on-demand data access without unsealing.
It's not replacing cold storage, but it is adding a powerful new storage primitive that
opens up new possibilities for builders and users.
And we're joined today by a load of people who have implemented PDP and have been crucial
in the creation of this new service from the Philo's team.
We have Sen and Arsh. We also have developers here today with us from PhilCDN and from PhilB.
And so we'll start with the main question. First of all, what actually is PDP and why does it matter?
And I'm going to hand, hand this one to Zen Grand.
Zen, are you there?
Are you able to speak at the moment?
So I can actually speak. I just got, I just sent a request for speaker and I can talk.
Good man.
Sorry, I think I cut out on my audio a little bit there before this, so I didn't quite hear what you said.
But just like a tiny bit about me, I was involved with implementing PDP for the last several months. And thanks to our efforts, it's now on mainnet.
It's also a test protocol on Calibnet.
I'm happy to talk about it today.
I know we're going to get into the details and some of the implications.
So, yeah, I'm excited to share what we have and how we think it could be useful
for people that want to build protocols and products in the Web3 space.
Thanks, and starting off with basics, how would you describe or explain PDP in simple terms?
Yeah, great. So in simple terms, PDP is a new Filecoin protocol and a new product.
And the basic idea is Filecoin type storage made easy for usability.
The biggest difference is that you can get data in and out very quickly.
in and out very quickly.
And the same sort of motivation applies to PDP data storage
as to the base file point power up storage,
which is that the data is verifiable
with on-chain integrated proof that can verify
that the data is in fact being stored.
And then the other side is that it can be programmable
by a smart contract which can hold
a reference to the data and do things like incentivize the storage uh yeah and things like
that so it's it's web3 native storage but this time it is not as difficult to use because there
aren't very high latency requirements because it's not it's not being incentivized by the base
of the block reward, which is what brings that high latency requirement. I guess the other thing
is that it's because we have this flexibility, there are these first, these native or first-class
native or first class primitives for deletion and adding small data. So it really looks a lot
more like what developers would like to see or are more used to from a Web 2 context.
That's amazing. So with my other hat on, I'm also a provider i have i have been since the launch of uh filecoin
um so i'm used to power up i'm used to to lots of gpus um lots of long unsealing and ceiling jobs
um this sounds like it's a completely different thing altogether so from from uh if i wanted to
start off or if i was just starting out as an sp my hardware requirements would be considerably less
is that what you're saying yeah so, so they would be a lot less.
So you don't need any GPUs.
The proofs are simpler.
You can just use a regular CPU.
The biggest requirement is just having enough disks to store the data.
So this is the sort of thing which you could actually do with like really small consumer hardware as an SP.
actually do with like really small consumer hardware as an SP.
I'm not sure if you'd want to, but a lot of SPs with good file point setups would be like well over provisions.
You need enough to run, you need enough like hardware to run a storage node, which like the memory and CPU requirements are small.
It's like the sort of thing you can run on a laptop without any trouble.
And then there's no, again, there's no GPU requirements for proving.
So, yeah, the big thing is just having enough space to store as much data as you want to.
Excellent. Awesome. Thank you.
I've actually installed PDP, and I'm running now taking part in tests.
And I'm using Curio.
So the software is pretty much the same for an SP who's running PoRep.
They can basically also run PDP alongside that. Is that true?
Yeah. So there are actually are a few implementations of a storage node out there. So Sriracha has recently gotten a open source,
a Sriracha native PVP storage node,
like storage backend software out in the wild.
So that's, it's cool to see
like people are developing for the protocol,
but Kirio is the like reference implementation
where the,
that's what we've been building on to make sure that things work when launching the protocol to mainnet. And yeah, to like,
if you're running Curio to do PoRev stuff,
it is a pretty trivial matter to configure your software to
also accept data for PDP,
interact with the PDP protocol on chain and submit proofs,
serve retrievals, all that stuff is built right into Curio. So you don't have any extra software
requirements there. Awesome. Thank you, Zen. Ash, I see you're on the line as well. Now you've been
creating a lot of demos. You've been working with PDP a great deal. I'm very interested to know your opinion on PDP in simple terms and what do you think about the future?
I think it's a lot.
Yeah, one thing I'm seeing is that Arsh is still a listener.
And I don't know if he's requested.
If you can request by just tapping the microphone to become a speaker.
And then I think you might have to add him as a speaker, Tippi.
I think we have him now.
There we are.
We have our Oshka.
Go ahead, Oshka.
Thanks, Zen.
Yeah, sorry.
I was just requesting, hey, everyone.
I'm Oshka.
I'm an engineer with Philoze.
I've done some work on PDP with Zen.
In my experience, PDP is much more lightweight than Porep
in terms of getting your data onboarded to an SP
because the proving cost and the hardware that SPs need to prove it
is lightweight compared to what you need for Porep.
So it's very good for hot storage applications where you need to get your data onboarded quickly.
There's no unsealing involved like Porep. So
retrievals can be much faster. Porep has like 32 gig sectors, whereas for PDP, I mean, there are
some limitations in how small your data can be for it to be economically viable for SPs, but it's not
that much, which means that you can store much smaller files with PDP and get them proven on chain compared to what you need for Porep.
So in my mind, it's like Porep Lite or Filecoin Lite.
Both Porep and PDP have their use cases and applications.
cases and applications, choose what works for you.
Choose what works for you.
But PDP does unlock a whole host of applications
related to, you know, hot storage, quick retrieval,
smaller file sizes.
You can have SPs running it for cheaper compared to poor app.
So it has a lot going for it.
Amazing. That's a really exciting summary. Thank you.
So let's move on to another question. How PDP improves Firecoin and who benefits? And I'm going to ask Tim to speak here. I'm really excited to introduce Tim. For those of you who haven't met him, he's recently joined PhilOz as a product lead and he's got off to a flying start.
start. So Tim, question to you in the context of how PDP improves file quality benefits,
how would you say PDP closes the gap with traditional storage services?
We can hear you, buddy. We can hear you. Oh, great. Hi, everyone. Thanks for the intro.
We're excited to join here. And one of the things that's exciting has been talking to hearing interesting ideas. And the biggest comparison is often, well, how does this compare to S3, the number of conversations I have?
through some of those ingit samples.
So I talked with a D-Pin company that wanted to store the data
that was being collected through decentralized set of users.
And one of the things that came up was, hey, they were using S3.
And as I walked them through the feature set and what they needed to do,
one idea which I proposed to them was these data sets is their source of revenue.
But if they wanted to enable
their users to say, set those revenue streams as collateral so that they could borrow more
to buy more of these devices, which was collecting the data, they needed something that had more
of the financial and crypto economic security that's not possible with an S3.
And so this was unlocking a way for them to operate in a very Web3 native way
with all the data that was being collected since they were financializing the data.
I can give another example of something I was talking with a developer,
and he was very excited about the idea of how do I use my AI agents,
which were crypto enabled agents, for them to have memory and to have that memory uniquely
associated with that agent, whoever that agent is.
And so having something that's not an S3, but something that's sovereign to the agent
or was something that was really important to them,
and that was something that was a new use case.
The third one was talking about if they wanted to have a way to have signed documents that were exchanged,
very similar to how it was in DocuSign, but they didn't want either party to be able to rug the copy of what the document was for legal reasons,
then by having it in PDP and it was decentralized, but they could share ownership,
was a design space that got them really excited about so that it wouldn't be locked out of access to those documents in the future
by either the other party or by the application themselves.
So those are three, and there's a bunch more.
I don't want to take up more time from that, but it really is allowing people to think
about, well, if I have this data, who has ownership of it?
How is this being used, especially in a financial situation or where I don't want to be beholden
to something?
I need to have proof that it's mine
and have sovereign access to it.
So those are three that have gotten me really excited,
and that's just been for this week.
Just for this week, that's an awesome summary.
Thank you very much.
So you mentioned developers,
and I know you guys have been working really, really hard
on the back-end developer
tools. And we've been seeing things, I've been seeing chats about things like Synapse and Pandora,
which are very cool names. But I just want to, maybe any of you guys, so Tim, Arsh, or ZenGran,
what's the story behind these new services? Where are we with them? Who can use them?
And how can people access them?
I can take it on the high level, what the developer experience was, and then the others
can go into what's going underneath it.
So when talking to developers, what the experience was and being able to interact with the protocol
easier than trying to work directly from sort of
like scratch with the smart contracts was valuable. So having these abstractions where they could
understand these were the operations that were being done for the storage properties, as well
as anything that needs to do with, say, payments, payments, moving along on the payment status, the storage status,
and being able to make that available to the developer
in sort of like an easier taxonomy was actually very valuable.
And that's sort of what I got from the few conversations I had
with developers who are looking at it.
Amazing. Thank you.
Zen and Ash,
we'd be very interested to hear your views on that.
Sure, I can go.
So, yeah, the idea is
we're building this platform called Synapse
and the aim for it is to become an on-chain marketplace for
a whole host of services that leverage Filecoin protocols running on Filecoin and the plethora
of hardware that Filecoin SPs currently have. But as of today, the one service that we're going to launch is called Pandora.
Think of it as, you know, on-chain paid PDP with CDN-grade retrieval.
So you can go to this on-chain service.
You can buy storage from any Filecoin SP that's running the PDP protocol.
You can pay for it completely on-chain using USDFC, which is a Filecoin-backed stablecoin, which is awesome because then you don't need to worry about crypto volatility and fluctuations.
you're paying in dollars and not only that the on-chain payments you know the payment to the
You're paying in dollars.
storage provider is contingent to the storage providers proving your data according to the
pre-agreed SLA and pre-agreed duration so for example if you do a deal where you say I want my
data to be proven by PDP every 24 hours, the SP only gets paid on chain if they actually
submit a verifiable proof every 24 hours and they don't get paid for, you know, durations that they
don't prove. So it's really nice. It's really nice. And you get CDN grade retrievals using
something called PhilCDN, which i won't get too into right
now we can we can talk about it later but yeah this is this is basically the idea is the on-chain
uh you can buy on-chain storage backed by you know hot proofs with pdp and cdn grade retrieval
and the payment is contingent to sps keeping their part of the SLA.
It's amazing. Thank you very much, Ash.
Zen, any extra comments to make on this?
Yeah, I'll just add we're working with SPs to provide a good quality of service,
a good availability on the input and output of data.
And I guess that this is a good example of how you can program PDP storage.
So we can plug in this Pandora contract to accept payments
and only allow paid data to be making its way into the protocol.
And this is like one of many potential ways to program the PDP contract to do things.
It's probably the most useful, obvious way.
So this is what people should probably use who want to just use this as developers and
consumers.
But it's a part of a bigger pattern which kind of gets at the
power of of what you can do if you're a power user with pdp so yeah that's it thank you so
tim question for you i'm kind of sensing the the bigger vision is is maybe filecoin as a full stack
layer a full stack data layer is Is that something you support? Sure.
Yeah.
So if we think about it, the lifecycle, and I'll give you an example of a conversation I just had, of the lifecycle of data.
There is data that is stored, which we're talking about it.
There's data that's archived, which we already have it.
There needs to then be a way to retrieve that data.
There needs to be a way, remember,
we're not location-based, we're content addressed. So how do people find and route that data? And so if you play out those pieces, it's very similar to the way the traditional internet works. When
you go to a website, it needs to look up a server, find that content, and then deliver it. And we're finding
that there might be a use case that is actually crypto native that does depend on those pieces
of the full lifecycle of content. So I'll give you an example of another project that I'm providing
guidance on. And the problem they want to solve is there are lots of content providers.
You can think about it as a magazine or someone who runs a blog or a forum. In this case, we were
looking at specifically the YouTube market, but it could be anything. And a lot of those are being
scraped by AI agents, and no one's really paying for them. And in the crypto world, it is now possible with
existing protocols, not science fiction, but they exist, where those agents can pay with a wallet
to have that particular data ingested. And so here it actually unlocks a way for creators to have
that data, say from YouTube, a transcript, and they point their pointers
to it to like get that pulled out and reverse the process where the consumer actually pays
for retrieval. And using it on the crypto rails is actually probably the only way that's going
to be possible to do because you can't really have an agent have like a credit card. And so I think as we think about the new world
of where does data live, who retrieves it,
who pays for it, who owns it, who has that as an asset,
all of those things require elements of the stack,
which we've all, and we've been touching all of those.
Amazing. Thank you very much. Excellent. So let's move on to a couple of questions
that were asked previously. How does PDP technically work behind the scenes and what makes it
cryptographically sound? That question for Zenground.
Yeah, so it's quite simple compared to ProRep.
So I guess the one thing to remind everyone of, this is like a user space program.
So we're using EVM contracts on the File.01 to do the protocol, to do the management of proofs and of the references of
data. So I guess that's like one thing. So this is all written in Solidity. You can check out
the code on GitHub. It all is pretty comprehensible. The way that it works for guaranteeing proof of storage, so it's like technically a proof of possession.
And basically five Merkle proofs are submitted every day, which are sampled from a randomly generated challenge somewhere in each data set.
So data sets or proof sets are set up between a client and a provider, and the provider initiates these messages.
And each one of these data sets has this proof sampled from it.
It's actually a configurable time depending on how you program it,
but by default, at least say a day is something that makes sense.
So you simply take Merkle inclusion proofs from five random places in your data set, submit them to the chain, and those are validated by the chain.
And over time, this gives you a better and better guarantee that things are actually there.
But yeah, that's really it. It's about as simple as it can get with storage proofs.
It's about as simple as it can get with storage crews.
Thank you, Sam.
It sounds like a heck of a lot of work has been done in a pretty short amount of time, to be honest.
Really impressive stuff.
What do you think comes next?
What's the roadmap for PDP going forward?
Ash, if I could put that question to you first.
Sorry, my audio got cut off for a bit. Can you repeat the question? No problem. Yeah,
I was commenting that a great deal of work has been done in a short period of time. It sounds
like you guys have a lot more planned. I was wondering what the roadmap looked like for PDP
over the next few months. Oh, yeah, of course, of course. I mean, yeah, the team is moving really fast.
So for the next stage,
we're going to be looking at multiple things.
One is we want to integrate down the road,
we want to integrate Porep with PDP.
So if you are a client, you know,
who wants the durability of a protocol like Porep, but also the hot storage features
and the quick retrieval features offered by PDP and PhilCDN. We want to make the UX as easy as
possible for you. So you only need to make a deal once and you get both Porep and PDP out of the box. We're also going to implement
a lot more features to make the payments, on-chain payments experience as seamless as
possible for both clients, you know, who are the ones who are going to pay and for SPs who are
going to be the ones who settle these payments and on after, you know, once the SLEs are met.
So we want to build a payments dApp that makes it easy for clients and SPs to interact with on-chain payments. We're going to build subgraphs of builders.
You know, if you're a builder, you can come in and build your dApps on top of Filecoin Synapse and PDP easily by leveraging these subgraphs.
We're going to bring up explorers for payments.
So it's very easy to introspect on-chain payments happening on Pandora,
which is the PDP service contract that I earlier talked about.
So, I mean, there's a lot more,
but basically a lot of focus is going to happen on like a great UX for SPs and clients and a great DX for builders who want to build dApps on top of PDP using on-chain payments and CDN-grade retrievals.
So, yeah, UX and DX is going to be a big point of focus from here on.
be a big point of focus from here on.
Because building out the protocol is one thing,
making it very easy to build on top of
and to use is what really gets you success.
Thank you, Ash.
Tim, same question to you from your perspective
as a product lead.
I think that what's...
How can I rephrase it?
I think kind of like we talked about the developer experience,
like what Arsh said is opening up these things
and abstracting away some of the challenges. And I think that
that's like addressing the core underlying thing. But I think it's also, the desire is that these
are things that are not disjointed. These are part of a view or a point of view of what to do with the data around sort of this life cycle.
And I think that making that in one place and that makes it interoperable and abstracting
this complexity underneath, but at the same time providing these elements of these different
services, I think that that, I think, is going to be able to allow them to enter a new design space.
So for example, when I talk to the developers,
they're able to put piece together first,
what is it that I want to do that's differentiated and useful,
and they not having to go to multiple places
that can operate within this same set of APIs.
Awesome. Thank you, Tim.
And Zen Graham, same question to you.
Where do you see the roadmap going?
Do you have any different ideas, anything else?
Yeah, so I mean, this is all, I think the previous two ideas are exactly right,
or the previous two ideas are exactly right, or the previous two comments are exactly right.
So the nice thing about PDP is it's basically done as a protocol.
There's not much more to do.
So we do have some basic cleanup stuff
that we want to get in to upgrade the contract.
It's kind of like a protocol upgrade,
but just using the standard ETH upgradable stuff.
So we want to change some basic small things,
like pick some trivial bugs or add some built-in support
for a CompTV2 validation.
So there's some kind of boring maintenance work stuff
that needs to happen in the protocol,
which we haven't talked about yet.
But on top of that, I think the plan with PhilOz
is to start using this
stuff. So there's like a bunch of like, like UX stuff where we could try to can have a
go at trying to make this like you use this protocol to make like an actual service that
works well for people. And there's also the whole integration into PowerUp story, which
fits in with making a service. But it's probably the thing that I'm most excited about,
like having a pipeline from easy access
or easy onboard PDP data into easy to know it's there.
Power App Archive Storage is actually pretty cool.
So I'm looking forward to that.
Yeah, that's about all.
Thank you, Zen.
So PDP is part of the larger overall Firecoin Services project, which we haven't mentioned too much yet.
Ash, can I ask you for your rundown on what Firecoin Services is and how PDP plays a part in that?
Yeah, sure, sure sure sure so filecoin services like i said aims to be it's still early stages
but it aims to be an on-chain marketplace for buying filecoin backed services so people usually
think of filecoin as only a storage network which i I don't think is accurate. Filecoin is a deep-in network backed by, it's a network of data centers, basically,
where you have all these SPs with GPUs and HDDs and HDDs spread across the world with
like provable hardware, you know, when they submit a POREP or a POST, they're proving
or a POST they're proving hardware not just storage so the the aim of Filecoin services
hardware, not just storage.
is to be an on-chain marketplace where people can buy services backed by this provable hardware
that this network of data centers called Filecoin is running so to make it more concrete it could
be storage with PDP or PORAP it could be retrieval that leverages the bandwidth that all these SPs have.
It could be compute that leverages all the GPUs and CPUs
that all the SPs are already running today.
That is how they're proving storage.
And we want this on-chain marketplace to leverage
on-chain Filecoin payments
or Filecoin-backchain filecoin payments or filecoin backed stablecoin
payments so pandora which is the service i talked about offers pdp as a service with on-chain
payments but you could deploy your own service as a contract on filecoin services that offers
bandwidth as a service or compute as a service and integrated
with the payments contract to have on-chain payments, SLA-based payments. And if you do
this, you can also leverage all the existing tooling, like existing and new tooling that we're
going to build that I alluded to earlier, you know, like a payments dab, the payments explorer,
the PDP explorer, you you're gonna get all of that
out of the box plus all this amazing hardware that sps are running your service can tap into
that too so that's the idea but like i said it's still early days the only service we have today
is pandora which is you know hot storage with pdp but we definitely starting to look into building
out more services and more importantly would love it if any builder here on this space wants to build their own service and be willing to offer any and all help that we can for that.
Amazing. That's so exciting. Thank you very much. And I'm really pleased to see that our fellow COO Jennifer has joined us. And Jen, I'd really be interested to hear your thoughts on what the future roadmap looks like for PDP and Farcoin services.
I think like Arsh covered more.
So I feel like in a nutshell, if I am here just to remind folks, we launched FVM two years ago, and the reason why we
introduced FVM to the whole network is to allow programmable storage to happen on Filecoin.
It's not just program storage, but it's really any programmable data applications that's needed
like call resources to happen on Filecoin. We spent a decent amount of time to make a VM happen.
And it was designed to be a hyper like pluggable runtime VM.
And we were going to we introduced EVM first so that we can leverage the great
user community like tooling and builders. So to enable them to to can leverage the great E-SERB community like tooling and
builders so to enable them to leverage the file queen resources.
The roadmap was then to introduce Walsam and we didn't, there's a lot of community members
keep asking, hey, what's going on with EVM?
We didn't keep doing that because we actually didn't see a perfect use case to enable Walsam
to allow people to build programmable storage.
So instead of working on more different VM into the runtime, what we are working on is
really to bring programmable storage to the network by building this Filecoin service
concept and building the tooling that's needed to allow builders to build their own storage market backed by on-chain smart contract with different verifiers like SOAs,
so that not only they can leverage Falcreen service providers like storage, but like Arch data center. They have a lot of global resources that can provide support for different use cases.
So what we are doing here, not only just us, but with many other Filecoin teams,
what we are trying to do is to enable that, to make that very easy for the builders by building,
for example, a one-stop payment
contract that is like super flexible you can just plug it into your service your market your debt
and back you can use any ERC20 tokens you can use field backed stable coins like USDFC
and so on so forth and of course a lot of people know that Vue Us has been building this new storage primitive
backed by proof of data possession,
because we want to get closer to meet where the users are.
They love Polarap for archival storage,
but they also want something that's better for warmer,
like harder storage.
And we have been building this to to just gave a example on how can you
build different storage primitive uh in the user land without having to go through like fibs network
upgrades and protocol upgrades basically to allow innovation happen faster so we are keep building
that and again like arch mentioned that we really want to make sure that we are not
just staying on the protocol level but also making sure the protocol is very very easy for builders
to work uh to build their applications or l2s on top of so that's why we are also building this like
synapsis dk where you basically basically we are trying to hide a lot of the protocol
complexity from the builders, from the users, and just like bringing Filecoin storage to
where they are.
So we are working on that of, and the Filecoin payment, that's called the Pandora service,
by the way.
And then we are also working on the payment thing to, and getting that production ready and hopefully audited as well.
So more applications can just leverage it
without building their own.
The other thing that we are doing is partnering
with another Filecoin teams.
They are now like FieldCDN,
they used to be like Spark and the Checker Network.
And this collaboration is where we realized that
in the past, File Queen has been talking about
storage and retrieval as like two separate things,
but that's not how the real practical world works.
When people use storage and buying storage,
they just expect certain retrieval SOA,
and they want to pay for it.
And service providers, they are also expecting to be paid to serve retrieval.
So separate those out is making a retrieval story not ideal for Fall Queen at the moment,
because on the one hand, clients assume they get retrieval guarantees or certain retrieval SLA's, but on the other hand, storage providers today just think,
hey, I'm getting paid for providing storage, not providing retrieval.
So it's a little bit weird.
So as we are building this new service backed by PDP,
we are trying to make sure that we are talking about storage,
content routing, and retrieval as a whole package
when we think about a service. That's where we started to partner with the field CDN team to
make sure that we are also implementing a little bit centralized right now, sitting there on top of like Filecoin service providers
for those users who prefer to have higher retrieval performance
in trade-offs,
like maybe like decentralization or trustless,
however, people can get to choose
how decentralized, how much Web3 they want to be, right?
Because there's always an option that you can choose who,
you as a user can choose where to retrieve the data from
by the, from the SP that you originally store the data with
or any other SPs that you see has the data.
And how we are combining these services
and allowing different like storage and retrieval services
to be composed to be one service package,
I believe it's gonna be making the usability,
at least the developer experience much better
for those who want to use Filecoin resources
because you just need to pay once for the product
and you get all these like bundled service guarantees
as you see fit.
And we will love down the line
as we get like the payment contract
and the service like the first canonical service
like more ready.
We will love to call to action
to the community members
like with a series of requests for services
where we know
the builders and L2s that need to have some early builder programs so that the
community members can also join us in building together. Wow, that's amazing. I mean, as a storage
provider, with my storage provider hat on and with my fellow's hat on, I'm really excited about all
of this. Question, we're almost out of time.
We've got about four minutes left.
So just one more question that the community submitted.
This one to Ash.
What were the biggest challenges in getting PDP to mainnet
and how did you overcome them?
You're allowed to say there were no challenges at all and it was easy
no no that's but i honestly would love zan i mean zan was the driving force i mean kudos to him for
getting this to mainnet right from research inception to deployment uh so i would love it
if he wants to talk to talk to this question honestly yeah yeah thanks all right yeah I spent some time thinking about
about this actually by coincidence past couple of weeks and really there was no there was no
big charismatic long pole it was just a bunch of little issues over and over so I mean the
the process of driving a research idea is this was the main idea for this mostly came from Nicola and Luca for like how to get a
nice hot storage primitive, hot storage proving mechanism.
And so working with them to iterate on the research idea and then how to instantiate
it as a protocol.
There were some really fun moments, some interesting data structure challenges there were some like really fun, there were some like fun moments, like some interesting data structure challenges
that were just like technically difficult,
but like more fun, more than anything,
just the kind of slow slog of getting proving software,
like the SP software into the right shape,
trying to get like a decent like UX with the PDP Explorer,
making sure that like we tested things enough before we launched.
It's learning about the solidity patterns and upgradable contracts.
Yeah.
So overall, no big, nothing particularly big.
It just takes a lot of work to do.
Even though PDP is kind of a simple protocol, kind of a small protocol, it's probably like
a hundred times less complicated than Filecoin.
It's a lot easier than like Filecoin Porep.
But yeah, like PDP on Filecoin,
it's still a lot to build something that provides value.
So yeah, I hope that answers a little bit.
It's not the most satisfying answer.
No, no, absolutely does.
Thank you. We're almost at time. We have a minute and a half left, so we'll wrap things up. First of all, thank you to every one of our speakers for
taking part. Really appreciate your insights. Really exciting thing that you guys are doing.
And thank you to everybody as well for listening. Really important that this gets heard by the
community and we get feedback from the community.
So let us know what you think.
There are a bunch of resources out there and a lot more to come.
You can read all about implementing PDP yourself at docs.farcoin.io.
And we have a dedicated PDP channel in Slack at phil-pdp.
And obviously you can DM us at the at PhilOz Twitter account as well.
We also have a few YouTube presentations on the PhilOz YouTube channel,
which you're very welcome to watch.
Those include a few demos of PDP in action,
and some of our team members who are giving presentations on PDP and Farquhar services
at the recent PhilDe Dev Summit 6 in Toronto.
And obviously stay tuned
because we're going to be announcing a lot more information,
a lot more details of new incentive programs,
new developer tooling for clients and storage providers.
And you can also find a really good rundown of PDP
on the Philoz blog post at the philoz.org website. So with that we are at time. Thank you
everybody. We will look forward to tuning in again soon for the next project. Thank you. Thank you.
