Play
The whole nest in your tab
This tab runs a nest, not only its queries: nuthatch's cursor follows a token at the chain's tip, keeps its hot store in redb in this browser, rolls back what a reorg takes away, maintains two incremental entities, and answers the node's HTTP API under this page's address. All of it is nuthatch's own code compiled to WebAssembly (RFC-0075). To query a published nest instead, open the playground.
Ask it
Every request here is a plain fetch to this page's own address, answered by a Service Worker from the nest in this tab with the node's status and bytes. The browser console can do the same: await (await fetch('/play/live/sql?q=SELECT%20count(*)%20FROM%20tab__transfer')).json(), or await nest.sql('...'). Nothing outside this browser can reach it.
The answer, as the node sends it
The nest's entities and views
The data is what this tab indexed since it opened: nothing comes from a mirror, and each visit starts a fresh store. Blocks seal to Parquet segments past finality, by the node's own rules; newer ones stay in the hot store, where a reorg can still reach them. Source: spike/dbsp-wasm.