Filecoin Filecoin Virtual Machine - FVM, 13 Mar 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Filecoin Making Storage Deals on Filecoin-EVM - Zak Ayesh

Description

Join Zak Ayesh from Filecoin for a talk titled "Making Storage Deals on Filecoin-EVM".

As new users flock to web3, critical infrastructure advancements are needed to scale. Scaling Ethereum is your chance to shape the future of Ethereum. Join us March 10th-29th for three weeks of hacking and summits featuring teams like Gnosis Chain, Scroll, Hyperlane, UMA, IPFS/Filecoin, and more.

-----------------

Follow us: https://twitter.com/ETHGlobal
Check us out: https://ethglobal.com
Email us at: hello@ethglobal.com

A

B

Welcome everyone to the filecoin workshop, making storage deals on filecoin evm joining us today is Zach ayish, who will be taking us through this session and with that I will pass over to Zach to introduce himself and get this session started.

C

Hey everyone Hi yep, my name is Zach ayish.

C

You might have seen me around on a couple of uh other file: coin coding, demos, I'm, a developer Advocate with the file coin, virtual machine team at protocol labs and today I'm, going to go over uh programming on the fevm, and you know you might have seen this talk from me before I previously Global events, but on this talk, we're going to do something a little bit new we're going to go over uh towards the end, how to make storage deals uh with smart contracts on the follow coin virtual machine.

C

um So this is a really cool new functionality. We've been working on for a long time. The engineers have been hard at work and so I'm excited to go through this.

D

C

Demo with you today.

C

Yeah so uh quick Story, one of my very first projects, uh interacting with any of the file coin.

C

Ipfs protocols was creating a dynamic nft and essentially it was like this nerdy shooting Jersey cat reference, where you would mint an nft box and it would use the chain link vrf and randomly pick uh when you minted the cat to either be this attack cat or a sleeping cat right- and this was probably two years ago or so now, and little did I know I'd be working uh this closely with the final coin stack and helping push things forward.

C

So today we're actually going to be using this photo uh to store on the with filecoin storage providers uh using solidity, smart contracts um you can find this is the actual uh photo of me trying to get this demo working. We actually uh first got this demo working for East, Denver and I presented at the filecoin hacker base. It was uh quite the experience uh working with Engineers uh late into the night. They put such a phenomenal amount of effort into getting this working and so yeah it was it was.

C

It was quite the Herculean task, but I'm happy to be a little bit more well rested and presenting to you today and, if you've seen any of my other presentations. You know I like to talk about um imposter syndrome and a lot of my uh talks and I just want to briefly mention that here like this is. This is like me, working with the engineers trying to figure out how all of this works, uh I'm still figuring. All this out too uh so like don't feel bad.

C

If any of this is confusing to you or um feels overwhelming, it is for everybody I just like to put that in. In all of my talks.

C

All right so today we're going to be going through um just a short introduction on the final coin. Virtual machine I want to focus more on the coding side of things. We'll do a demo and remix deploying a very basic uh like solidity.

C

Contract doesn't use anything special file coin related in it uh then we'll you we'll show an example using the file coin, uh solidity: libraries that gives you filecoin specific functionalities and then we'll move on to hard hat and making a deal on uh a storage deal on using smart contracts, which is kind of uh the special thing we're demoing in this talk.

C

Right, so what is the file called virtual machine? It is a virtual machine that lives on the file coin, blockchain right and it delivers on-chain programmability to the final coin, Network for the first time.

C

So the filecoin virtual machine is actually made in webassembly, um but it was built to support multiple runtimes right. So um you might have you'll hear me talking about the F evm right and uh that isn't running on ethereum or anything like that. That is running on file and how it works is at the base layer. You have the filecoin virtual machine uh like running on top of file coin nodes written in webassembly, and that was designed specifically to be able to virtualize other runtimes on top of it right.

C

So the first runtime the team targeted, was the ethereum virtual machine because uh everyone knows how to work with Lydia. At this point in web 3, at least you know it's the most common um language to use. There's tons of tooling You Know Remix hard hat metamask everything supports it, so the ethereum virtual machine is actually virtualized on top of the fvm and this ethereum virtual machine when you're interacting with it um interact, acts like any other evm chain.

C

You may be used to whether it's uh ethereum or or polygon or Avalanche or or what have you um and so to you. It shouldn't look any different and you should be able to use all all of your tools in the future. This could be extended to other runtimes if they are developed and um there is a roadmap for the team to develop what we call native actors or the ability to compile smart contracts to wasm and deploy those directly to the chain as well.

C

If uh you know you like to program in any language that compiles tawasm webassembly, which is a lot.

C

So yeah, this is the new thing. This is the big New Deal uh is creating a contract, uh creating a storage deal via Smart contracts. This is a relatively new development, even on the sem and we'll kind of go over how it works. Essentially, um you know we'll be emitting a event, a solidity event that boost storage providers can listen to and uh store your store, your data for you. But you know this is the FIP file coin Improvement protocol. You can find it in the file coin. Github.

C

If you want to read up more uh on a little lower detail on how it works all right. So let's go ahead and let's just dive into the coding. Well again we're going to start with remix and we're going to deploy a very basic contract called Simple coin. You can think of it as as a simplified erc20 contract very basic um and yeah. This is just going to show off. You know the evm compatibility, so let's start out uh first, of course, you're going to need to download metamask. You can get this at metamask.io.

C

It is one of the most popular uh ethereum wallets. You can get. um You know I use it as a hot wallet for testing development um yeah. So you can. You can download it on metamask.io and you see I already. Have it downloaded right here right and once you have metamask, it doesn't know about the final coin chain.

C

It has some default chains, it knows about, you, know ethereum and its test Nets, but it doesn't default, know about the final coin chain and so we're actually going to point it to uh hyperspace, which is uh the filecoin test net, similar to sepolia or Gurley. Before it, you know, became a whole for-profit thing um on ethereum right so to add uh hyperspace to metamask.

C

We can just go to chainlist.org.

C

Click include test Nets.

D

This out of the way.

C

And just type in filecoin.

C

And you'll see here, like all of the different file coin test: Nets uh mainnet as well we're gonna click on add to minimask for hyperspace. Since that's what we'll be using for the remainder of this demo, mainnet for fevm support comes out on March 14th, so no evm, yet, but very close on mainnet.

C

So yeah, you just click, add to metamask. You know um a pop-up will come up for metamask I already. Have it added right here, but yeah that'll, add hyperspace to your meta mask.

C

And finally, you're going to need to get some test net fill just like ethereum and uh any other, almost any other blockchain you work with. You need to have currency to interact with that chain. You know to prevent spam prevention and to pay the node operators um for running all this computation right, but on a test net. uh You can just get this from a faucet right, because test Nets have no value.

C

um Most tests, National I, have to add so we'll click on hyperspace dot, yoga right- and this is the faucet you can use now. Filecoin has its own address, address scheme which you'll see as like key addresses so like T4, yada, yada, yada or T1 yada yada, but everything is actually compatible with ethereum addresses right. So, if I just copy, my account address and I paste it in there just the ethereum address we get to go through this awesome captcha, which is always a fun challenge to do live now.

C

Click on the bunnies next honey bunny usually have to go through two screens, all right cool and click Send and test that faucet testnet fill from the faucet is on the way to my wallet.

C

It takes about a minute to get to my wallet, um we'll kind of go over uh transactions on filecoin in a second all right, but with that you have metamask, you have some t-fill and we're ready to move on and deploy some contracts on. Remix and I already have remix open. So that's nice!

C

So once you come into remix You Know Remix is an online IDE, integrated developer environment. Basically uh just a quick and easy way for devs to test and interact with smart contracts.

C

Some people use it for the whole Dev flow, we'll go over some hard hat a bit more complex tool later, but for now um we're gonna go and remix and you'll see on the left. Here we have a little file explorer and you'll. You should get some pre-built smart contracts, storage, outsole, but I've imported. These smart contracts, uh simple coin, is one of them and you can see it here. Right and all simple coin does. Is uh it's a very simple coin? It takes the Constructor.

C

You can pass in a value for the tokens you want to be minted and it will mint it to whoever deployed this contract onto the fevm, and we just have a function to send that coin to other addresses and get our functions to get the amount of token held by a specific address.

C

All right. So we're going to come to the compiler tab, click compile simplecoin.soul and everything is good. I have Auto, compile, turned on to make my life easier and we'll go to the deploy tab right, you're going to want to make sure that injected provider metamask is chosen when you come in, it will default to remix VM. That is a local VM within metamask and it doesn't interact with any blockchain anywhere.

C

Just this like virtualized chain on your browser injected provider, metamask will tell it to send all transactions through metamask and because my metamask is pointed to hyperspace it um it is going to go to hyperspace and it looks like I got my 5T film added. So that's awesome right.

C

So then, you're going to want to make sure that the contract you're pointing to is the one you want to deploy. I want to deploy simple coin and we're going to put put in the Constructor, since that has to be filled out before we deploy it to 1200 tokens. That's how many I'm going to Mint uh for simple coin, and they will be assigned to me again if I click deploy we'll see. Metamask comes up with a transaction. It's going to estimate gas fees, we're going to click confirm.

C

So if you're used to gas on ethereum gas on file coin is actually calculated a bit different and it does use file coin gas and not the traditional evm gas, so the gas calculations, you can find more detail in the docs, but they're based on wasm time, run times for all these computations, um as opposed to the hard coded gas values that you'll find in most ethereum run times right, and so that's going to take about a minute to deploy it's going to take some time. uh So I have a pre-deployed contract.

C

We can look at all that goes through, so you can load any contract right here as long as you have the ABI and uh the address is deployed at which remix has the API. Since we have the contract in here and we'll just click add address, oh and it turns out my contract deployed at the same time. So that's convenient, we'll just go ahead and look at the contract. We just deployed.

C

All right, so, if I copy and paste my account in here and click balances boom, so I have a thousand two hundred. A thousand two hundred I meant it to myself to initiate this token and um yeah. So that's simple coin right, so this is just basic um solidity. Working on the filecoin evm.

C

But now I know that that's cool, um but why uh evm on filecoin right? There's a million other evm chains out there and remember the history of filecoin is that it was designed um primarily for decentralized storage. Storing the internet's data and I find that this is a very important part of the web. 3 stack right. A lot of front-ends for web3 dapps are actually hosted on centralized servers um and so filecoin is kind of there for Cold Storage right, which is a very important um like sector right.

C

So we don't have to trust on any like one centralized entity right and so the Falcon blockchain actually um monitors. The storage deals right, the metadata um for these uh for for the storage providers right, and so how can you access these storage deals? You can do them through these file coins. Solidity libraries created by our friends with the team zondex right. So let's take a look at them right here and what I'm about to go into some more detail about uh storage deals in a second.

C

Right so you know these are basically solidity apis. You can't use these on any other chain, because these are specifically for the fevm and they take again take advantage of um these native actors. We call them uh for interacting with storage deals.

C

It is in beta at the moment it is being audited as we speak. It should be uh ready very soon, but I just need to put that disclaimer and yeah. You see the readme kind of explains some things. If we look in the contracts directory you'll see here, we have apis that these represent apis that were already open to filecoin, but this opens them up to be used in solidity.

C

So if we look at the market API solidity contract, this actually opens uh apis, like a bunch of apis for getting information about a specific deal on chain, getting the actual pcid getting the client who asked for the deal getting the provider, the address of the provider, who's, storing the deal and um so on right. So these these really uh using these in your dapps, really opens up the world of the fevm, would compare to other evm chains.

B

Hey Zach, when you're um in remix, could you zoom in a little bit as well.

C

Oh yeah sure yeah right, no problem I'll make sure to do that when we go to the next contract. Okay, yeah appreciate that um cool, so I'm mentioning these deals right. So let's talk a little bit more about them and how they're created in the past and how we're going to create them later on in the demo right. So if we go to Phil Fox, which is um a block Explorer for filecoin, you can click on the blockchain tab here and click on Deal list right and these are actually.

C

These are actual storage deals on chain if we click on one. This deal ID right here you have the provider. These are usually minors on the file coin Network and their address their ID, and you have the client right the address of whoever requested data to be stored right.

C

um The data that are stored here and this deal is started to gigabytes um and you can see when it was stored and the pcid AKA. Basically, you can think of it as the root hash of the data that's stored there right.

C

So we're going to talk a little bit more about that that root hash. That I mentioned earlier right, also known as the pcid or the com P right. So you'll see this big graphic. uh It may look confusing, but it really isn't much. Essentially, you take a file. Let's say it's that that cat photo that I showed earlier right and um you want to prepare it to be stored in a fire coin.

C

Storage deal right well, one of the first steps is you're, going to turn it into a car file right, a compressed version of the of the actual file and then you're going to want to compute what we call the ipld, dag uh directed acyclic graph, uh confusing it's just like a tree. If you're familiar with like the inner workings of ethereum or Merkle tree or a binary history, that's essentially what it is um right. So it's going to take that data. It's gonna!

C

It's gonna take that file that compressed files, kind of split it up into chunks, and then it's going to Hash each of those trunks and then create a tree hash all the way up until you get your root hash, and uh this allows you to get like a hash that represents the whole data um and so that kind of just represents the um raw file or the raw compressed file.

C

We actually are gonna You're, Gonna Wanna pad the file uh to make sure it fits and there's tools that do all of this we're going to use one later in the demo, um with some zeros and essentially, when you send this to a storage provider, you're going to send this padded compressed file, along with um the ipld graph or dag to the source provider and they're, going to confirm that you know your file does in fact uh hash to that pcid or that root root hash and that's going to be what represents your deal on chain right here right.

C

So long story short file, we create this graph. We get this piece of data that represents the file and that's what we send to the storage providers to store our files.

C

So this is how deal making uh works at the protocol level and how it worked uh specifically uh before the fem was a thing right. um Essentially you you, the client or whoever wants to store the data, would um uh would uh decide what data you want to store. You would use a tool of your choice to compress it and create that file that we talked about earlier um say: look, you would do some research on storage providers and what deals they're offering.

C

Maybe you know what storage provider you can negotiate with them either way say: okay, you kind of find a deal that you think works. You need to lock some funds in escrow so that the storage provider knows you're willing to you have the funds to pay for the deal over time.

C

uh You send what's called a deal proposal to the storage provider right and uh the storage provider will look it over and make sure that that's what y'all negotiated or what they deem as a fair deal, um the storage provider would then say: okay, this looks good uh we're ready to accept this and publish the deal. So then you need to actually transfer the data to the storage provider right and uh all of these steps. There were tools to do this. There's marketplaces, you can look uh to find storage providers, um but yeah this.

C

This is a quite a manual. You know process. There was also things like web3., storage and nst.storage that do all of these steps for you and make it a lot easier, um but yeah you would transfer the data over. You know they would make that check to make sure the data is actually what the pcid that's in the deal and uh then they would call a function on the filecoin API. It's called publish, storage deal and that would actually you know, prepare them for storing the data.

C

And so that's kind of the traditional way of making the deals and how everything will work uh with the fvm uh I know that was a lot of information, so I'm going to go ahead and check the chat to see. If there's any questions uh about any of that before I move on.

C

So yeah, if you have any questions, feel free to drop them in the chat as we're going on and I'll try to make uh periodic checks like this.

B

Yeah there was one question from harsh um how seven maynett would lead to burning Phil.

C

Yeah, so um file coin, just like ethereum has a similar implementation uh for EIP 1559, so every transaction that's sent to the file coin blockchain. uh Some of that fill is burned right and so, with the final coin, virtual machine live. You would expect more transactions to be coming through now, because there's more utility- and uh you know- that'll- probably increase the burn of Phil.

C

Yep and I see some feedback on zooming in we'll make sure to do that when we go back. Okay,.

D

C

So I think that answers all the questions right now so yeah. So uh we kind of talked about uh the traditional way to make deals. You can still totally make deals that way by the way. None of this deprecates that you know, file coin, uh still works that way. This is just adding on functionality and new ways to make deals using smart contracts now right and so one of the first ways we demoed how to do.

C

This was what we call the bounty, hunting, Bounty, Hunter method um and there's a contract you'll see in my hard hat later that that does this, um but essentially like it's just a smart contract where you take that pcid, you know again that piece of data that represents it and the size of data you want to store, and you just create a bounty in a smart contract for that right, and so this is a very useful tool.

C

I would say for like Dows, like maybe you're a decentralized science, a d side down, and you want to crowdfund for a specific piece of data to be stored on the file coin. Network. You can use uh this flow to say hey. This is the pcid for the data. This is the size of the data that we want stored, uh let's crowdfund and see who can actually get this data stored on chain for us and we'll reward them, and it actually uses the follow coin.

C

Libraries to make sure that the payment is sent to whoever actually the address of whoever made the deal right. So this is one way this is just kind of like hey. Please, someone make my storage deal for me.

C

This is what we're going to demo um in this uh later on is um an even more automated flow for making a deal which um now, like you know, let's say: I have uh some data I want to store, I generate the car file and the dag and I want uh in part of my smart contract flow. I want to be able to call a method to store this, uh this data right, and so we can actually call a function in salinity as long as it emits that event.

C

I talk about I talked about earlier, create deal proposal. Boost storage providers can listen for that event to be emitted from the evm and read the data from it and use that as the deal proposal right and actually store your data from that you know so we're going to tell them hey. We have this already pre-prepared data and a server somewhere uh here is like the deal proposal. Here's how much I'm willing to pay here's.

C

You know the collateral, um here's, how much collateral I expect from you and how much this is all going to cost uh per block and um send that into a function in our smart contract that functioned in a mince an event.

C

The Boost storage provider sees that event and says: hey um that looks like a fair deal, takes it up and stores your data right and a core thing I do want to point out here is that when the storage providers actually store your data, they are writing proofs to the final coin, blockchain that they are storing your data. Like that's, super important right. That's how that how we keep this all decentralized. Is that we're not just trusting the storage providers to keep your data?

C

You know live they actually have to provide proofs and specific windows, and if they don't, they risk getting slashed.

C

So we're going to first go through um a demo and remix again using the file coin uh example: contract I call the file coin, Market consumer. It just uses that uh zondax file coins, literally library, and gets data for a specific deal on hyperspace right. It's all the same things we're just going to go here back to remix and I'll zoom in. Hopefully that is better and we're not going to do simple coin. We're going to come back here and we're going to do this file coin Market, consumer right, really basic contract.

C

We just have a bunch of State variables and a bunch of functions uh to call those getter functions and the uh Market API for the zondax right. So we're just calling all these getter functions and storing the data um in our smart contract in these State variables here right and then I have one function that calls all of these. Many functions store all.

C

So um yeah I see a question for uh repos, with showcase to file. Coin storage deals working, yep we're going to get to it right after this demo, um so yeah we're just going to compile it. You know here we are calling the zondex libraries and just like everything else, make sure it's injected provider metamask up here supporting your Falcon Market consumer. You can hit deploy again to save us some time, I'm going to pull in a pre-deployed contract.

C

So we don't have to wait for the transactions to go through.

D

Oh not that one.

A

C

Throw this right there.

C

All right, so if we go to fill Fox we're going to go back to the main fill Fox page, we're on mainnet right now and we're actually working on hyperspace. So we're going to switch the network explaining to hyperspace.

C

And let's pick a deal, we want to pull information on right. So let's just get information for deal. Id, 1011.

C

And uh go to remix: you know you can store deal. 1011 click store, all we'll confirm our metamask transaction go through again. You know we are paying gas fees. It is going through with that EIP 1559, like uh structure where some of the fees are getting burned, um but yeah. um This should update with our information uh for that specific deal.

C

If we look here, um we actually have this old deal with old information in it, uh since this is a pre-deployed contract um and when this transaction goes through we'll come in and we can see that like hey, like this deal, matched with that, but it's going to take some time for the transaction to go through, so actually why transactions take time on the file coin.

C

Blockchain is because there's what's called a delayed execution model where it takes about 30 seconds for your transaction to be actually included in the chain and another 30 trans 30 seconds for your transaction to actually be executed right um and yeah. So that's why it takes about a minute on average, so our transaction has gone through and let's look at some of the information here right, so our size is 262..

C

Let's look at uh here yep, so 256 kilobytes, uh that's about where we're at on there, um and this is actually that PC ID but serialized and represented as ethereum bytes right. So if we convert it to the representation, CID representation which leaves base 64., um it can be represented as a CID that we see on chain.

C

um You know the price per epic, which is zero since it's on test net, the deal provider, actor ID 1036, which is their deal ID right there right. So we got the information from that deal in our smart contract and you can use this to create all kinds of cool logic.

C

um You know other applications that you may have heard earlier, like data dials or Perpetual storage contracts, all kinds of things we're excited about to be built right, Okay. So now we're going to move on to the new cool part right and we're going to actually create storage deals uh with that method. I talked about earlier um on hyperspace and we're going to do it via hard hat right. So you can find this Nifty hard hat starter kits under the file corn project GitHub right and here you'll see.

C

If we go into contracts, you'll see the basic solidity examples. There's a simple coin: we deployed earlier you'll see um the Bounty contract I talked about in the market consumer we just interacted with, but we're actually going to be dealing with basic deal client today and deal client.soul specifically right.

C

So let's go ahead and we're going to clone this repo.

C

We'll try to get this oh got to minimize this, so we're going to go into a terminal right. You see. I already have another repo open here, but we're just going to walk through this real, quick, we're going to do git clone and we're going to paste in that repo name.

C

Make it big. So it's easier to read: hit enter that's going to clone it in there we're going to type in code. I have the vs code shortcut that'll automatically open this nvs code.

C

We don't need to update right now.

C

Oh I'm, actually One Directory up right, so, let's CD into the fvm hard hat kit and now we'll open it from we'll open it from there and I'm goofing with by typing abilities right now.

C

There we go all right, cool, uh we'll, open a terminal in here right and one of the first things you're going to want to do is type in yarn to download packages.

C

Right and this will get all the packages that we need into our project and um while that's going on we'll just kind of talk about how this works right so again, just like I showed you in that repo. We have all of those uh contracts, including the deal client.soul um contract, and uh it's going to give us some problems just because uh some downloading the yarn, but it's fine.

C

We have a deploy script right here that deploys each of our contracts and we have very importantly here, tasks right and these tasks are how we can interact with our deployed smart contracts once they're on chain.

C

So if we go to, for instance, the market consumer, we have a task that calls that store all function right and sends it on chain. um But the what we're going to focus on here.

C

Is we're going to go back to deal client.soul and we're actually going to focus on.

C

