Through technologyinto the futureAny event

› intake—

anchoringcontinuous

—

···· ···· ···· ···· —

curve secp block —

specimen register · live data on mainnet release

› your event

examples

from€ ——

The bureau receives any event — write the context above, or pick an example.

view source · this artefact

canonical SHA-256computing…

self-anchor block—

self-anchor hash—

timechain anchor—

live state—

entry context—

privacyentry context (referrer, URL parameters, hashtag) read locally to tune bureau response. No cookies. No analytics. No fingerprinting. No raw text leaves your browser at this stage.

engineOHC Protocol · application-layer · BTC-anchor · SPV inclusion · vanilla web stack

verificationheader double-SHA-256 = announced id; compact bits decoded to a target, work asserted as hash ≤ target; the tip coinbase txid's merkle-proof is folded locally (double-SHA-256) and matched to the header merkle_root — all in-browser via WebCrypto. Reproduce: GET /block/<hash> → header → double-SHA-256; GET /tx/<coinbase>/merkle-proof → fold path → merkle_root.

tamperingany mutation of the canonical inscription region — its text OR a link target (href) — triggers a visible alert and re-strikes the bureau's own OHC-005 mark from the changed digest.

Through technology·into the future·Any event

Through technologyinto the futureAny event