Record format
@flashyos/bolt
bolt/1 — one secret split across an estate: a hunt verified by sha256 commitment, in the finder’s own browser, with no server to trust.
version 0.2.2 · audit of 2026-10-04 · source: flashyos/packages/bolt
npm i @flashyos/boltThe verify page holds the digest and not one shard, sends nothing anywhere, and keeps no record anybody visited. A miss never says which shard was wrong: a check that narrows the answer is brute-forceable one field at a time.
Edge cases — each one paid for once
Growth adds a tier; it never revokes one
One commitment over N shards breaks the day property N+1 launches. Tiers are sealed like shipped/1 entries: each contains every property of the one before, and an early finder’s proof stays good forever.
Server components only — a shard in a client prop is findable in devtools
Rendering the snippet from a client component puts the shard in the RSC payload and the bundle. And the hunt page itself must never carry its own property’s shard; the test caught that on the first build.