sneak
2bdcfae629
Out of the box the wallet sent the user's addresses to Blockscout and each recipient to Etherscan. 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. Each gated request reads its setting from storage before it asks and when the answer lands, and drops a late answer. An open popup takes another page's change and draws its screens again. While "Use Blockscout" is off, no address keeps an untracked token, and no screen names a token from Blockscout's report. ENS lookups ask only the RPC endpoint. Model: opus-5-5
62 lines
2.7 KiB
JavaScript
62 lines
2.7 KiB
JavaScript
// The popup's network switch.
|
|
//
|
|
// A network switch reaches the popup's `state` in one of two ways:
|
|
//
|
|
// - onChainSwitch() below makes the switch the user picks in Settings, with
|
|
// applyChainSwitchFields() (chainSwitchFields.js).
|
|
// - followStoredSettings() in src/popup/index.js takes a switch the background
|
|
// or another popup page saved, from the stored record, with
|
|
// takeStoredNetwork() (state.js), which copies it with
|
|
// copyChainSwitchFields() (chainSwitchFields.js).
|
|
//
|
|
// Both change `state` inside a save, holding the lock, and both reset the
|
|
// popup's own caches through clearPopupCaches(), so a reset added there
|
|
// reaches both. A field applyChainSwitchFields() sets has to be copied by
|
|
// copyChainSwitchFields() too.
|
|
//
|
|
// Adding a new chain (e.g. ETC) requires only a new entry in
|
|
// networks.js — no per-caller wiring is needed.
|
|
//
|
|
// The background does NOT come through here: this function mutates the
|
|
// module-level `state` singleton, which the MV3 service worker never
|
|
// populates, and a background switch performed on it wrote DEFAULT_STATE over
|
|
// the user's whole profile
|
|
// (https://git.eeqj.de/sneak/AutistMask/issues/316). The field mutations
|
|
// themselves live in chainSwitchFields.js, which takes the record to mutate as
|
|
// an argument; src/background/state.js applies them inside a read-modify-write
|
|
// against storage, and the singleton is not reachable from the background
|
|
// bundle at all (enforced by the ESLint rule in eslint.config.js).
|
|
|
|
const { applyChainSwitchFields } = require("./chainSwitchFields");
|
|
const { clearPrices } = require("./prices");
|
|
|
|
// The popup's own caches a network switch resets. Prices are chain-specific
|
|
// (testnet tokens are worthless, ETC has different pricing, etc.). In-memory
|
|
// and per bundle, so this is the popup's own cache — the only context that
|
|
// ever fills it.
|
|
function clearPopupCaches() {
|
|
clearPrices();
|
|
}
|
|
|
|
// Switch the active chain and reset all chain-specific cached state.
|
|
// Returns the network configuration object for the new chain, or null when
|
|
// `state` already has that network once the save holds the lock, and nothing
|
|
// is switched.
|
|
//
|
|
// `state` is switched inside the save that stores the switch, holding the
|
|
// lock, so it is never switched while a follow of a switch saved elsewhere
|
|
// waits for the lock (followStoredSettings() in src/popup/index.js): that
|
|
// follow runs first, and this switch is made after it.
|
|
async function onChainSwitch(newNetworkId) {
|
|
const { state, saveState } = require("./state");
|
|
let net = null;
|
|
await saveState(() => {
|
|
if (state.networkId === newNetworkId) return false;
|
|
net = applyChainSwitchFields(state, newNetworkId);
|
|
clearPopupCaches();
|
|
});
|
|
return net;
|
|
}
|
|
|
|
module.exports = { onChainSwitch, clearPopupCaches };
|