Closed jamiehewitt15 closed 8 months ago
Details to hash out:
What about ENS names that point to a data token address? E.g. /asset/dataunion.eth or /asset/trepel.eth or whatever the user decides they like.
Something came out of prototyping and we accidentally created decentralized publisher URLs in the market based on ENS names, so covering human readable URLs. For the publisher, not the dataset but can't have everything 😄
See https://github.com/oceanprotocol/market/issues/858#issuecomment-921725530
@kremalicious The ENS names work great in the URLs for the profile pages. I can see that there could be a route to doing the same thing for assets in V4. If the asset URL points to the address of the asset NFT then the publisher would have the option to customise the asset URL with ENS
not gonna happen in v4 release, we have bigger things to do
From a marketing and branding perspective it would be great if we could implement human readable URLs.
At the moment publishers have to share very ugly looking URLs when they are promoting their datasets, for example:
https://market.oceanprotocol.com/asset/did:op:7Bce67697eD2858d0683c631DdE7Af823b7eea38
For the publishers it would be better if they could set their own URL slug. For example:
https://market.oceanprotocol.com/asset/dataunion
This would require us to have a mapping between the domain slugs and the dids. It will also require us running a check to see if the slug is unique when the publisher sets it.