 Yeah, hello everybody, my name is Chi-Jo. I'm the founder of Issa Storage. Today I will be going to present our talk on the future of Raspberry, paving the way to the fully Android and fully decentralized web. So what is the current status of decentralized web? So we have a decentralized access protocol, like IPFS. And we also have a mature P2P network layer, in which we are able to retrieve the data. And we also have the incentivized storage layer that has to keep the data consistency. However, there are still great limitations of current decentralized storage solutions. First, those storage solutions has a great limit on the semantics in many work for static files, which means that it's very inefficient to update and delete those existing files, even just a single byte that is changed. And then further, there's no way to compose this data in a decentralized way. So sometimes we have to rely on centralized server. Second is that all these projects, they have their ecosystem, which means that users has to use their wallets, tokens, and addresses in order to be able to upload those files to their systems. So with these problems, we are projecting what features that we need in the future web 3. First, we need rich storage semantics in the decentralized storage, which can support create, update, delete, blobs for very large amount, potentially petabytes. Further, it can be programmed by smart contracts so they can easily compose our data with the large of the smart contracts running on Ethereum. And second is that we want to simplify the user body, which means that the user, just using the Ethereum wallet, pay Ethereum and is able to upload and basically store large amount of data on top of the whole Ethereum network. And lastly, we need to have a new access protocol that is able to render those dynamic data from end to the blockchain and storage without any centralized identity. So what's the solution? Thanks to the latest development of Ethereum technologies, we believe that we are now at a position that we can achieve these goals in the near future. First of all, we have data availability thanks to thanksjotting, which greatly increase the data upload speed using advanced cryptographic primitives. And second is that we are able to build external data retention network so that we only store corresponding metadata on Ethereum and be able to store large amount of data in this layer 2 network. And we just periodically submit the proof of storage into the Ethereum mainnet so that it tells that everybody can check the actual data, the latest data is kept in the network with high replication. And lastly, we also develop a Web3 access protocol, which is able to decentralize access both web objects hosted by smart contracts. So this is a Web3 access protocol, which is defined by ERC4804, which is a way to render web objects hosted by smart contracts. It's very similar to HTTP so that it can inherit all the good benefits of HTTP while we are able to identify a resource that hosts by smart contract and further access the underlying storage layer that we built. And the user storage is a layer 2 solutions that aims to scale Ethereum storage rather than computation. And so here is a quick comparison of what is storage can do versus Filecoin, ORI, and the default storage solutions of Ethereum. And with this infrastructure, we believe that we are able to enable a lot of new applications. For example, trusted website hosting like Uniswap Curve or Dynamic NFT, which we are able to change the presentation of image dynamically. And we also be able to build decentralized social network, such as decentralized Twitter, Medium, or even decentralized job box. So here I will give a demo. Let me see. OK. This is my Firefox browser that supports Z3-VML. So now type in Z3-VML. Mr. Store the unit eth that we registered at Uniswap points to the smart contract that hosts our front end. So all the images HTML, CSS JavaScript now hosted by the smart contract returned by this web straight access protocol. So there are also a couple of interesting examples, for example, decentralized job box. So this is also a homepage that returned by smart contract, another smart contract. And we can see, I can see them on the list. All the prints found have been uploaded before. And in order to upload a new file, what I should do is just check the file. And then it will ask me to sign a transaction while I might not ask. So during the whole procedure, you don't need to require any additional two, such as CLI. And once the transaction is confirmed by network, I can access the file also via web straight access protocol. So the file has been uploaded, so we are able to access so it's still a gateway, but we can still use the web straight access protocol. And the corresponding file is also updated according to thanks to smart contract. So this is an example for decentralized job box. There are also a couple of other examples like Webstraining, decentralized blog, dynamic NFT extension. So welcome to play. Yeah, so there are a lot of more details of our technology that are built. So we have a party this afternoon in the nearby Hilton hotel for you to come. I'm happy to answer any questions. Yes, you listed four. You've made comparison for systems, but you forgot to mention SWARM. Yeah, actually I talked to SWARM people a few days ago. So SWARM actually has a similar architecture as FFS, which is using a content addressing to basically locating a file. And also it has a way to basically call dynamic hash to be able to locate a latest version of file. But at the same time, right now I don't think it has the programmability with the smart contract, which is able to modify and able to compose all the data purely on chain. And there's something we really want to enable. And second is that or who the design is using easier. So basically the data providers will be paid by the user. And also the users will pay the user to storage those content. So it's a highly coupled with the theorem with basically native support.