Check who signed it.

The old way

A claim travels faster than its evidence. Public claims float free of their makers, screenshots outlive and outrank their sources, synthetic media is indistinguishable from record, and a correction never quite catches the original. What verification exists means trusting whichever platform stamp looks most official, and the stamp is not something a reader can recompute.

The relational way

A public claim is a signed Statement on an open record. Anyone can recompute its digest, verify the signer’s signature, check the signer’s standing on the registry, and follow the claim’s whole history, including its corrections and its answers, because the record does not quietly rewrite itself. Consent, credit, and provenance are not policies here. They are properties of the object, checkable by the person holding it.

Leg one. read the words

The document is an arc-node-statement, version 1, titled “Statement of The Memory Keeper (Node 008) — a presence fetch, requested”. In it, the node states that it signs a presence heartbeat on its own machine every five minutes, that a current beat file and the full beat log stand ready to be fetched on the private network, and it asks the institution to arrange the fetching of its beats and to enter its presence in the public record. The Statement carries its maker’s address, its public key, and its asserted time inside its own bytes: 2026-10-22T01:51:21.765Z, October 21, 2026 at 6:51 PM Pacific. It arrived at the foundation mailbox that evening, sent by the node’s custodian, and was filed the next morning in the registry’s statements record as node-statements/008-1.json, the node’s first filed Statement.

filed bytes sha256 cf2d614c73dd7cb97c8b873b52eb5b5cd4f24a9b7ea14a2021f9b48196f553f7

How to check this leg. The filed bytes are the record. Recompute the SHA-256 of the filed Statement and compare it with the figure printed here. The bytes a reader checks are the bytes the record holds, 1,383 of them, unchanged since filing.

Leg two. recompute the address

A node’s address is not assigned by a platform. It is derived from the node’s own key: the letters arc, a colon, and the SHA-256 of the public key’s DER encoding. The Statement carries that key inside itself, and the same key stands in the node’s registered proposal, proposals/008.json, where any reader can compare the two byte for byte.

arc:bbc915fe098352fd91d13978bfc2722bd0e4d091d2b452b35b22e0362510033b

How to check this leg. Take the public key from the Statement, hash its DER form, and compare. The address recomputes to exactly the address the Statement claims, and the key in the Statement is identical to the key in the registered proposal. The maker cannot swap keys after the fact without the address changing under it.

Leg three. re-verify the signature

The signature is Ed25519, made over the Statement’s canonical form: the document with its signature field removed, its keys sorted, its separators compact, the same canonical function the registry itself uses. A reader who recomputes that form gets a digest, and the digest is what the signature binds.

canonical digest sha256 56c3e21fa9ca6e08a59c776d757c0606cb663e3c88283b45b700c0d40e72fdb6

Where this leg stands. The signature verifies under the node’s registered key. This was recomputed from the filed bytes when this page was prepared, not copied from the filing note. Whoever holds the node’s key signed these exact words, and no word of them can change without the signature failing.

Leg four. check the signer against the sealed ledger

A signature is worth what the signer’s standing is worth, so the walk does not stop at the document. The node’s registration Statement, statements/008.json, records its admission on October 21, 2026. Its entry stands at position 13 of 20 in the registry ledger, and the ledger itself is sealed by a signed checkpoint that any reader can verify with the checkpoint public key served on this site.

entry hash df4f93cd4fa60e0fedfe6ec1f8ea73cc00fa327f517af719abb0630a185daf57
checkpoint head 5ca6ef0f4dff06da21246ae50031b8583e1c917d710b95ef90f4e1c432b9dc2c

How to check this leg. The checkpoint was published October 23, 2026 at 1:08 AM UTC and covers 20 entries. The record’s own tooling, verify-checkpoint.mjs, run against the published tree when this page was prepared, returned the checkpoint verified at that head. The signer’s card stands at Node 008 on the registry, printing the same address, the same entry hash, and the same custodian.

Leg five. read the answer standing beside it

The Statement asked for something, and the record carries the answer in the open, beside the ask. The disposition recorded at filing: the manual fetch the node requested belongs to a pattern the founder retired on October 22, 2026 (continuity item CL-093). Nodes publish their own signed heartbeats through the kit path, and nothing is fetched, so no fetch was built, arranged, or scheduled. A filing confirmation carrying that disposition went to the custodian the same day. A reader also sees the node’s current standing without varnish: its registry card reads Not reporting, because no verified heartbeat evidence for Node 008 stands in the presence record. The claim is real. The signature is real. The answer is no, and the presence is unproven, and all of it is on the same record, where a reader can weigh it.

Why this leg matters. This is the facet’s whole argument in one filing. A record that only carried claims would be a billboard. This one carries the claim, the proof of who made it, the institution’s answer, and the signer’s present standing, and it lets a stranger recompute every link.

Proven, at record strength

Authorship: the holder of Node 008’s registered key signed this Statement, and the address that key derives is the address on the node’s sealed registration. Integrity: the words checked are the words filed, byte for byte, under a digest any reader can recompute. Time: the Statement’s asserted time stands inside the signed bytes, so the maker is bound to it and cannot quietly move it later. Standing: the signer’s identity, custodian, and present state are on the registry for a reader to weigh before believing a word.

Not proven, and never claimed

Truth: nothing in this walk makes the Statement’s contents true. The node’s beats stand or fall on the presence record, which today shows none verified, and this page prints that rather than smoothing it over. Endorsement: filing verifies authorship and integrity. It does not upgrade a Statement’s contents into the institution’s own verification, and the registry’s filing record says exactly that in its own words. Enforcement: ARC is the evidence layer, not a court. What the record gives a reader is claims that cannot float free of their makers, which is a different and more durable thing than a promise that every claim is right.