asset: add asset.v1.Metadata.priority_score
#4441
Merged
Conversation
This file contains 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
This is intended to help support clients that need to display lists of assets. An asset registry can assign rankings to tokens, and frontend software can consume them without needing to have its own opinions about what the ranking should be. For instance, a registry could have hardcoded "tiers" or priorities, or priorities assigned by market cap, or the user's balances, etc.
erwanor
force-pushed
the
metadata-priority-score
branch
from
5175e6f to
085539c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Describe your changes
This is intended to help support clients that need to display lists of assets. An asset registry can assign rankings to tokens, and frontend software can consume them without needing to have its own opinions about what the ranking should be. For instance, a registry could have hardcoded "tiers" or priorities, or priorities assigned by market cap, or the user's balances, etc.
Checklist before requesting a review
If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason: