Implement "USDT Transfer" Display for USDT Transactions in AppID

[SamantaCasal]

Description:

As a user, I want the application to display "USDT Transfer" as the appID whenever I am sending USDT tokens so that I can easily identify and confirm the specific bridge being used for my transactions.

Acceptance Criteria:

1. When a user initiates a transaction involving USDT, the appID should automatically display as "USDT Bridge."
2. Add USDT Transfer in the Protocol filter
3. Add functionality to the vaaa-payload-parser to identify USDT transactions and display them in the appID.

Resources

Contracts: https://docs.google.com/spreadsheets/d/1O6g_g8GQsgB_UJt06JxaX7dLozseHfct-CcxBe6YUkY/edit#gid=0

• VAA Base: https://wormholescan.io/#/tx/0x1b4c6034333288a4771713547d730044e44ab4e6c98dda72aa44e40a535032ba
• Arb VAA: https://wormholescan.io/#/tx/0xcf4ed3d3b969431d81467744c771853ef817160e546190af725f47a41380eede
• BSC VAA: https://wormholescan.io/#/tx/0xa6eaa134966a43cf002389e828a96ebd4c3886716d9e18feac3e5298b2237795
• Mainnet: https://wormholescan.io/#/tx/0xae9715d7f03f8a5a52025639bdc820ba9091ba102f974f19a47cfc3a0b2200ad

[mliu-xlabs]

There is a known issue that we may have with this because for OP, Polygon, and Avax - these are still using the original Eth transfer portico contracts. What this means is that for origins from OP, Polygon, or Avax, the App ID will show as Eth Transfer instead of USDT Transfer, since AppID is currently based off of the contract. we will need to find a method (Snale had idea to additionally parse the token bridge details to determine if the transfer is USDT or ETH. If USDT then USDT Transfer, if ETH then Eth Transfer)

[valentinoConti]

@mliu-xlabs I'm almost sure I can handle that in the vaa-payload-parser 👍🏼, good info

[M-Picco]

A small tidbit of info mentioned on a slack thread:

For the USDT Bridge, the new emitters will be:

• ethereum: 0x4db1683d60e0a933A9A477a19FA32F472bB9d06e
• bsc: 0xF352DC165783538A26e38A536e76DceF227d90F2
• arbitrum: 0xE70946692E2e56ae47BfAe2d93d31bd60952B090
• base: 0x4568aa1eA0ED54db666c58B4526B3FC9BD9be9bf

For the other chains (polygon, avalanche, and optimism), the emitter will be the same as it is for ETH Bridge transfers

Basically when transferring USDT, it calls the new contracts since those chains have a PancakeSwap pool. But if the chain doesn't have a PancakeSwap pool, the it calls the "old" contracts which swap via Uniswap pool

That's why there weren't new contracts deployed to all of the chains (because the new ones use PancakeSwap for USDT swaps)

I'd double check the emitters with the spreadsheet that Sami linked on the ticket

[SamantaCasal]

There are no transactions yet to test this implementation. We send the filter to Prod, when transactions appear, if we find any bugs we will report it in a separate issue. FYI: @M-Picco @mliu-xlabs @valentinoConti

• https://xlabs.github.io/wormscan-ui/#/txs?page=1&appId=USDT_TRANSFER
• https://xlabs.github.io/wormscan-ui/#/txs?page=1&appId=USDT_TRANSFER&network=TESTNET