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
Given we are able to compute the ibc denom for a new qAsset on another chain deterministically, we should automatically do so for at least the host zone, and osmosis (perhaps all chains for which we have a connectionData?) at the point of zone registration, in the same way we do for LocalZone and for ConnectionData.
The text was updated successfully, but these errors were encountered:
see x/particpationrewards/keeper/hooks.go: AfterZoneCreated method.
This creates ConnectionProtocolData, and LiquidAllowedDenomProtocolData for the Quicksilver zone.
We want to additionally create LiquidAllowedDenomProtocolData for:
host zone (zone.ChainID)
osmosis (chainID from OsmosisParamsProtocolData) (we don't want to hard code this, because it won't be correct for testnet)
umee (chainID from UmeeParamsProtocolData) (we don't want to hard code this, because it won't be correct for testnet)
You'll need to fetch these PDs and decode them to fetch the ChainIDs; you'll want to fetch the transfer channels from ConnectionData for these zones (post #1459 completion) and use the DeriveIBCDenom in utils to determine the denom.
Summary
Given we are able to compute the ibc denom for a new qAsset on another chain deterministically, we should automatically do so for at least the host zone, and osmosis (perhaps all chains for which we have a connectionData?) at the point of zone registration, in the same way we do for LocalZone and for ConnectionData.
The text was updated successfully, but these errors were encountered: