When a user sends a tx to osmosis it is routed through wormchain (chain id 3104)
Currently we see the transaction in wormholescan as tx with destination wormchain.
We want to include also the routing information on the API so we can include that in the front end.
We need to add a new parser to the payload parser to support this kind of payloads where the destination chain is 3104.
And add the gateway_transfer data to the db.
Also an app id should be added to the VAA with "OSMOSIS".
The recipient is base64 encoded, should be persisted unencoded like: osmo1d898yxhaq0wsa3rqu3uy3af73hukvtqd3tn535
Acceptance Criteria
When we call the payload parser API with a VAA with destination wormchain we should see the gateway_transfer data
Also we should see the OSMOSIS app_id.
Notes
Identify other cases of chain behind wormscan. Osmosis is not the only one.
In analytics the destination chains is going to be wormscan.
When a user sends a tx to
osmosis
it is routed throughwormchain
(chain id 3104) Currently we see the transaction in wormholescan as tx with destination wormchain. We want to include also the routing information on the API so we can include that in the front end.Example a tx to osmosis: https://wormholescan.io/#/tx/6/00000000000000000000000061e44e506ca5659e6c0bba9b678586fa2d729756/7632?network=TESTNET
The decoded payload looks like this
And if we also de code the inner payload we see this:
We need to add a new parser to the payload parser to support this kind of payloads where the destination chain is 3104. And add the
gateway_transfer
data to the db.Also an app id should be added to the VAA with "OSMOSIS".
The recipient is base64 encoded, should be persisted unencoded like:
osmo1d898yxhaq0wsa3rqu3uy3af73hukvtqd3tn535
Acceptance Criteria
gateway_transfer
dataNotes