Draft
Conversation
Contributor
Author
|
@KiChjang, this is the RFC, the possibility of which we spoke of long ago in Matrix. Could you please take a look? @franciscoaguirre @xlc Please take a look as well 🙏 |
xlc
reviewed
Jan 19, 2024
| 3. Are the proposed metadata format and operations general enough? | ||
| 4. Could the proposed instruction set be reduced without losing both generality and convenience? | ||
| 5. How one could easily pay for the execution of the `ModifyMetadata`, `ApproveMetadataModification`, and `NoteMetadataModificationApproval`? | ||
| 6. How to make the `MetadataMap` bounded? The same question for `MetadataKeys`. |
Member
There was a problem hiding this comment.
the simply way is define max key length, max value length and max number of keys
another ways is not define anything here, but depends on the overall XCM size limit
12 tasks
paritytech-rfc-bot bot
pushed a commit
to polkadot-fellows/RFCs
that referenced
this pull request
Jan 24, 2025
This is a refined version of the XCM Asset Metadata RFC. This PR supersedes the [PR](polkadot-fellows/xcm-format#50) opened in the xcm-format repository following the migration of XCM RFCs to the Fellowship RFCs. ## Summary This RFC proposes a metadata format for XCM-identifiable assets (i.e., for fungible/non-fungible collections and non-fungible tokens) and a set of instructions to communicate it across chains. --------- Co-authored-by: Adrian Catangiu <adrian@parity.io>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a preliminary version of an RFC describing the metadata communication of asset collections and asset instances (i.e., NFTs).
It is by no means final. Instead, it provides a base for a more formal discussion.
Improvements, discussions, and any other input are enormously appreciated!
The preliminary version of the RFC was requested to be posted during the discussion of the Unique Network's XCM NFT proposal.
The RFC is meant to evolve over time.
RFC Summary
The proposed change provides a general way of communicating metadata of assets and asset instances between consensus systems via XCM.
Currently, there is no standard, general, and easy way to do so.
Communicating metadata enables new cross-consensus use cases for NFTs and might simplify the registration of foreign assets (both fungible and nonfungible).