Eighteen on-chain events since April.

Five-layer commitment topology

One artefact. Five public networks. Two heterogeneous silicons.

Bitcoin OP_RETURN, ordinals, Lightning channel openings, OpenTimestamps calendars, a Merkle commitment ready to broadcast — every layer publicly verifiable, every claim cross-attested across two different GPU architectures. The substrate did not assert itself in a single moment. It manifested across April 25 → May 6 2026 over five protocol classes. To forge a single leaf, an attacker would need to compromise three of the five layers while also forging the silicon fingerprints of two heterogeneous architectures.

1. Layer 1Bitcoin OP_RETURN·1 event· Reality-check anchor at block 946,772 — mempool.space
2. Layer 2Bitcoin ordinals·3 inscriptions· Within 14 minutes on 2026-04-27 → 2026-04-28 — ord.io
3. Layer 3Lightning channels·6+ openings· Live mainnet node jerry-gb10-gracewell — 1ml.com
4. Layer 4OpenTimestamps·5 calendar submissions· Three independent public calendars — opentimestamps.org
5. Layer 5Merkle commitment·828,001 artefacts· Root committed locally, broadcast pending milestone — mempool.space

Live infrastructure · Lightning

jerry-gb10-gracewell

pubkey

03d3c542…693c9f

lightning address

jerry@pay.shravanbansal.com

channels

3 · mainnet

synced at

block 946,934

verify on 1ml.com ↗

Commitment · ready to broadcast

BRMSTE-CORPUS-REGISTRY-v1

A single Merkle root commits to 828,001 artefacts at tree depth 20. The root is locked client-side; the on-chain inscription is held for a defined launch trigger.

merkle root

c6f68453…38724b

artefacts

828,001

tree depth

20

taproot address

bc1pclxx2d…5qaxf9lt

status

committed · broadcast pending milestone

watch the address ↗