Censorship resistant storage network powered by Decentralized Durability Engine

Transcript

okay so let's start hello guys welcome to the to today's St burning sharing sessions I'm Alex that is the host for this session uh so before we start so please allow me to introduce the that learnings and by the way I'm also the member of this community so that's learning uh I mean our men tutorial is located on the GitHub and our purpose is to uh give the Junior developers and executable and simply simplest blockchain dep learning tutorial and present Advanced developers with a platform for communication and cooperation so today we invite Guru from

codex and today's topic is to is sensor shap resid than storage Network powered by the decentralized durability engine so now let's welcome to G we have the microphone hey guys uh I'm quickly going to share my screen uh okay yeah before we jump into the slides I'll take a moment to just tell about what we do at if so if is Institute of free technology and I've been contributing to IFD for the last two and a half years so uh we have a portfolio of multiple projects uh starting with logos which is basically a network State Building and movement

building side of if uh and we also have other projects on the technical side like waku which is a Communications protocol uh this is very much similar to ethereum's whisper so whisper was a part of ethereum white paper itself and vaku is pretty much the same protocol I'm sure uh you've heard about it from vitalic tweeting about vaku multiple times over the year so yeah uh it's being used by status rail gun craft and multiple other projects uh under the hood so yeah this is the communication side of thing and we also have codex which I'll be talking about today and this is the storage side of uh logos

where you can pretty much store a file on codex in a decentralized storage Network and build applications on top of this leveraging decentralized storage as well and uh another thing that I would like to highlight is uh logo codex is kind of new to the market compared to the existing uh dsns so it's kind of early and it's a great time for you to start contributing to codex if you want to but uh yeah uh I'll be taking you through about codex in the next couple of minutes but you can also check out our other projects in the portfolio at this website it's free. technology and you can find this portfolio over there and if you're looking for a job we also

have a job board over here if you are interested in looking for a position but going on with codex uh I have a short presentation before we head into the Hands-On part of today so uh MH when we look at the problems that exist with centralized Storage Solutions in the market right now uh I would like to categorize it into six of these problems the major ones the first one is data breaches for example if you store something on centralized storage service like AWS or any kind of uh cloud-based storage this is very much vulnerable to uh data breaches because it's a single

point of storage and also the access control usually lies with the storage providers itself so you can't really trust them on the security side of things and data Integrity is also a problem and this is directly linked to uh things like immutability so if a store provider wants to kind of modify your data they can just do it because they have physical uh access to the single point of failure uh Network or the place where you store the file so that's another problem and there's very limited transparency about what is happening in the storage infrastructure and this leads to multiple other

problems which include censorship where uh people can basically censor data based on the source of the data because the source is from a single point so censorship is a problem in multiple cases and uh when you use a cloud-based storage it's also custodial to third parties which means the access control the liability and everything remains with the person who's storing it and not with the person who wants to store it so this ultimately removes the powers from your users leading to various other data silos and privacy problems so this is a a very high level uh discussion on how uh how the current centralized storage

systems are not reliable enough and uh again like I mentioned it's single point of failure users privacy is under third party custody and it's also uh there's no verifiability so this makes the whole system easy to Tamper and if you are asking us why codex is intending to solve this problem and how it is intending to solve this problem we have six main value propositions again so uh the first point is decentralized codex itself is a decentralized storage Network so any file that you stored on codex is going to be stored on multiple notes in the

network rather than just one point of contact so the second point is sensorship resistance uh since the file is stored in multiple nodes this ultimately makes us censorship resistant so that uh a particular organization or region cannot censor you based on a particular parameter and uh codex is also durable this is what makes codex different from the existing Alternatives in the web3 space there's already a lot of Alternatives like filecoin uh storj RV and a lot of other projects who are trying to build a DSN but uh the point that makes CeX different from the existing DSN is durability and I'll be

talking more about it and uh again it's accessible any file that you store on codex is going to be perpetually available over time so you can access the file at any point of time uh until you have it in the storage contract codex is scalable it can scale to multiple uh sizes of storage can you can easily store files both DBS using codex and uh it's also cost effective that's the most important value proposition uh it it is very competitive to the web three storage pricing standards and U cost Effectiveness is something that we've been thinking of from day one now looking at the definition of

durability we have uh we have multiple multiple factors that contribute to this one word umbrella word called durability and some of the factors crr redundancy which makes sure that the file is stored multiple in multiple nodes and persistence which Mak sure that the file is available or is persistent for a particular period of time and incentives which make uh the node which kind of make the node operators join the Codex Network and contribute to the network by offering storage there's also availability of the file Integrity of the file so this so

