search

0xpatrickdev / agoric-vault-collateral-proposal

CoreEval Proposal and Permits for Inter Vault Collateral Type
0 stars 3 forks source link

use correct denom for emerynet, mainnet #1

Closed 0xpatrickdev closed 11 months ago

0xpatrickdev commented 1 year ago

this cannot be populated until there is a channel between agoric and stride. using ibc/toystatom for now.

# trace atom denom
$ agd query ibc-transfer denom-trace ibc/BA313C4A19DFBF943586C0387E6B11286F9E416B4DD27574E6909CABE0E342FA --node=https://agoric-rpc.polkachu.com:443
> denom_trace:
   base_denom: uatom
   path: transfer/channel-5
# determine hash from atom trace
$ agd query ibc-transfer denom-hash transfer/channel-5/uatom --node=https://agoric-rpc.polkachu.com:443
> hash: BA313C4A19DFBF943586C0387E6B11286F9E416B4DD27574E6909CABE0E342FA
dckc commented 1 year ago

we could just pretend that uphoton (testnet ATOM) is stATOM

0xpatrickdev commented 1 year ago

Per this forum comment and this chain registry pr, it seems something like this will provide the denom:

agd query ibc-transfer denom-hash transfer/channel-59/stuatom --node=$NODE_URL

This is currently returning denomination trace not found: key not found. Curious if there is a way to determine a trace w/o sending tokens 🤔

Also see this for the stuatom and statom denoms: https://github.com/cosmos/chain-registry/blob/2c08fb52b1b585c5a24a04eb1c84fe8d2d105c92/stride/assetlist.json#L27-L51

dckc commented 1 year ago

fixed:

https://github.com/0xpatrickdev/agoric-vault-collateral-proposal/blob/89fd318764e5575f528b0d38f23b33b18d8fa727/add-stATOM.js#L12

dckc commented 11 months ago

we've been playing with the denom lately. need to line it up

seems to need a separate release for each