swaps show up as sends #3

New Issue

sneak · 2026-02-27T11:48:10+01:00

sneak commented

2026-02-27 11:48:10 +01:00

On the transaction history on main, address, and the transaction detail page transaction, swaps just show up as "Sent" - they should say "Swap" in the tx lists and the detail page should show all of the swap details (if we are able to decode it). The transaction detail page should in any event indicate that it's an unknown contract call if it's NOT a standard erc20 send/receive, and we don't know how to otherwise decode it. In that case it should show the raw transaction hex in the tx detail view.

If we can decode it, make it look the same as it does on the signing confirmation view (it's in a well iirc). Display consistency.

On the transaction history on `main`, `address`, and the transaction detail page `transaction`, swaps just show up as "Sent" - they should say "Swap" in the tx lists and the detail page should show all of the swap details (if we are able to decode it). The transaction detail page should in any event indicate that it's an unknown contract call if it's NOT a standard erc20 send/receive, and we don't know how to otherwise decode it. In that case it should show the raw transaction hex in the tx detail view. If we can decode it, make it look the same as it does on the signing confirmation view (it's in a well iirc). Display consistency.

clawbot was assigned by sneak

2026-02-27 21:00:31 +01:00

clawbot commented

2026-02-27 21:01:45 +01:00

Taking this. Plan:

In tx history lists (home, address, addressToken views): detect contract calls vs simple transfers. Show "Swap" for decoded Uniswap txs, "Contract Call" for unknown contract interactions, "Sent"/"Received" only for actual transfers.
In transaction detail view: if we can decode (Uniswap, ERC-20), show the decoded summary in the same well format as the signing confirmation. If unknown contract call, show "Unknown Contract Call" label + full raw calldata hex.
Reuse the existing decoder modules in src/shared/ (uniswap.js, etc.) for display-side decoding.

Spawning a sub-agent now.

Taking this. Plan: 1. In tx history lists (home, address, addressToken views): detect contract calls vs simple transfers. Show "Swap" for decoded Uniswap txs, "Contract Call" for unknown contract interactions, "Sent"/"Received" only for actual transfers. 2. In transaction detail view: if we can decode (Uniswap, ERC-20), show the decoded summary in the same well format as the signing confirmation. If unknown contract call, show "Unknown Contract Call" label + full raw calldata hex. 3. Reuse the existing decoder modules in `src/shared/` (uniswap.js, etc.) for display-side decoding. Spawning a sub-agent now.

clawbot referenced this issue from a commit

2026-02-27 21:04:03 +01:00

fix: display swaps and contract calls correctly in tx history (closes #3)

clawbot referenced a pull request that will close this issue

2026-02-27 21:04:14 +01:00

fix: display swaps and contract calls correctly in tx history (closes #3) #10

sneak referenced this issue

2026-02-27 21:06:11 +01:00

fix: display swaps and contract calls correctly in tx history (closes #3) #10

clawbot referenced a pull request that will close this issue

2026-02-27 21:06:34 +01:00

fix: show swap transactions with decoded calldata in history and detail views (closes #3) #12