many reasons around this one word durability and to know more about this the best part uh best resource that I can point to is the Codex white paper which I will be linking in the end of this slide so uh just a quick uh nutshell about how codex is different other dsns compromise either performance or durability for the sake of providing you a good experience but with codex we're trying to solve both both of it parall and uh in a nutshell if you want to uh understand codex uh the Codex architecture this is how it can

potentially look like so this a storage Network layer Marketplace layer and a peer-to-peer file transfer layer so uh the storage Network layer has storage providers which are the ones in blue and storage renters which are the ones in yellow so there's something called decentralized durability engine which kind of uh orchestrates the whole process and makes the storage Network reliable with codex and when we look at the marketplace layer this is where we have storage contracts deployed on the blockchain and these storage contracts make sure that uh the incentivization happens for uh every node operator who

stores your file and also verifies if a particular file is available over time so that's the second layer and finally we have the peer-to-peer file transfer layer and we have a distributed hash table for this and yes we will be diving deeper into the architecture in the next few minutes so looking at the storage Marketplace uh I just wanted to give you a visual uh overview of how the storage deals happen in codex so uh there are multiple M storage providers who are the ones in blue over here and there are multiple notes who wish to store data so these are the consumer applications or

any kind of node that wants to uh store some data in codex in exchange of uh some kind of monetary benefit and we also have a blockchain so the blockchain is the marketplace layer like I mentioned before and uh over here we have original data from the person who wants to store the file and uh when you deploy a St when you interact with the storage contract what happens is uh we generate the parity data and uh a storage contract is created and the person who wants to store data basically funds the storage contract which is on the blockchain and the other storage providers uh who wish to store the file

in exchange of monetary incentives store uh store the file in their uh notes by downloading the data and then uh basically the parity and the original bits move over here and there's a verification process that makes sure that the file is stored over a particular period of time and uh every time uh the verification happens a proof is generated and uh the proof of storage is submitted to the blockchain and this way uh we know that at periodic intervals when this verification happens we know that the particular node is storing file for a particular amount of time and finally after the storage

contract is done uh the pay payment is received by the storage providers and the collateral is returned so the storage providers are also asked to uh provide a collateral before they can do this and uh we do have a toonomic section in the light paper and as well as the white paper so this gives you a deeper dive into how these things work but this is a very very high level overview of how the storage Marketplace functions uh if you don't have idea about how storage marketplaces work in web3 so this is a very high level overview uh but yeah this is the link to the Codex white paper uh you can scan

the QR code to access it I'll also give you some links later in the end of the session but uh the next part is joining the test net so codex is available as a test net right now for users to build on top of CeX and also experiment CeX and to do this you can join the CeX Discord server and we have something called a codex node setup category in the Discord and over here you can just go to the step one uh Channel and then follow all the instructions over there and by the end of the six steps you will have your own X node running and this shouldn't take you more than 5 minutes uh so it's kind of easy and I'm also going to walk you

through live after this uh that's the next part of the session where we will be uh running a codex node and interacting with the node so let's go ahead and do that so uh I'm going to use the Codex docs as a reference for doing this uh you can head on to docs. codex. storage and by the way if you if you have any questions I can also help you out asynchronously on Discord or you can also ask your questions in the Google meet itself and I'll try to uh answer the questions in the end of the session so yeah you can go to docs. codex. storage uh to find the documentation or alternatively you also have uh the Codex cheat sheet which

I shared previously uh so yeah you can use either of these resources they are basically the same but uh now let's go ahead with documentation uh once you go here you can go to join codex tnet uh I mean you can just go here uh to the top there's something called setup codex with installer this is the recommended way to use codex and this also helps us with some data for uh basically to understand where people go wrong and to make the Codex experience better uh so you can go ahead over here you can read the disclaimer about what data we collect and what how it is being used and yeah once you agree to the

disclaimer you can go to the Second Step which is the requirements and the requirements over here are basically just get an npm you just need both of these things set up on your machine and uh you can you'll be able to run the Codex node but another important uh important uh block Locker for people who are in public networks is the port forwarding setup uh for example if you are in a public network like me I'm on a public network right now so I I won't be able to modify the ports or forward the ports at this point but then you can still run a codex node without put forwarding it's just that you can't

