Sidechain spends are opt-in; cached chain state; 0.0.10

[jjohare]

Sidechain spends become opt-in, and each chain's validated state is cached so spends open quickly. 0.0.10.

Opt-in

• Spends are off until the person turns them on, either in settings or in the spend window the first time a site asks: "Turn on and review", or "Not now", which answers the site with code: 'unsupported'.
• Settings list the chains in use, each with its pinned signer and a Forget button. Turning spends off forgets every chain. Signer pins from 0.0.9 carry over and count as turned on.
• New: window.nostr.sidestr.enabled, read live from <html data-podkey-sidestr>, which the content script mirrors from the setting. signTransaction is present either way, so a site never hits a dead end. A page that forges the attribute only misleads itself.

Cache

• The explorer resumes from its saved state, and the holders' asset view resumes from its own. Both are keyed to the block hash at the saved height; if either doesn't match, both are dropped and every block is checked again. The spend window says which it did ("N new blocks checked, M from your last visit").
• On the live sidestr:dreamlab, a full check of all 545 blocks took 5.9 s and a resumed check 0.3 s, with an identical asset view. The saved state is 47 KB.

Checks

• npm test passes 228/228, with new tests covering the settings, migration, forget and off, and an asset-view resume that must equal a full replay and refuse a mismatched save. Lint is clean.
• Both screens were rendered in Chrome: the opt-in step and the settings switch with its chain list. Turning spends on saved the setting, validated the live chain and wrote both caches.

Spec text: sidestr/spec (PR to follow) adds enabled and the opt-in behaviour to the browser-signer proposal.

🤖 Generated by Claude Code