Ethereum Foundation DevCon 6 - Developer Infrastructure Track, 16 Oct 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Using IPFS to Create a Metaverse by Agustina Aldasoro | Devcon Bogotá

Description

Visit the https://archive.devcon.org/ to gain access to the entire library of Devcon talks with the ease of filtering, playlists, personalized suggestions, decentralized access on Swarm, IPFS and more.
https://archive.devcon.org/archive/watch/6/using-ipfs-to-create-a-metaverse/

Leverage the decentralized IPFS network to scale content storage management for a Metaverse implementation.
- Manage all assets storage and remove S3 dependency
- Navigate through the Metaverse Assets changelog history
- Ownership validation based on Ethereum blockchain
- Strength the network and decentralization by fostering the community to contribute with nodes
- Remove the complexity to manually implement content synchronization on the network

Speaker(s): Agustina Aldasoro
Skill level: Intermediate
Track: Developer Infrastructure
Keywords: IPFS,metaverse,content

Follow us: https://twitter.com/efdevcon, https://twitter.com/ethereum
Learn more about devcon: https://www.devcon.org/
Learn more about ethereum: https://ethereum.org/

Devcon is the Ethereum conference for developers, researchers, thinkers, and makers.
Devcon 6 was held in Bogotá, Colombia on Oct 11 - 14, 2022.
Devcon is organized and presented by the Ethereum Foundation, with the support of our sponsors. To find out more, please visit https://ethereum.foundation/

A

A

And during the last two years, I've been contributing to the Sunderland and today I'm going to talk about using ibps to create the metaverse. So let's first talk about what the meters is. Well, it's a social network where you interact with friends, people that you meet there in a three-dimensional way, and also there you have a digital identity which is customized. Custom is custom for you and it's your the way that people recognizes you.

A

um What distinguished the central from other metaverses is that the users are the ones who owns the platform right. So how do we do that? Well, the world is divided into parcels and each parcel has an owner and is the owner. Who decides what to show on the on the world they could chose to set up an essene, for example, for a casino for a bar or even a music festival, and how we do that. We have deployed contracts in ethereum to check the ownership of those lands on the worlds and to check the ownership.

A

We use the graph in the backend services. um So we have the the contract for lands which, where you can own a Land and then let others have permissions to deploy some scene on the world.

A

We also have nft collections as well, where the wearables creators can meet a collection and then sell them in the marketplace, and then you, as a user, you can choose those wearables, buy them and then set up your uh your avatar and that's where we store them in the users profiles and we, you can also have a name in the sand run and that's like the identity that you own right. What happened with that?

A

There are a lot of files and it's a it's too many assets to store scenes and free models and well some pictures. So we need to store them in somewhere and we have to delete that the centralized right. So what we have are the centralized servers. We just store all the data that the client needs to to run right. The community owns the the servers, which means that there is a there isn't around Dio, which is a responsible of approving the list of servers that that are in the Dao.

A

So they they have to synchronize between them, because we have all the content replicated on each of them, so the client can connect to any of them and we'll get the same information right.

A

um The way we do, that is every every server which we name catalyst is doing a polling mechanism to all the others, to retrieve the files and the entities, and this works okay, but we wanted to go a little bit further and test two things. The first thing is that, as you may assume, we have lots of data and we have like the only historical data like all the changes that have happened on unseen and also the way that the files are replicated together. Well, let's first talk about the historical data.

A

What happens? For example, this is the Genesis Plaza for the sandran, which was away in 2020, and there was a change in 2021, so the servers need to retrieve the content, the latest content. They don't need to serve the. How was the sundran two years before right, but we want to store that data as a backup and for, for example, if you want to run the world how it looked a year before, if you run a full node, which means that you have all the historical data.

A

All you need to do is enlarge your disk and everything will work. Okay. The only thing is that you will need two terabytes of of disk, but if you want to run a light note, then we you can enable the garage collection, which is a mechanism that deletes all the all the files from the entities that were written by new ones, right, okay, but what happens? If all servers then enable garage collection, then we may lose those data and we don't want that.

A

So our idea was to set up a node, an ebfs node connected to a server which listens all the network and listens all the changes and stores well pins to ibps all the files that are synchronized. So, first we uploaded all the all the files and now and then um we set up the server to listen all the changes and automatically pins the new files, and the other thing is the files replication which we. What is that? Well, the way that we share those files between the servers?

A

We are doing it by HTTP request and it's a full match, topology right, because every node is talking to every other node.

A

um Oh I think I was well what what happens if we use ibps and we leverage that so we don't have to care about synchronizing files. We only have to care about the evaluations that we need to do to the blockchain and the entities and the way that we need to retrieve those files, but we con. We only would need to know the hashes that we need to pin and then all of that part themselves. So that's our idea on a trial to to make something different um test.

A

If we can Leverage The ipvs to work that um that's.

B

All thank you, I was just wondering. Could you speak a little bit about your decision to use ipfs instead of RV for storing historical data instead.

A

B

Weave for like permanent data to store like historical data, we.

A

We currently have the the data stored locally, like in the file system, and we have the the way to configure that and store. If you were running out and want to store them on as free you can. We have been thinking a lot about the way that the catalysts sing each other and we've been assigned a lot. How ipvs does that? So that's why I think we chose ibps to test this, um but we have done so far. It's only the historical data right we haven't done, used the ipvs to run the sync.

C

How do you handle content, moderation or cases where, like certain content or files, might be illegal in certain countries, but would be valid in other ones?.

A

Well, the way that way now is each of the servers has an owner and it's there's a responsibility to deny list some entities or files, or they think that they need to moderate. So we I we are. We are not taking care of the moderation ourselves, we're letting the owners of the Catalyst do themselves. We we only provide the mechanism for them to to remove to remove those files and don't serve them.

C