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
Orchestration has to work with arbitrary Cosmos interchain denoms. There could potentially be thousands in a user's account.
Offer safety for with a denom requires creating a brand and issuer. They must be canonical so hold in a single central vat. Creating and holding them is expensive enough that thousands would spam that shared resource and be an attack vector.
Description of the Design
Provide some other mechanism for offer safety with denoms. One aspect could be incremental provisioning of the necessities for offer safety, such as lazily creating the issuer. Another aspect could be gating, such as having an electorate to approve spending the shared resource or charging the spender of the shared resource.
What is the Problem Being Solved?
Orchestration has to work with arbitrary Cosmos interchain denoms. There could potentially be thousands in a user's account.
Offer safety for with a denom requires creating a brand and issuer. They must be canonical so hold in a single central vat. Creating and holding them is expensive enough that thousands would spam that shared resource and be an attack vector.
Description of the Design
Provide some other mechanism for offer safety with denoms. One aspect could be incremental provisioning of the necessities for offer safety, such as lazily creating the issuer. Another aspect could be gating, such as having an electorate to approve spending the shared resource or charging the spender of the shared resource.
Another aspect is reducing the scope of brand:
Security Considerations
Scaling Considerations
Test Plan
Upgrade Considerations
TBD what upgrade this is a part of.
The text was updated successfully, but these errors were encountered: