4 Commits

Include renames

Author	SHA1	Message	Date
clawbot	ca9cd438d9	fix: transaction screens name a token from the tokens of the transaction's network (closes #629) ... decodeCalldata() looked a token's symbol and decimals up in the active network's tracked tokens and balances, whatever chain id it was given, so TransactionDetail and TxApproval showed a token tracked on another network by address only, with its amount in base units. The lookup now uses what the wallet knows of the tokens on the transaction's network: the active network's tracked tokens and balances, or for another network the tokens tracked on it and no balances. TxApproval's token labels, the symbol it hands the wait, success and error screens, and SuccessTx's decoded token label use the same lookup. Model: opus-5-5	2026-10-20 04:16:04 +02:00
clawbot	3aed2bb5f0	fix: TransactionDetail reads a transaction from the Blockscout of the network it was sent on (closes #623) ... TransactionDetail read the block, network details and calldata from the active network's Blockscout and decoded the calldata for the active network, so after a network switch a transaction sent on the other network showed none of them. It now reads them from the Blockscout Settings has for the network the transaction was sent on, and decodes the calldata for that network. endpointsByChainId() in the shared view helpers gives a network's RPC and Blockscout URLs, picked as reviewedNetworkProvider() picked its node; reviewedNetworkProvider() now uses it. Restore refuses a stored transaction whose chain id names no network, as it does for WaitTx. Model: opus-5-5	2026-10-20 03:10:30 +02:00
clawbot	e46d894527	fix: WaitTx and TransactionDetail use the network the transaction was sent on (closes #584) ... WaitTx asked the active network's node for the receipt, so after a network switch a transaction sent on the other network was never found and was reported as timed out. It now asks the node of the network its chain id names, through reviewedNetworkProvider(), moved from ConfirmTx into the shared view helpers so both screens use one function. WaitTx and TransactionDetail build their explorer links for that network too. A stored wait or transaction whose chain id names no network is refused on restore, as a stored ConfirmTx transaction already is. Model: opus-5-5	2026-10-19 23:38:10 +02:00
clawbot	cb27281b21	fix: the transaction detail screen decodes a token transfer against the token contract (closes #515) ... The screen decoded a transaction's data against the history entry's `to`, which for a token transfer row is the transfer's recipient. The decoded Token line named the recipient, and the amount read "decimals unknown" for a token the wallet tracks. It now decodes against the address the explorer's answer for that transaction says it was sent to, which is the right address for every kind of row. tests/tokenTransferDetail.test.js opens a row made by the real history parser and checks the Token, Recipient and Amount lines. Model: opus-5-5	2026-10-14 16:37:55 +02:00