Add: Multiple attestators to same Rank NFT #56
Closed
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
3 tasks
|
peersky
changed the title
peersky
changed the title
peersky
force-pushed
the
18-factory-registry
branch
from
897fc96
to
9afa813
Compare
4 tasks
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.
WIth completion of #62 it is now possible to create multiple subjects that correspond to different Rank NFT asset minting privilege.
As we go forward, this brings a ux question of supplorting multiple subjects with absolutely identical subject. Technically right now it is possible, to create two Rank Token NFTs, with identical subject.
With this ticket, we want to create token such that it can work for every subject, but will avoid duplication of Rank NFTs.
This means that there will be one Rank NFT endpoint that can mint tokens for unlimited number of instances. Following is needed:
instantiateworkflow should be able to recognize already existing instance and attach to it another instance