WaitTx and TransactionDetail. The receipt check in src/popup/views/txStatus.js (line 131) asks the active network's node (state.rpcUrl, state.networkId), and both screens build their explorer links with explorerUrl() for the active network. Each transaction already carries its own chainId, which the screens use for the native token's name.
What happens
The popup reopens onto WaitTx or TransactionDetail for a Sepolia transaction after the user has switched to Ethereum Mainnet (or the other way round). WaitTx asks the mainnet node for the receipt, never finds it, and reports a timeout for a transaction that may have been mined. TransactionDetail links the transaction, its block and its token to the mainnet explorer, where they do not exist.
What should happen
A transaction screen describes the transaction on the network it was sent on: the receipt is asked of that network's node and the links go to that network's explorer, whichever network is active.
Severity: minor
Definition of done
WaitTx checks the receipt on the network the transaction was sent on.
TransactionDetail's explorer links are for the network the transaction was sent on.
A test of each with the other network active.
Model: opus-5-5
Seen by the worker on https://git.eeqj.de/sneak/AutistMask/pulls/572.
## Where
WaitTx and TransactionDetail. The receipt check in `src/popup/views/txStatus.js` (line 131) asks the active network's node (`state.rpcUrl`, `state.networkId`), and both screens build their explorer links with `explorerUrl()` for the active network. Each transaction already carries its own `chainId`, which the screens use for the native token's name.
## What happens
The popup reopens onto WaitTx or TransactionDetail for a Sepolia transaction after the user has switched to Ethereum Mainnet (or the other way round). WaitTx asks the mainnet node for the receipt, never finds it, and reports a timeout for a transaction that may have been mined. TransactionDetail links the transaction, its block and its token to the mainnet explorer, where they do not exist.
## What should happen
A transaction screen describes the transaction on the network it was sent on: the receipt is asked of that network's node and the links go to that network's explorer, whichever network is active.
Severity: minor
## Definition of done
- [ ] WaitTx checks the receipt on the network the transaction was sent on.
- [ ] TransactionDetail's explorer links are for the network the transaction was sent on.
- [ ] A test of each with the other network active.
Model: opus-5-5
clawbot
self-assigned this 2026-10-19 03:59:36 +02:00
Plan: one PR to next. WaitTx asks for the receipt from the node of the network whose chain id the transaction carries, using the node ConfirmTx already picks in reviewedNetworkProvider() (the active network's RPC URL, otherwise the one Settings remembers for that network, otherwise its default), moved to the popup's shared view helpers so both screens call one function. WaitTx and TransactionDetail pass the transaction's chain id to explorerUrl() for every link. Jest tests with the other network active, each failing on next.
Model: opus-5-5
Plan: one PR to `next`. WaitTx asks for the receipt from the node of the network whose chain id the transaction carries, using the node ConfirmTx already picks in `reviewedNetworkProvider()` (the active network's RPC URL, otherwise the one Settings remembers for that network, otherwise its default), moved to the popup's shared view helpers so both screens call one function. WaitTx and TransactionDetail pass the transaction's chain id to `explorerUrl()` for every link. Jest tests with the other network active, each failing on `next`.
Model: opus-5-5
Built in #621: WaitTx asks the node of the network the transaction was sent on for its receipt, and WaitTx and TransactionDetail link to that network's explorer, whichever network is active.
Model: opus-5-5
Built in https://git.eeqj.de/sneak/AutistMask/pulls/621: WaitTx asks the node of the network the transaction was sent on for its receipt, and WaitTx and TransactionDetail link to that network's explorer, whichever network is active.
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 #572.
Where
WaitTx and TransactionDetail. The receipt check in
src/popup/views/txStatus.js(line 131) asks the active network's node (state.rpcUrl,state.networkId), and both screens build their explorer links withexplorerUrl()for the active network. Each transaction already carries its ownchainId, which the screens use for the native token's name.What happens
The popup reopens onto WaitTx or TransactionDetail for a Sepolia transaction after the user has switched to Ethereum Mainnet (or the other way round). WaitTx asks the mainnet node for the receipt, never finds it, and reports a timeout for a transaction that may have been mined. TransactionDetail links the transaction, its block and its token to the mainnet explorer, where they do not exist.
What should happen
A transaction screen describes the transaction on the network it was sent on: the receipt is asked of that network's node and the links go to that network's explorer, whichever network is active.
Severity: minor
Definition of done
Model: opus-5-5
Plan: one PR to
next. WaitTx asks for the receipt from the node of the network whose chain id the transaction carries, using the node ConfirmTx already picks inreviewedNetworkProvider()(the active network's RPC URL, otherwise the one Settings remembers for that network, otherwise its default), moved to the popup's shared view helpers so both screens call one function. WaitTx and TransactionDetail pass the transaction's chain id toexplorerUrl()for every link. Jest tests with the other network active, each failing onnext.Model: opus-5-5
Built in #621: WaitTx asks the node of the network the transaction was sent on for its receipt, and WaitTx and TransactionDetail link to that network's explorer, whichever network is active.
Model: opus-5-5