[ralph-bitgo]

Description

What: CosmosCoin.verifyTransaction in @bitgo/abstract-cosmos compared txParams.recipients against the decoded transaction outputs as raw {address, amount} strings. Recipients using the BitGo combined address+memo convention (address?memoId=X) therefore never matched the plain on-chain address that explainTransaction() reports, and local validation failed with Tx outputs does not match with expected txParams recipients even when the prebuild was correct.

This change normalizes both sides to a common {address, amount, memo?} shape via getAddressDetails before comparing, which also checks the recipient memoId against the transaction memo. The per-coin fix previously applied only in sdk-coin-zeta (COINS-1676) is lifted into the shared base class so TIA and every other Cosmos coin (ATOM, OSMO, SEI, ...) behave consistently; the now-redundant Zeta.verifyTransaction override is removed and TIA regression tests are added.

Why: TIA withdrawals to memo-tagged recipients fail client-side before signing — reproduced on wallet 6ac4da812f35c0437d86b20a4307e41a in COINS-1760. The same base-class comparison backs all Cosmos coins, so any customer withdrawal to a tagged/exchange address written as address?memoId=X fails the same way on every Cosmos coin, not just TIA.

Behavior note: verification is now memo-aware in the fail-closed direction: a transaction that carries a memo whose recipient did not declare ?memoId= is rejected (previously the memo was ignored). A declared ?memoId= must match the transaction memo.

Issue Number

COINS-1760 — https://linear.app/bitgo/issue/COINS-1760/tia-withdrawal-fails-on-testnet-with-recipient-mismatch-error

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• yarn run unit-test scoped to all 17 Cosmos coin modules that depend on abstract-cosmos (asi, atom, baby, bld, coreum, cosmos, cronos, hash, initia, injective, islm, mantra, osmo, rune, sei, tia, zeta): all suites pass (TIA 80, ZETA 79; only pre-existing pending skips).
• New TIA regression tests in modules/sdk-coin-tia/test/unit/tia.ts using the existing TEST_TX_WITH_MEMO fixture: (1) recipient to?memoId=5 verifies successfully against the memo'd transfer, (2) ?memoId=999999 is rejected, (3) bare recipient against the memo'd tx is rejected.
• RED/GREEN proven against the reported failure: with the pre-fix cosmosCoin.ts, tests (1) and (3) fail (test 1 with the exact Tx outputs does not match with expected txParams recipients from COINS-1760); with the fix all three pass.
• The existing Zeta memo tests from the COINS-1676 fix now exercise the base-class implementation and pass unchanged.
• yarn lint and yarn check-fmt clean in abstract-cosmos, sdk-coin-zeta, sdk-coin-tia.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• My code compiles correctly for both Node and Browser environments
• I have commented my code, particularly in hard-to-understand areas
• My commits follow Conventional Commits and I have properly described any BREAKING CHANGES
• The ticket or github issue was included in the commit message as a reference
• I have made corresponding changes to the documentation and on any new/updated functions and/or methods - jsdoc
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

Ticket: COINS-1760

[linear-code]

COINS-1760

[github-actions]

⚠️ Unit tests are failing on Node 26.x (Current release line, non-blocking). This is not an LTS version yet, so it does not block merge, but it signals an incompatibility to fix before Node 26.x becomes LTS.

View run