upload files uh because the discovery Port will not be working U along with the transport Port un as you forward them but you can still go ahead and uh you know do these uh instructions in this next page uh if you don't wish to uh provide any data for the Codex installer you can also set up codex manually by using this instructions this is going to take a bit of a time because uh this is going to walk you through every command step by step but over here we have a easy installer which can uh get you a codex node up and running in a few minutes so let's go ahead with the installer now so the third page has a video tutorial

as well if you wish to watch it later but uh going down we have this particular command called npx codex storage this is all we have to run uh for having our node up and running so just copy the command uh and open our new terminal I'm going to do it from the beginning so open a new terminal and once you have the terminal then me make it a bit bigger yeah once you have the terminal you can just uh hit npx CeX storage or just paste it and once you run this you should be

seeing this particular interface on your GUI uh so yeah you can go ahead with step one uh which is downloading and installing codex you can use your arrow keys to navigate around these steps but uh yeah the first step is to download and install and once you hit enter this should take a few seconds to get your codex binaries installed in your machine uh in my case I already have it installed so yeah it just tells me that I've installed it already and once you do this go back to the main menu and you can go ahead with the Second Step which is to run a codex node

and yeah again in my case I have a codex node running already in my machine so uh in your case this should ask you for your uh ports the ports that you entered over here the discovery and transport ports which by default is 8090 and 8070 uh you can just hit enter uh over here if you if you don't wish to uh you know if you don't wish to modify the default ports and yeah it should be very much similar to this you will have uh these two questions and after you answer them uh you will have a codex node up and running and after that you can you have

an option to uh couple your node along with a erc20 wallet address just so that we know who is running the node so you can simply drop your ethereum address over here if you wish to this is this is completely optional uh this is just to know who are our early stage contributors who wish to run our node so yeah this is completely optional but if you do that you can uh couple your erc20 address with the node and after that you you can also uh get the alteristic mode on the Codex Discord uh we have a separate role on our card called the alteristic mode and this role is given

to people who help us stock food uh codex in the initial stages so you can basically get it and I'll tell you how to do that and to do that you can go to the main menu again and you can go to the third option which is check codex status check note status and uh yeah ideally you should be seeing something like this uh node is online but has few peers or uh node is online with many peers but if you if you uh have a message saying node is offline you'll have to uh drop a message on Discord and we'll help you

troubleshoot the whole process and uh yeah now that we have the node online we can go ahead and view the node information so you can see it on the second option which is uh over here so you have this node ID right over here just copy it uh go to the Codex Discord and paste it on the slash sorry in the B Channel with the slash node command uh I can quickly show you how to do that uh so when you come over here where is my B

Channel yeah over here so over here you can just type SL node and drop your node ID uh in my case I already have a node associated with my Discord account but in your case it should say uh uh the node is uh coupled with your erc20 address and your Discord account and to verify this you can also go to uh test net. Matrix sorry metric. test. codex. storage and over here you can see your active notes and if you click on a particular node you can see that the node is linked to a

Discord um and you can also link it to your ec20 wallet address so this is basically all you have to do to run your own codex node uh within a matter of few few minutes and you also have more options in the main menu to uh edit your Cod X configuration so the default paths are over here if you want to change your codex uh notes location in your machine you can simply edit it over here hi Guru oh sorry can I ask a question yeah sure what what we Cur currently run is just a P2P Network or blockchain network uh So currently codex

is in alteristic mode which means that uh you can't really you can still interact with the marketplace contracts but it's not integrated in the Codex installer yet so right now you are just running the peer-to-peer network uh which kind of lets you you know share files with multiple other nodes yeah if I want to use the marketplace so uh what blockchain will will you use like arbitr or uh right now the Codex uh network is in test net so uh we just have all the contracts deployed on h ethereum sepolia test net but eventually we don't have a

choice uh as of now for which blockchain we are going to use it could also be multiple blockchains but uh ideally it should be any anything like optimism or arbitrum which has negligible gas fees but yeah right now it's just sepolia uh so test it okay and see thank you yeah I'll also yeah I I'll also give you some pointers on the marketplace side of things so once you have your node up and running you can also interact with the marketplace but uh please not that if you do that you are quite you're a lot early and uh there are a lot of things breaking down right now so you might experience errors but if if you uh wish

to contribute that's a good place to uh really focus on but yeah uh before we head there uh I'll show you the other features available in the testnet so I mean in the installer so you can also upload and download files using uh the CLI or you can also use the Codex app which I will be using right now uh so you can hit the fifth option uh which should take you to the Codex app or an alternative could be just just to run your node and go to app. codex. storage uh this is the same so you can go over

here and uh yeah you can just give a preferred name and once you have that you will see a health check over here which basically checks if all the requirements are met so in our case uh the internet connection and CeX connection are available because I have a CeX node running uh if you don't have a codex node running and if you go to app. codex. storage this should uh be uh this should not be checked it should be incomplete but U yeah since we have the first two steps done uh shows me completed and the third and fourth steps are for put forwarding and Marketplace so port forwarding requires you to uh

basically uh forward your ports on a router like I mentioned over here in the docs so you can watch YouTube tutorials on how to do port forwarding but right now I'm on a public network so I won't be able to do that but it shouldn't be hard for you to set it up it should again take you like a minute or two so yeah put forwarding is another requirement uh if you want to share files with other people and finally the marketplace is still U still Alpha so you know there's a lot of things breaking down but I will show you the marketpl contracts and also the apis later but now let's try uploading and downloading the file files and

generating a CID for a particular file so to do that just go to the next step and then you should see this dashboard in front of you and uh right now I don't have a pier connection but then um that's because uh I don't have the port forwarding setup but anyways I can just show you how to upload a file so you can pretty much uh select any file let me select this particular file so so yeah this is uploaded to find the CID I can go here to files and in the files I see the list of all the files that I've uploaded into the test net so this is the CID

pertaining to the particular file that we uploaded uh just copy the CID and if you have port forwarding set up this should a potentially help you share files with other peers so uh for example if if you are running a codex node and if I have port forwarding set up already uh I can just share you the CID and you can go over here uh and paste it over here in download section and download the file uh you also have the download section over here I guess yeah over here so let me try downloading this from a local node but another thing that you have to notice um the file name this is basically a bug in the uh front end

application but then uh the file name does not automatically get stored over here so you will have to you know manually save the file uh but once you do that you'll be able to see the file stored uh so in my case I think that was a PNG let me just check uh yeah it's a PNG let me just say uh downloaded file.png when I open this yeah this is downloaded so this is a minor bug that needs to be fixed with the with the interface but then when you use the CLI this should uh

automatically download the file with option six and seven this will download the file with the proper file name and the file extension but yeah that's pretty much about uh what codex is right now till step seven uh you can view your local data by going here this has all the data available in your local node and uh if you wish to uninstall codex just hit n step nine and this will uninstall codex from your machine so that's all about the installer that we have and finally if you have any feedback it's really valuable to us to improve your codex experience so hit this 10th option it will show you a

simple form that asks you for your feedback and that'll be really helpful for us in making this experience better but now that we have a codex node running I'll go ahead and show you what are the different other things that you can do with codex uh so when we look at the documentation we have the first three parts completed also the fourth part completed with uploads and downloads uh after you complete this you have this what's next session section uh where we have the Codex test apis that can help you interact with your codex node uh I'll take you through the Codex test apis

firstly U it's available at api. codex. storage uh you can go here to see all the list of apis that you can uh use for interacting with your local node so uh the marketplace section has all the apis that can be used for interacting with the marketplace contracts so uh this is a lot experimental than the other ones uh so yeah let's go ahead with the second section First Data which has end points for basically uh uploading files in a streaming Manner and also downloading files from the local node and downloading files from the network

to the local node so you have multiple apis available for this and it's pretty simple well documented uh the apis have work worked very well for me so I'm I'm expecting it should work for everyone's so we also have a not section where you can uh get the nodes PR ID and also a debug section where you can get the node information for example this end point should show you all the no information yeah that's all my node information uh but yeah that's pretty much for the API and uh codex has a very new JavaScript library or a typescript library it's it's pretty new we don't

have much of applications built on top of it uh I'll show you the reposter for that it's this one yeah so uh codex JS uh is our first SDK that we have and uh we have maybe one or two applications built using the Codex SDK and we're also working on making the SDK a lot more better so you can also use the SDK directly without having to look at the apis uh yeah it's all well documented in the uh read me section of the reposty uh and this is the link to the reposty if you want to check it

and now that we are done with that I'm also going to show you an application that I'm personally building on top of codex uh so so it's called share. Haack guru.com this is a file sharing app that I'm trying to build just as an example for people to understand how codex and vaku can work together so uh I remember mentioning this project called vaku when uh I was showing you the free. technology portfolio and vaku is the communications protocol and uh codex is the storage protocol and we look at e uh I'll just show you a image of the

