You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use the bank module to keep track of the value owner of a scope.
Problem Definition
Scopes have to be read and written in order to update the value owners which causes a lot of unneeded read/writes. There are several operations that only update the value owner, though, that could be made much cheaper by extracting the value owner into its own record. Further, things like quarantine and sanction should apply to scope value owners too.
Proposal
Use the bank module to record the value owner of scopes by giving each the denom "nft/", e.g. nft/scope1qzge0zaztu65tx5x5llv5xc9ztsqxlkwel.
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged
Contributor assigned/self-assigned
The text was updated successfully, but these errors were encountered:
More complex metadata module since it'll now be using/managing bank state too.
This would be a reason to not convert existing endpoints to their bank managed counter parts... I guess that still doesn't let us simplify this away though because creating a scope means minting the token with the bank module as well...
Summary
Use the bank module to keep track of the value owner of a scope.
Problem Definition
Scopes have to be read and written in order to update the value owners which causes a lot of unneeded read/writes. There are several operations that only update the value owner, though, that could be made much cheaper by extracting the value owner into its own record. Further, things like quarantine and sanction should apply to scope value owners too.
Proposal
Use the bank module to record the value owner of scopes by giving each the denom "nft/", e.g.
nft/scope1qzge0zaztu65tx5x5llv5xc9ztsqxlkwel
.For Admin Use
The text was updated successfully, but these errors were encountered: