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 contracts that use ChainHub seed it using chainInfo and assetInfo from privateArgs. This is more recent development from using vstorage, and was introduced in #10329 and #10571.
In order to wrangle brands, it uses brandKey to provide a DenomDetail.brand using the issuerKeywordRecord. This is a bit hacky when we have other tools at our disposal, namely:
0xpatrickdev
changed the title
orchestration / fast-usdc: remove brandKey from assetInfoprivateArgs
orchestration / fast-usdc: remove brandKey from assetInfo in privateArgsNov 27, 2024
What is the Problem Being Solved?
Orchestration contracts that use
ChainHub
seed it usingchainInfo
andassetInfo
fromprivateArgs
. This is more recent development from using vstorage, and was introduced in #10329 and #10571.In order to wrangle brands, it uses
brandKey
to provide aDenomDetail.brand
using the issuerKeywordRecord. This is a bit hacky when we have other tools at our disposal, namely:#10329 (comment)
Description of the Design
brandKey
no longer appears in privateArgs forfast-usdc
,send-anywhere
,basic-flows
, orauto-stake-it
contractsregisterChainsAndAssets
:assetInfo
that already containsDenomDetail.brand
brands
argumentSecurity Considerations
Scaling Considerations
Test Plan
Upgrade Considerations
The text was updated successfully, but these errors were encountered: