[DAO:bc3be0f] Scene Metadata vs Land Metadata

by 0xb7ee502c4dadcc9a62934b02c5f8decbbfa32c48 (kourtin)

As Decentraland gets more attention from creators and brands that want to hop into the metaverse, builders struggle to promote it properly through the Events feature of the platform when it comes to pre-promote scene builds or deploys happening in the world.

While I believe there is a valid reason for land to have its own metadata (title, description…) as it helps on the land market, I find it not useful at all to have the Events location to grab the information of the land instead of the scene deployed. This usually leads to confusion among users, creators and brands that see how from the Map Atlas they see their thumbnail, name and creator properly showcased but from the Events page it takes the data from the state they are in.

My proposal is to change the Decentraland Events behaviour and grab the data from the scene deployed in the selected coordinates and not from the marketplace land metadata and make the Events location clearer.

  • Make Events grab the Scene Metadata
  • Keep it as it is (Grab Land Metadata)
  • Invalid question/options

Vote on this proposal on the Decentraland DAO

View this proposal on Snapshot

Isn’t this how it already works? The name and thumbnail shown for a piece of land is taken from the scene.json file of whatever scene is currently deployed.

No, currently the location data is taken from the Land metadata, same shown from the Land market.

Scene.js currently doesnt interact with the events page

Looks like this is not a plausible option based on the votes. I wonder if anyone can explain why this wouldn’t be possible.

Scene Metadata vs Land Metadata

This proposal is now in status: FINISHED.

Voting Results:

  • Make events grab the scene metadata 71% 844,170 VP (51 votes)
  • Keep it as it is (grab land metadata) 1% 15 VP (5 votes)
  • Invalid question/options 28% 340,807 VP (10 votes)

Scene Metadata vs Land Metadata

This proposal has been PASSED by a DAO Committee Member (0xbef99f5f55cf7cdb3a70998c57061b7e1386a9b0)