Calling this function make deal proposal right, so it takes in this struct called deal, and you know, stores a bunch of information on chain does a lot of stuff, but the most important thing is it emits this event. Deal proposal create right um and that's the event that uh storage providers know to look out for, and if you want to see that struct here's our deal request we're going to pass in a PC ID a peace size.

C

It's a deal verified on fill Plus uh the label, which is uh usually the raw, um the raw CID before we do any padding or anything to the car file.

C

When we want the deal to actually start the Epic, we want to start when the deal will end how much we're going to pay per Epic the collateral that the provider puts up in case they need to be slashed. The collateral the client puts up are you. The client puts up to prove to the provider that you can continuously pay them for their services, and um these extra params here are where some interesting magic happens right.

C

So this is where we're saying uh you know the the the booth storage provider sees that there is an event committed emitted in ethereum and um that they want- and they say, okay, this this uh proposal looks good I want to store that data, but they need to retrieve that data from somewhere right. So we need to have that in some kind of open server um somewhere else right.

C

um So yeah see there's still some maybe issues with reading it. So hopefully this makes it a little bit more clear.

C

um Yeah, so that's kind of what we're doing here, we're giving them like an HTTP, ref or ipfs reference and the size of the file that they're actually going to store right.

C

um And then to deploy you just type in yarn, hard hat, deploy in the console hit, enter and I'll run. It run the script and actually start deploying our contract. Oh of course, one specific thing I missed here is: we need to add our private key in a DOT EMV file right, so you're actually going to want to create a DOT EMV and then put your wallet private key in there. So um Hard Hat knows what wallet to send this transaction with right and you can do that.

C

By going into metamask and again, I always have to put this disclaimer never ever show you a private key to anyone and never ever check this into git. If someone gets your private key and you have mainnet funds in that wallet, they can and most likely will steal the funds right. This is a dummy account, I use just for demos, so there's no real money associated with this and I want to show you the steps.

C

But again um you know this is not advised to ever be shown right, so you're going to go here, I'm going to type in our password and metamask and we're going to copy our private key over.

C

So please uh don't don't steal my my poor test net fill they just type in private key private, key and I'll put it in some quotes. Paste save now we'll type in yarn, hard hat deploy and our deploy. Script will start and start deploying our it's going to compile our solidity files and it's going to start deploying them right.

C

um We're not going to wait. That's why I have my other demo open, so we're just going to go ahead and close that and we're going to go to the the pre-deployed one which real, quick.

C

Go ahead and open this.

C

All right so in this, in this uh repo we've already deployed the contracts. Everything is good there. You know, we've done the yarn, I have the dot EMV file and so we're almost ready um to call the method. The last thing we need to do here is we need to take a file and we need to.

C

um We need to generate that car file and we need to store it somewhere right.

C

um So let me make sure this is big. There's.

A

C

C

What we're gonna do.

C

See do I have my Explorer open here.

C

All right, so, if I just go to my pictures right here, you'll see I have my cat photo. uh He attack dot jpeg as opposed to he sleep, um and so that's the the file we're going to turn into a car file right and how we're going to do this is we're going to use this tools. uh uh Go generate car tool right here right. So, if I see the into tools and I see D into go generate car, you can type make I've already made it. This will compile it.

C

This tool is written in, go, hopefully we'll write this tool in JavaScript, so it'll be a little bit more native to hard hat, but for now it's written in go um so make will actually compile the program and we can call it uh from this uh directory right. So if we.

C

What we're going to do is we're going to um and just to save time, I'm going to put the script in here. uh We're going to call in this directory generate car, uh we're just going to say: hey it's a single file, and this is where the file is right and see attack.jpg, and this will actually generate the car file right and and the IPL dag that goes with it. So, if I hit enter you'll see we have all these cids are generated.

C

uh The very important one we need is right here under data CID, we have pcid right, so that is the CID of the file that we're going to store and that's the pcid that we're going to use to represent this to the storage providers.

C

Now, if I uh LS.

C

You'll see here this is that cid.car and this is the size of the file we're going to store right. So we've generated the car file. Now uh we know the size of the car file. We want to actually uh put this somewhere that the storage provider can store right.

C

um This could be anywhere right. This could be any open um service, but an easy one. We're going to go to today is web3. storage, all right, so we're just going to type in. We have three dot storage.

C

Right and I already have my logged in and we're going to click Start now, and here you can just upload uh upload files, and you know, web3. storage will actually go through that traditional deal, making flow and make deals for you. uh But what we're actually using this for is they actually just store your data and their ipfs Gateway, and anyone can kind of pull it up that way right, and so that's what we're going to use right. So um you know I've uploaded the raw file here, but here is that generated car file.

