DID substrate
Explore the full walkthrough

A Bitcoin-anchored DID network

One shared history

Three registrars. Five submissions. Four creations.

Follow a request from Alice’s hands to one checked history, shared by independent registrars.

170 seconds · opening sequence

Narration with subtle sound effects. Captions included. Use fullscreen for a closer look.

ABC
Read the narration transcript

The spoken narration follows an illustrative history through Bitcoin block 10. Download the narration text.

0:00–0:05
Each registrar starts with a public Bitcoin identity. Here is A, in block one.
0:08–0:13
B registers independently in block three. Its own identity remains visible on Bitcoin.
0:16–0:20
Then C joins in block five. These are three independent registrars.
0:24–0:30
They verify the small history through block nine: three registrars, and no D I D operations yet.
0:34–0:37
Alice signs a creation request, called A L one.
0:40–0:42
Provider A is her document service choice.
0:44–0:46
She sends those signed bytes to registrar A.
0:48–0:52
The request is pending. Receiving it has not yet created Alice's identity.
0:54–0:58
Maya also selects A. A registrar can carry requests from many users.
1:00–1:03
Ben sends his creation to B, selecting provider B.
1:05–1:08
Cleo chooses C, and sends her signed creation there.
1:10–1:14
B carries the same signed request. Alice's selected provider stays A.
1:16–1:21
A seals Alice, then Maya, into an ordered batch. It extends completed base nine.
1:24–1:28
B's batch contains Ben, followed by that identical Alice request.
1:30–1:35
C seals Cleo's request. All three batches extend the same completed base.
1:36–1:43
The anchor binds a completed base and a pending batch. Only commitments enter Bitcoin; operation bytes stay in registrar storage.
1:48–1:55
Block ten orders these anchors by transaction position: three, eight, twelve. Inside each batch, its committed order comes next.
1:58–2:04
A retrieves B's and C's full batches. Their original copies remain, with the same Bitcoin positions.
2:06–2:15
B and C obtain the same three batches. These are inputs to verification, not accepted history. Every registrar still reports checked through nine.
2:18–2:21
Check each fetched batch against its Bitcoin commitment.
2:22–2:25
Five occurrences now enter the ordered replay queue.
2:26–2:31
Check Alice's signature and current identity state. Then accept her first creation.
2:32–2:34
Maya's creation passes the same checks.
2:35–2:37
Ben's creation also passes.
2:38–2:40
Authenticated again. Already applied.
2:41–2:43
Cleo's creation passes too.
2:44–2:47
B and C check independently. All three agree through block ten.

An illustrative protocol design: this example assumes available, eligible submissions and uses symbolic commitments. Availability and eligibility rules, and cryptographic proofs, remain under design. The film performs no real cryptography.