ethereum white paper itself yeah this is a great image that I can potentially reference yeah so ethereum as a white paper had ethereum just for the consensus layer but to ethereum to work uh efficiently it has complimentary Technologies like swarm and Whisper so all these three Technologies together uh formed ethereum itself in the ethereum white paper uh so ethereum is the consensus layer basically the onchain layer and swarm is the P2P file transfer

layer or the basically what codex is right now and there's also other Alternatives like ipfs who do content based hashing and storage and also so codex who is which which provides you with better durability and uh there are multiple other DSN who do this so this is the storage layer and Whisper is the communications layer uh for epimeral or dynamic Communications that you can use so uh imagine this to be a network of sockets that's that's how I like to explain codex sorry waku so yeah all these three together can help you build

a decentralized application uh that's how the ethereum white paper was proposed and that's how it was meant to be and vaku is a cool technology it's you can learn more about it at vacu.org uh where you can kind of build a privacy focused uh and securely scalable uh Communications infrastructure for your applications and in this application called file share uh that I'm building right now I've used vaku along with codex to create a room based file sharing so if if both of us are in the same room like let's say both of us are in xyz1 two 3 room or maybe even more maybe everyone and this call are on the

same room I can basically drag and drop any files over here to share the files with other peers who are connected with me so that's the intent of this application I haven't completed it fully but uh uh if you already follow codex and waku socials on Twitter you will be seeing a block post coming out in the next couple of days after I complete this fully but yeah that's how it is supposed to work you can go here add your codex API uh endpoint uh which will be active after you run a codex node and you can also uh configure the vaku settings so in in terms of vaku if you need a if you use a right node

configuration you don't have to do any settings so yeah you just have to run a codex node come to share. hack.com and then uh select any file to share uh let us let us try sharing uh maybe the same file yeah so after I select the file you can see that the file is in my send files section over here and when I copy the CID this should copy the CID and the best part is since the file is the same file the CID won't be duplicated just like ipfs or any other content based storage uh this makes it uh makes files uh immutable as it's

content based it's hash content based so that way uh file tampering is a is not possible for a particular C so yeah that's about the send files part and people who are listening to the same room ID we'll have this file on the uh received files part but uh this is a cool application that you can look at for uh understanding how to implement codex in an application perspective using the Codex apis and there's also another application that my colleague is building it's called quu Uh quu means questions and answers powered by waku so

this also uses waku and codex uh under the hood so uh you can pretty much create question and answer sessions using this uh like for example if I want to get a list of q&as from this particular Google meet I can just create a link and share it over there so that people can ask questions using quu and I can just answer them using this interface uh but we do have a problem going on for the the last couple of days uh with waku uh the waku fleet is going through some updates so it's kind of not reliable at this moment um so yeah like I just have four vaku Piers connected

right now it should work because I have four peers connected but then um I think by next week after the updates are done this should be a lot more relable in terms of uh yeah sharing files but that's how both these applications are designed to be waku for the communications layer and codex for the storage layer so basically what vaku uses over here is the metadata of each and file each and every file that you store on codex so uh the maximum F you know message size in a vaku object can be one megabyte so this file is can be probably more than a

megabyte maybe like 5gb so if I want to share this file I first sh store it on codex and I share the CID of the file on vaku so that's how the architecture looks like for communications along with file sharing so yeah uh I will also show you a cool react hook that you can use uh this is available in my GitHub yeah it's called codex waku example again this is very new so expect some bugs and errors to pop in every now and

then uh so when you go into the hooks folder you will see something called use waku and use codex so these are two good hooks that you can use uh if you are VI coding using AI these qu Snippets are going to be super useful so in my case I'll show you use codex uh so yeah this is a simple book that kind of helps you oh it's it's not over here but then you can find it on the code base uh we have codex. probably over here yeah I'm guessing it's over here so what basically happens is we

use API . codex. storage over here we use these uh endpoints yeah this particular endpoint is for downloading a file and this is for uploading a file so let's uh let's look at where this particular code is I have my vs code open anyway cursor open so yeah I'm not sure which particular end

point that I was using but it should be somewhere with V1 data yeah found it so this file has all the code that you would require it's in index. uh TSX I haven't put it into use codex. or TSX yet but then it will be done later in the day but uh yeah you can see example Snippets of how to store files over here so this particular endpoint can simply help you upload and download and it's pretty simple uh you can you can just kind of understand it from one file but anyways that's that's how you can build