C

I click on the CID will come up right here and this will pull up like the the Gateway for it on on ipfs right here and that's actually what we're going to pass through and use as the URL uh to signal to our storage provider. We want to store this file.

C

Okay, so all of that said we now have our files stored in a server somewhere or ipfs, or wherever that the Boost storage provider can look for we're ready to call that function. Make deal proposal pass in all of our deal information and see. Hopefully, if the storage provider picks it up right.

C

So we're going to go back out to the main, hard hat kit directory here and we're going to call this task make get deal proposal. You see, there's a lot of parameters it takes in and so I've. Actually this is one we're going to copy and paste into the terminal.

C

um There and I can just show you because I have it in a Google doc right here, right.

C

So um this is the task we're running so yarn, hard hat, uh tells it okay and then make deal proposals the name of the task and we're pointing it at this contract I've pre-deployed and uh we're giving it that PC ID of the data that we have stored uh the size of the data.

C

um You know the verified deal uh is false and we're passing in all this information in and where it can actually find the data to store. So that's the actual full task, I'm running.

C

We'll hit enter, and this is going to take a second to go through again. You know it's making the deal proposal, Network, hyperspace and we'll look at something cool, because I'm actually um assh into a um boost storage provider right, and so hopefully we can see it pick it up live right.

C

um So here is a GUI for the Boost storage provider and uh hopefully once the steel goes through uh once the transaction goes through. We'll actually see a new deal added on here that the deal proposal picks up the the storage provider picks up like so we'll. Just give this a second to go through.

C

um You know we can kind of look here at uh the GUI for the Boost storage provider. So boost is just a um kind of uh helper uh binary. You can run the storage providers typically run to make it easy to deal with storage deals and visualize them with this convenient GUI, so they usually run alongside a file coin node like a Lotus, node right um so yeah. So this task is going to go through.

C

um You know it passes everything in um and then actually listens for the event right and boom. You see our transaction went through it emitted the event and right here the storage provider has seen that event and it's actually pulling in the data right.

C

um It's saying transfer installed uh that may be because of like a HTTP Gateway it'll try to redo that right um and boom. There we go so it's transferred the data. You know it's made all the checks that the pcid matches the file and it's saying hey this deal is good to go. Everything looks good and we're ready to publish the storage deal.

C

So after that um you know, if I was, you know, this SP I can just come here and click publish now, and um you know it's going to publish that deal on chain for me and, of course, this SPS probably have automated systems to do this. This is just a very automate uh manual way to demo how this works right and uh again, the data they're storing is that picture of my cat right um all done through smart contracts. uh So uh very excited about this. You know if we click on the deal here.

C

um You'll see that the client address is like a file. Coin. Client address a T4 address. Right um but if we actually copy this.

C

Oop, it's not actually gonna, we'll just open it up um and we'll copy it right here. You could copy this and you go to like uh a translator tool. There is one in the hard hat kit uh script that will actually translate addresses for you. You type it right here, um no because it's just converting okay, we'll just put it in here, oh and we need to put it on hyperspace. That's the issue here.

C

So if we do that, um you will see that this is the eth address of the contract that we um admitted. So if you use the contract itself as the client of the event right- and you know, we can also look up this contract on Phil Fox on hyperspace we could put in the ethereum address or the T4 address. Either one works see it's going to say actor evm and it's going to show um these.

C

uh This is the transaction we made with the mcdeal proposal and amid uh the events we admitted right and so yeah this is the full workflow. This is how you create storage deals on filecoin um and I'm, going to blast you with a bunch of resources. Now, before I save a couple of minutes uh for Q a right, so let me see here.

C

um Again, here is the hard hat starter kit. If you missed it, um you can find it in the GitHub uh for the file corn project fpvm, hard hat kit, um and if you go within hard hat kit, you'll actually see if you scroll all the way down, I link to Foundry kits for each of the the client contract and the Bounty contract. That's where they're being developed currently um under the Lotus project. We are going to kind of bring all of this together.

C

But if you are like kind of privy to Foundry, you can you can deal, you can look at these and they have a little bit more technical, detailed readmies.

C

um And I also want to shout out a Community Driven, Foundry starter kit right, so um a great Community member, very active uh shinghan um developed this uh uh Foundry kit right here um and he's very active Community member he's active on the East Global Discord, as uh at Peep, and you know, um yeah I'm, just like uh super proud that this is uh getting made, he's updating it constantly uh very knowledgeable, Community, member and uh yeah. You know we're gonna work on getting this.

C

um You know completely up to par, and this will probably become the official Foundry starter kit that we um push everyone to. So. uh Thank you very much for such an awesome job job and my colleagues, Matt and Sarah are actually doing uh twitch streams. Now uh twitch.tv slash Phil Builders. uh The next two streams will be March, 16th and 23rd at 9. 00 a.m, PST 12 p.m, EST, 5, PM, UTC right so feel free to go jump on those streams. Ask questions you'll find me there for some of the streams for sure.

C

um But uh you know we're excited to launch these. These twitch streams.

C

um There is a request for startups out, so if you are a startup and you think you want some support, um some uh uh kind of maybe some grant, funding or or just seeing what's going on with mainnet feel free to come over here to the request for startup, so rfs.fvm.dev.

C

And finally, all of this was done on hyperspace testnet, but this will be launched uh March 14th next week. We are super excited on Pi Day. Of course we are all nerds over here and we love it. So um you can watch uh the event for the fbm mainnet launch on the final coin. Youtube um and please go there. Subscribe, wait, it'll, be a big deal and, finally, for everything else. uh My colleague Sarah has made this awesome link tree.

C

um That just has a bunch of other resources on it. um You know an about page. uh The docs, uh this hackathon cheat sheet is really convenient. If you're um going to be on the hackathon, it really combines all of these resources um that we've talked about it's. uh You know up to date now and yeah super useful um uh resource.

C

And finally, we have our mainnet cohort, uh which you can apply for as well, which is just a combination of teams that are all looking to deploy to mainnet and are ready to go and become active uh members of the filecoin evm launch.

C

So, thank you. So much uh for listening to my talk, uh looks like I have just a couple of minutes to address any questions in the chat and I see there are some so I will try to answer them.

B

Yeah one of the first ones was a were there any libraries other than go for creating car files.

C

There may be there might be a JavaScript library out there somewhere I'm, not sure if it's up to date and how well it works right now we're using this, but we are working on making um uh uh more libraries and we're actually working on with uh the community to make a front end. That will do all of this, for you right so um just a convenient uh web app where you can go in upload a file or generate the car.

C

The dag everything store it somewhere that storage providers can take up and that'll be all done in the browser. So we are definitely looking forward to that.

B

And William asked what is the difference between the pcid and the CID when you you get when you upload the file to ipfs.

C

Yeah, that's that's a great question, so the ipf scid is actually just kind of the raw called the com. D CID, where you just take the file turn into uh you know uh you generate the IPL dag for it and you generate that the pcid is very specific. Since storage providers want these specific uh formats, so we turn it into a DOT car file. We do that padding and then that's the ID that we get is the PC ID right.

C

So it's just a very specific CID, but they look identical right um and if you were to put that car file with the padding and everything on ipfs um I believe that might be the same CID that you would get. But uh don't quote me on that. Thank.

D

B

Harsh asked uh how to access the data once stored, like via ipfs only.

C

Yeah, so uh that's like the retrievability side of things, um there's a lot of cool projects working on that uh you can go to the uh I believe it's the Lotus stocks um has a section on retrievability uh um on here. You can also um use a service like file coin Saturn, which is new, so this is basically a I. Don't think this works with filecoin like it works with ipfs, but now filecoin just yet, but it is working. So this is a CDN um that, like caches ipfs, um requests and makes them super available.

C

Anyone can run a node, you can go to saturn.network and they are working on being compatible with filecoin as well. To make um you know, data available on file, coin retrievable right! So there's a lot of options. um You know search up file, coin retrievability um and it's being made easier every day.

B

And uh what are the key advantages? Over ipfs Stephen asked that fantastic.

C

Question so uh ipfs, you know, is its own. uh Peer-To-Peer Network for file sharing, I can pin data on ipfs I do all the time and it's there, but there's no guarantees that your data on ipfs will stay there right like if someone. If everyone stops spinning that data it's gone right and someone could always repin it, but there's no guarantees right uh file coin.

C

We have very strong guarantees that the data will still be stored because the storage providers have to provide those proofs on chain uh that they have it or else they risk slashing. So they directly incentivize to keep your data right. So filecoin is really used for, like cold storage of data data that you want. Very strong guarantees will be stored uh and available.

B

Awesome, okay, and that was all the questions in the chat awesome a little bit over so uh yeah I just want to thank you uh for joining us. Today, uh everybody and thanks Zach, for the great presentation I'm going to drop in the uh just the Discord, the filecoin Discord Channel. If anybody else has any other questions feel free to reach out there.

B

C

Do and, and thanks so much for for having us uh this was this was awesome, so I hope, I hope. All of you found it helpful feel free to reach out to us uh on the follow con slack on the global Discord um and anywhere we can be found and we'll we'll try to reply and uh Happy hacking.