3 Commits

Include renames

Author	SHA1	Message	Date
sneak	d02e3aefe0	fix: Blockscout and Etherscan lookups are off until the user turns them on (closes #668) ... Out of the box the wallet sent the user's addresses to Blockscout for history and token lookups. It sent each recipient to Etherscan for its label. Two settings, "Use Blockscout" and "Check recipients on Etherscan", now gate those requests. Both are off in a new install and offered unticked on Welcome and in Settings. While one is off, the screens that relied on it say so in a plain line. The balance refresh and the Etherscan check read the stored setting. An open popup takes a change another page saved and draws its screens again. While "Use Blockscout" is off, no address keeps an untracked token. ENS lookups ask only the RPC endpoint. Model: opus-5-5	2026-10-26 02:57:23 +00:00
clawbot	1144fdb71b	harden: key remembered site permissions by full origin (closes #402) ... allowedSites and deniedSites held the bare hostname, so a grant to https://dapp.example also authorised http://dapp.example and every port on that host, and the connection, transaction and signature prompts named only the hostname. Both lists now store and match the full origin (scheme://host[:port]), the key the connections approved without Remember already used. The prompts, the Settings site lists and AUTISTMASK_REMOVE_SITE use the origin too. Entries saved by hostname are not migrated (pre-1.0): they match no site. Model: opus-5-5	2026-10-04 18:09:04 +02:00
clawbot	59f68b8859	fix: answer eth_chainId and net_version from loaded state (closes #317) ... Both methods answered from the module-level state singleton, which the MV3 worker never populates, so a cold worker reported mainnet 0x1 to a page whose user was on Sepolia. They now answer from getState(), the per-call detached storage read the other read handlers already use. An earlier revision of this fix used loadState() instead and was rejected in review: it replaces the whole singleton, and these methods are page-callable with no connection gate (inpage.js sends eth_chainId on every page load), so a load landing inside backgroundRefresh()'s network round trip detached the address objects being mutated in place — persisting pre-refresh balances while still stamping lastBalanceRefresh, letting a polling page suppress background refreshes indefinitely. The test stub now structured-clones on get and set, as chrome.storage.local does. The aliasing stub it replaces was independently measured to hide this defect class entirely: with the aliasing get restored and the defective handler in place, the suite passes 794/794. Verified failing first three ways: a plain singleton read fails the three cold-worker cases; the rejected loadState() revision fails only the new mid-refresh case ("1.5" expected, "0" received); moving saveState() ahead of refreshBalances() fails that case and only it.	2026-08-20 13:11:48 +02:00