-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Develop more RGB21-interfacing schemata #8
Comments
Proposed schemas make sense to me. Moreover our team would like to propose a change to the RGB20 interface. By adding optional medias and previews it would be possible for us to implement a schema similar to our previous RGB121, that we propose to name CDA (Collectible Digital Assets). |
@zoedberg we had this discussion with @fedsten and @giacomozucco back in 2020 and they were proposing to have fungible token media not be a part of the contract. The reason for that is that they are volatile, and may be provided by different vendors (for instance dark backgrounds may require different assets, or they may take different sizes, shapes etc). Thus, RGB20 does not include media for tokens - and instead, it should be a part of non-committable data (like Supplement). |
I must admit that I do not remember much of our 2020 discussion, but I do believe there are several use cases that we may not have considered at the time. For example security tokens may want to attached scans of analogically singed legal documents and/or visual representations of the real world asset (e.g. the cadastral plan of a real estate asset, the picture of a tokenized physical artwork etc). Personally I do not see any drawback in adding an optional media attachment, but in not supporting it I see the risk of limiting some potentially interesting use cases. |
I propose to continue the discussion on RGB20 changes in https://github.com/orgs/LNP-BP/discussions/160 where it belongs (since it is a change to the standard and not a question of RGB21 implementation). |
Main challenge: implement proper AluVM verification scripts
The text was updated successfully, but these errors were encountered: