Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow modifying the optional metadata of Confidential Assets #1985

Open
dbadol opened this issue Jun 16, 2024 · 0 comments
Open

Allow modifying the optional metadata of Confidential Assets #1985

dbadol opened this issue Jun 16, 2024 · 0 comments

Comments

@dbadol
Copy link
Contributor

dbadol commented Jun 16, 2024

From FR in https://forum.beam.mw/t/fr-dynamic-asset-text-archive-data/463

Current situation
This is the metadata used to create a Confidential Asset:
https://github.com/BeamMW/beam/wiki/Asset-Descriptor-v1.0

Currently, none of these metadata fields can EVER be modified once the CA has been created.

However, many of the OPTIONAL ones are dynamic and should not be set in stone, on-chain forever. Fields such as website, link to whitepaper, link to logo, link to favicon, etc. should remain open to modification as they depend on off-chain infrastructure (domain names, web hosting, etc.).

Proposed solution
Allow the creator wallet to register new values for the following optional metadata:

OPT_SITE_URL (website link)
OPT_PDF_URL (PDF whitepaper link)
OPT_FAVICON_URL (favicon PNG link)
OPT_LOGO_URL (logo SVG link)
OPT_COLOR (HEX color)

We note, that the previous values of all these fields would still be registered in older blocks. So the whole history of changes would always remain visible on-chain.

Alternative we've considered
The following two fields are also optional ones, and we could decide to allow modifying them A clear and concise description of any alternative solutions or features you've considered. To be discussed...

OPT_SHORT_DESC=CA short description
OPT_LONG_DESC=CA long description

Remarks

  • An fee amount could be required for such changes. To be discussed...
  • An update to the Beam Asset Minter DApp front end (and also smart contract?) would also be needed.
  • Would this change require a hard-fork?...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant