Where.src/background/index.js:725-772 (wallet_switchEthereumChain, gated
on connection only).
The behaviour.wallet_switchEthereumChain is gated on the site being
connected, then rewrites networkId, rpcUrl and blockscoutUrl, clears
balances and caches, and broadcasts chainChanged to every tab — with no user
confirmation. The README (TxApproval section) documents the connection gate as
the fix for an unconnected page clearing the [TESTNET] banner, but a connected
site can still flip the network silently between the two supported chains.
The question. Should a chain switch require a prompt? A connected dApp moving
the user from Sepolia to mainnet (or back) before a send is silent; the send
screen does show the network, but the user may not re-read it.
Options.
Prompt on every wallet_switchEthereumChain, as other wallets do.
Keep it promptless and make the switch conspicuous on the next approval screen.
Recommendation. Keep it promptless for the two supported chains but surface
the active network prominently on the very next approval; a prompt on every
switch is friction for a wallet that supports only mainnet and one testnet.
Definition of done.
The owner rules prompt vs promptless.
The chosen behaviour is implemented and the README matches it.
Model: fable-5-1 (review); opus-4-8 (filing)
Severity: hardening. Owner decision.
**Where.** `src/background/index.js:725-772` (`wallet_switchEthereumChain`, gated
on connection only).
**The behaviour.** `wallet_switchEthereumChain` is gated on the site being
connected, then rewrites `networkId`, `rpcUrl` and `blockscoutUrl`, clears
balances and caches, and broadcasts `chainChanged` to every tab — with no user
confirmation. The README (TxApproval section) documents the connection gate as
the fix for an unconnected page clearing the `[TESTNET]` banner, but a connected
site can still flip the network silently between the two supported chains.
**The question.** Should a chain switch require a prompt? A connected dApp moving
the user from Sepolia to mainnet (or back) before a send is silent; the send
screen does show the network, but the user may not re-read it.
**Options.**
- Prompt on every `wallet_switchEthereumChain`, as other wallets do.
- Keep it promptless and make the switch conspicuous on the next approval screen.
**Recommendation.** Keep it promptless for the two supported chains but surface
the active network prominently on the very next approval; a prompt on every
switch is friction for a wallet that supports only mainnet and one testnet.
**Definition of done.**
- [ ] The owner rules prompt vs promptless.
- [ ] The chosen behaviour is implemented and the README matches it.
Model: fable-5-1 (review); opus-4-8 (filing)
sneak
was assigned by clawbot2026-09-21 20:37:56 +02:00
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.
Severity: hardening. Owner decision.
Where.
src/background/index.js:725-772(wallet_switchEthereumChain, gatedon connection only).
The behaviour.
wallet_switchEthereumChainis gated on the site beingconnected, then rewrites
networkId,rpcUrlandblockscoutUrl, clearsbalances and caches, and broadcasts
chainChangedto every tab — with no userconfirmation. The README (TxApproval section) documents the connection gate as
the fix for an unconnected page clearing the
[TESTNET]banner, but a connectedsite can still flip the network silently between the two supported chains.
The question. Should a chain switch require a prompt? A connected dApp moving
the user from Sepolia to mainnet (or back) before a send is silent; the send
screen does show the network, but the user may not re-read it.
Options.
wallet_switchEthereumChain, as other wallets do.Recommendation. Keep it promptless for the two supported chains but surface
the active network prominently on the very next approval; a prompt on every
switch is friction for a wallet that supports only mainnet and one testnet.
Definition of done.
Model: fable-5-1 (review); opus-4-8 (filing)