Preferences
Settings
Everything here is browser state. Nothing on this page is sent anywhere, and there is nothing about data sources to configure — a visitor chooses nothing that affects where a byte comes from.
Privacy
What this deployment can observe, which is the whole of it.
- Account
- Not required Every published trace opens anonymously, whatever the chain's coverage mode.
- Ads
- None
- Third-party requests
- None No page fetches anything from a chain endpoint or any other third party.
- Telemetry
- Off Opt-in, off by default, and not yet implemented — so there is nothing switched on to switch off.
- What is logged
- This deployment's own CDN logs, and nothing else. A page load is a series of GETs against static files.
- Record caps
- None Address history is complete; it is paged by block range, not truncated.
Storage
Local trace-cache usage, its ceiling and a clear button. Measuring what a browser has cached, and clearing it, are both script operations, and this deployment ships none — so there is no number to show and no button that could act on it. Until then nothing is stored beyond the HTTP cache, which your browser already owns and can already clear.
Debugger
Theme, keybinding set, pane layout and reduced motion. The theme already follows your system preference through prefers-color-scheme, and reduced motion is already honoured — both are stylesheet-level and work now. The toggle that would override the system preference, the keybinding set and the persisted pane layout are stored per browser, which needs script.
Advanced
Registry override URL, for pointing a public build at a private deployment. A build already reads its registry from the tree it was built against; overriding that at run time is the part that needs script. A self-hoster changes it at build time today, which is the same capability without the switch.