TransactionDetail, opened from an ERC-20 transfer row. src/popup/views/transactionDetail.js line 186 calls loadFullTxDetails(tx.hash, tx.to, tx.chainId), and line 316 decodes the calldata against that address. For a token transfer row, tx.to is the transfer's recipient (parseTokenTransfer() in src/shared/transactions.js), not the contract the transaction was sent to, which is tx.contractAddress.
What happens
On next (8e52528), release build, Chrome, local chain with chain id 11155111: send 1234.5 of a tracked 6-decimal token, open the transfer from the token's history. The top of the screen is right (Amount 1234.5 TDOL, Token contract 0x74de…1b37), but the decoded Action well below it reads:
Token: 0x711e691962E5c054b78071C789A0C8CE657377aD, which is the recipient
Recipient: the same address
Amount: 1234500000 base units (decimals unknown)
So the screen names the recipient as the token, and calls the token's scale unknown although the wallet tracks it.
What should happen
README calls this screen "the authoritative record of a specific transaction". Its decoded details should name the token contract the transaction called, and state the amount at the token's known scale, as the approval screen does for the same calldata.
Severity: major
Definition of done
The decoded details of a token transfer opened from any history list are decoded against the contract the transaction was sent to.
A test opens an ERC-20 transfer row and checks the decoded Token line and amount.
Model: opus-5-5
## Where
TransactionDetail, opened from an ERC-20 transfer row. `src/popup/views/transactionDetail.js` line 186 calls `loadFullTxDetails(tx.hash, tx.to, tx.chainId)`, and line 316 decodes the calldata against that address. For a token transfer row, `tx.to` is the transfer's recipient (`parseTokenTransfer()` in `src/shared/transactions.js`), not the contract the transaction was sent to, which is `tx.contractAddress`.
## What happens
On `next` (8e52528), release build, Chrome, local chain with chain id 11155111: send 1234.5 of a tracked 6-decimal token, open the transfer from the token's history. The top of the screen is right (Amount `1234.5 TDOL`, Token contract `0x74de…1b37`), but the decoded Action well below it reads:
- Token: `0x711e691962E5c054b78071C789A0C8CE657377aD`, which is the recipient
- Recipient: the same address
- Amount: `1234500000 base units (decimals unknown)`
So the screen names the recipient as the token, and calls the token's scale unknown although the wallet tracks it.
## What should happen
README calls this screen "the authoritative record of a specific transaction". Its decoded details should name the token contract the transaction called, and state the amount at the token's known scale, as the approval screen does for the same calldata.
Severity: major
## Definition of done
- [ ] The decoded details of a token transfer opened from any history list are decoded against the contract the transaction was sent to.
- [ ] A test opens an ERC-20 transfer row and checks the decoded Token line and amount.
Model: opus-5-5
clawbot
self-assigned this 2026-10-14 04:39:17 +02:00
Fixed in #549. The detail screen now decodes against the address the explorer reports the transaction was sent to, not the history entry's to, so a token transfer's Token line names the token contract and the amount uses the token's known decimals. A new test builds the row with the real history parser and opens it.
Model: opus-5-5
Fixed in https://git.eeqj.de/sneak/AutistMask/pulls/549. The detail screen now decodes against the address the explorer reports the transaction was sent to, not the history entry's `to`, so a token transfer's Token line names the token contract and the amount uses the token's known decimals. A new test builds the row with the real history parser and opens it.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Where
TransactionDetail, opened from an ERC-20 transfer row.
src/popup/views/transactionDetail.jsline 186 callsloadFullTxDetails(tx.hash, tx.to, tx.chainId), and line 316 decodes the calldata against that address. For a token transfer row,tx.tois the transfer's recipient (parseTokenTransfer()insrc/shared/transactions.js), not the contract the transaction was sent to, which istx.contractAddress.What happens
On
next(8e52528), release build, Chrome, local chain with chain id 11155111: send 1234.5 of a tracked 6-decimal token, open the transfer from the token's history. The top of the screen is right (Amount1234.5 TDOL, Token contract0x74de…1b37), but the decoded Action well below it reads:0x711e691962E5c054b78071C789A0C8CE657377aD, which is the recipient1234500000 base units (decimals unknown)So the screen names the recipient as the token, and calls the token's scale unknown although the wallet tracks it.
What should happen
README calls this screen "the authoritative record of a specific transaction". Its decoded details should name the token contract the transaction called, and state the amount at the token's known scale, as the approval screen does for the same calldata.
Severity: major
Definition of done
Model: opus-5-5
Fixed in #549. The detail screen now decodes against the address the explorer reports the transaction was sent to, not the history entry's
to, so a token transfer's Token line names the token contract and the amount uses the token's known decimals. A new test builds the row with the real history parser and opens it.Model: opus-5-5