stuff on top of codex and let's go back to the documentation to see if I missed something uh yeah so that's the rest API part and we have the marketplace support uh so you can run codex with the local Marketplace support by following the instructions over here uh you'll just have to run a couple of commands to get your local Marketplace set up and then you can interact with the marketplace contracts and once you have this setup that means that you have a completely working piece of uh you know working piece of peer-to-peer Network along with uh Marketplace that helps node operators uh you know store your files and get

incentivized for it so that's the second part that you can second thing that you can do after running your codex node and finally you can build the applications using codex JS library that I showed you earlier so yeah I think that's all about codex for now uh if you have any more questions you can always reach us to uh reach us on Discord and we'll be happy to help and uh if you are uh if you wish to dive even more technical you can read the tokenomics light paper uh which is right on the left side uh yeah this gives you a complete overview of how the Codex toomics work how the incentivization structure is different

from the other available Alternatives in the storage uh side of dep three and if you wish to go on a a deeper technical overview you can look at the white paper which is the Holy Grail for understanding how uh codex Works in terms of uh the decentralized durability engine and stuff uh also codex particularly to State some highlights of how CeX is different from PFS and filecoin uh codex uses eraso coding uh instead of uh instead of whatever filecoin uses like proof of replication proof of proof of space time and all the all the other things but uh codex uses

aasal coding for making sure that the files are redundant in the network and the files are also uh make not corrupting and it's automatically repairing even when you even when there's some problem s in the network so that's uh one difference and the other differences include things like store uh garbage collection for example so uh in ipfs if you don't access a file for more than 30 days the file simply disappears so imagine you meant an nftd and after you don't access the nft for 30 days the asset is completely gone from ipfs so

that's that's how non durable ipfs and file coin are and with codex we focus on filling these gaps to make sure that uh it's a more reliable DSN yeah so that's all about it from me if you have any questions I'll be happy to answer them now or you can also ask the questions in the Codex Discord and I'll have my team help you over there group yeah uh very amazing job yeah I have a question is that you say that uh

it use uh event code to keep the data uh uh durability yeah so uh it you need a run many notes yeah many many notes like usering yeah usering not keep the blob data so there are there are many nodes running so how how can you uh encourage I think you need to encourage in love developers to run the notes yeah if you want you use eval code yeah yeah so uh to answer this I see the the

question has two subsets the first one is how erer coding can be implemented I believe and for this I just did a explain a tweet on how erao coding works I just sent a link on the messages over here so that's a very high level overview of how AO coding works but yes uh for the Codex Network itself to evolve and provide better storage uh we need a lot of node operators to join codex and run nodes to for storage and uh yes the main net launch is scheduled later at the end of this year so right now most of the things that happen in codex are pretty new and we don't have

any incentivized test net as of enough so there is no use of people running uh and offering storage at this point uh but yeah like once we have the incentivized test net and the main net I feel like it's going to be really really attractive for people who have infrastructure to offer storage so basically another explanation could be uh this consumer side of CeX where people create the demand for data and there's uh the node operator side of codex where people store data that is

coming from the demand so the challenge for the Codex team is to grow both of it uh yeah so only when the consumer demand grows up the demand for storage operators will grow up so it's like a proportional growth that we should be looking at than yeah yeah let see answer questions do you think if work could use codex to build a decentralized communication T um

is it very expensive for user yeah so uh we did sponsor a lot of hackathons with waku last year uh for example we had 81 projects that were on top of vaku I can also share the link to these projects but basically basically the problem that most of the projects had was storage uh with waku you are not supposed to share big files because it's just a layer for communicating metadata or like a small Json object or something that's less than a megabyte uh so yeah the best way to share bigger files is by using codex as as a storage layer and you just share

the metadata on waku so example in this awesome waku repos that I linked we have like 85 projects that use waku and out of the 85 at least 25 projects needed a you know some kind of storage solution so that explains that there's still demand for [Music] storage oh anything else that's it cool guys anyways if you have any

questions again feel free to join the Codex Discord shoot your questions over there and thanks for having me for today yeah thanks for thanks for your excellent presentation to tell us how it works and how these projects or your ecosystem work together it's pretty nice um yeah thanks for presentation and uh all of our audience joining this presentation thanks a lot yeah thanks I know whether do you write it on my computer now okay yeah I'm excited to see your note on the network cool then have a great rest of your

evening bye-bye