TransactionDetail, src/popup/views/transactionDetail.js. The block, nonce, gas, fee and calldata sections are read from state.blockscoutUrl + "/transactions/" + txHash, the active network's Blockscout, and the calldata is decoded with currentNetwork().chainId.
What happens
With Ethereum Mainnet active, opening a Sepolia transaction on TransactionDetail (the popup reopens onto it after a network switch) asks mainnet's Blockscout for it. That finds nothing, so those sections stay empty.
What should happen
TransactionDetail describes the transaction on the network it was sent on: its details come from that network's Blockscout (the one Settings has for it) and its calldata is decoded for that network, whichever network is active.
Severity: minor
Definition of done
TransactionDetail reads the transaction's details from the Blockscout of the network it was sent on and decodes its calldata for that network.
A test with the other network active.
Model: opus-5-5
Seen by the worker on https://git.eeqj.de/sneak/AutistMask/pulls/621.
## Where
TransactionDetail, `src/popup/views/transactionDetail.js`. The block, nonce, gas, fee and calldata sections are read from `state.blockscoutUrl + "/transactions/" + txHash`, the active network's Blockscout, and the calldata is decoded with `currentNetwork().chainId`.
## What happens
With Ethereum Mainnet active, opening a Sepolia transaction on TransactionDetail (the popup reopens onto it after a network switch) asks mainnet's Blockscout for it. That finds nothing, so those sections stay empty.
## What should happen
TransactionDetail describes the transaction on the network it was sent on: its details come from that network's Blockscout (the one Settings has for it) and its calldata is decoded for that network, whichever network is active.
Severity: minor
## Definition of done
- [ ] TransactionDetail reads the transaction's details from the Blockscout of the network it was sent on and decodes its calldata for that network.
- [ ] A test with the other network active.
Model: opus-5-5
clawbot
self-assigned this 2026-10-19 23:12:43 +02:00
Plan: one PR to next, in src/popup/views/transactionDetail.js. TransactionDetail reads the transaction from the Blockscout of the network its chain id names, picked the way reviewedNetworkProvider() in src/popup/views/helpers.js picks a node (the active network's state.blockscoutUrl, otherwise the one Settings remembers for that network, otherwise its default), and decodes its calldata for that chain id rather than currentNetwork().chainId. A Jest test with the other network active, failing on next.
Model: opus-5-5
Plan: one PR to `next`, in `src/popup/views/transactionDetail.js`. TransactionDetail reads the transaction from the Blockscout of the network its chain id names, picked the way `reviewedNetworkProvider()` in `src/popup/views/helpers.js` picks a node (the active network's `state.blockscoutUrl`, otherwise the one Settings remembers for that network, otherwise its default), and decodes its calldata for that chain id rather than `currentNetwork().chainId`. A Jest test with the other network active, failing on `next`.
Model: opus-5-5
#627: TransactionDetail now reads the transaction from the Blockscout Settings has for the network it was sent on, and decodes its calldata for that network, through reviewedNetworkEndpoints() beside reviewedNetworkProvider() in src/popup/views/helpers.js.
Model: opus-5-5
https://git.eeqj.de/sneak/AutistMask/pulls/627: TransactionDetail now reads the transaction from the Blockscout Settings has for the network it was sent on, and decodes its calldata for that network, through `reviewedNetworkEndpoints()` beside `reviewedNetworkProvider()` in `src/popup/views/helpers.js`.
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.
Seen by the worker on #621.
Where
TransactionDetail,
src/popup/views/transactionDetail.js. The block, nonce, gas, fee and calldata sections are read fromstate.blockscoutUrl + "/transactions/" + txHash, the active network's Blockscout, and the calldata is decoded withcurrentNetwork().chainId.What happens
With Ethereum Mainnet active, opening a Sepolia transaction on TransactionDetail (the popup reopens onto it after a network switch) asks mainnet's Blockscout for it. That finds nothing, so those sections stay empty.
What should happen
TransactionDetail describes the transaction on the network it was sent on: its details come from that network's Blockscout (the one Settings has for it) and its calldata is decoded for that network, whichever network is active.
Severity: minor
Definition of done
Model: opus-5-5
Plan: one PR to
next, insrc/popup/views/transactionDetail.js. TransactionDetail reads the transaction from the Blockscout of the network its chain id names, picked the wayreviewedNetworkProvider()insrc/popup/views/helpers.jspicks a node (the active network'sstate.blockscoutUrl, otherwise the one Settings remembers for that network, otherwise its default), and decodes its calldata for that chain id rather thancurrentNetwork().chainId. A Jest test with the other network active, failing onnext.Model: opus-5-5
#627: TransactionDetail now reads the transaction from the Blockscout Settings has for the network it was sent on, and decodes its calldata for that network, through
reviewedNetworkEndpoints()besidereviewedNetworkProvider()insrc/popup/views/helpers.js.Model: opus-5-5