XPlorer following the chain as its own read-only node

height 1 of 1 on the network. 6 peer(s) connected, 19 known; 0 block(s) followed and 0 pulled in by sync since this follower started. Caught up: this follower holds every block any peer has claimed, so every panel below is the whole chain. Genesis 1cf8655125cc1bbb…, producers genesis.

What this follower is, locally

Node id STR.C16757F87E62. Seeds 127.0.0.1:47001, 127.0.0.1:47002, 127.0.0.1:47003, 127.0.0.1:47004, 127.0.0.1:47005, 127.0.0.1:47007. Its store is held under its own Cerberus lease — no other node’s store is opened, touched or stopped.

STR.talk

STR.talk puts on the chain that a message passed and never what it said. A post carries a position in the thread and a salted commitment; the envelope stays off chain, because a chain stores a thing once and every node then keeps it forever — ciphertext in a block is ciphertext held by whoever breaks that cipher in twenty years. The inbox keys below are public by nature and are the reason a sender cannot be handed a man in the middle by a relay. The thread figures are counts and stay counts.

Inbox keys published0

Threads opened0

Messages passed0commitments; no chain holds the messages

Deliveries acknowledged0signed by the reader, not by the sender

Thread re-keys0

What this page will not show, and why. An index of which domains are in threads together is a social graph, which is the one property STR.talk does not hide — so it is the one a public explorer should not make easy. Held back here:

which domains are in which thread — the participant sets on open and rekey records
who sent which message — the sender domain on a post record
who acknowledged which message — the reader domain on a receipt record
any per-domain thread or message count, which reconstructs the first three

Each of these is on the record, in the records root, and held by every node on the network. The individual rows are rendered in the block that carried them, under /block/{height}/occultation, with the same fields withheld.

Folded from 2 block(s), genesis to 1

Folded from every block this node holds, genesis to 1. Each of these registers is state the chain keeps and the explorer’s read-only port does not expose, so the records in the blocks are replayed here — the same arithmetic every node performed to accept them.

Inbox keys (0)

Published whole, deliberately. A sender who asks a relay where to seal a message has been handed a man in the middle by construction, and no amount of post-quantum in the key agreement repairs an answer from the wrong party. The chain carries these so that two nodes cannot disagree about them.

no domain on this chain has published an inbox key