Pattern scan over the live Bitcoin transactions and addresses
You are looking at Bitcoin value-flow graphevery transaction and address key, no inverted index in one Semurg substrate. Ask it to run the index-free pattern scan and it runs the
real query live on this box, on data you can
download and re-run yourself ▸.
Click an example in the agent rail, or type any address prefix or pattern, e.g. bc1q, 1A1zP1, 3J98. Every run is measured end to end, on
this box, on the real dataset. Nothing is pre-computed.
the live Bitcoin value-flow graph, transactions and addresses linked by value-flows (prev-tx to tx to address), parsed straight off the P2P network · Bitcoin mainnet P2P (our own block-parser node, no bitcoind, no REST). A query sweeps every transaction and address key with NO index, the moment the data lands, any ad-hoc prefix or pattern, no ingest wait. Measured live.
the full-text search leader, same corpus
Index first, then answer. An inverted index must be built over the dump before the first query, and it can only answer the terms and fields it was told to index ahead of time.
semurg, one engine
Zero indexes built. Any ad-hoc prefix or pattern, the instant the Bitcoin data lands, by sweeping the raw bytes at memory bandwidth, on the same engine that also serves graph and vectors.
No index to build means nothing to wait for and nothing it cannot answer.
Bitcoin transactions and addresses (188.97M keys). Measured live on this box. Re-pull it over Bitcoin P2P and re-run it yourself.
ask the agent to find a term, the live scan renders here
Honest concession: a pre-built inverted index is fast for the one warm single-keyword lookup it was built for. It must be built first, can't answer what it didn't index, and lives in a separate engine. This is one substrate, running the live Bitcoin transactions and addresses corpus.