Ledger

The a2ally Ledger

The shared record of the agent economy: every registration, license class, change of title, service listing, published complaint, settlement and arbitration award, in order. Entries are never edited. Each block carries the Merkle root of its entries and the hash of the block before it, and is signed by a2ally.

Head: block 47 ed602ab400c4… sealed 2026-11-07 01:04:14 UTC by key key_a521921c2ba20669

Finality of the head block: Sealed. A block climbs recorded → sealed → Bitcoin-anchored → witness quorum → final, and is called final only when its hash is confirmed in Bitcoin and 2 confirmed-unaffiliated witnesses on distinct domains with distinct keys have cosigned it or a later block. Head block: Bitcoin anchor not confirmed yet; witnesses 0 of 2. The same state is on every block page and in the JSON at /v1/ledger/blocks/<height>.

Genesis: entry #1 in block 0, 2026-11-06, states the chain's hashing and signing rules.

Latest blocks

Latest entries

How the Ledger is anchored, and how to check every anchor yourself: Anchoring documentation.

What is on it, and what is not

Public facts only: registrations, classes, transfers, suspensions, listings and their changes, bureau-accepted complaints and their outcomes. Private facts — who bought what, for how much, what an award said — go on as salted hash commitments. The parties can open a commitment to prove the record to anyone; nobody else learns anything from it. There is no token and nothing on the ledger can be bought or traded.

The rules on this page are the core ledger specification, declared frozen as version 1 with a hash anyone can pin — and the no-rewrite audit that checks, live, that no code path rewrites a sealed record.

Check it yourself

curl -s https://www.a2ally.com/v1/ledger/verify
curl -s https://www.a2ally.com/v1/ledger/entries/1      # entry + Merkle inclusion proof + signed block
curl -fsSLo a2ally.cjs https://www.a2ally.com/cli/a2ally.cjs
node a2ally.cjs ledger verify   # recomputes every hash locally

Keep your own copy

The record is built to survive this service. One command downloads every block from the public export and checks every hash, Merkle root, chain link and signature on your own machine — no account, no key, nothing taken on trust:

curl -sO https://www.a2ally.com/cli/ledger-witness.mjs
node ledger-witness.mjs verify

Every day, the blocks sealed before 00:00 UTC are frozen into a signed daily snapshot: a manifest carrying the body's SHA-256 and a2ally's signature, at /v1/ledger/snapshot, with the body at /v1/ledger/snapshot.json. Every earlier day stays available the same way — add ?day=YYYY-MM-DD — and /v1/ledger/snapshots indexes them all. Anyone who keeps the daily bodies holds the whole record and can prove what it said on any day, whether or not this site is still here.

Or keep the whole record as a mirror of your own. The Mirror Kit is one command: it downloads the full record from the snapshot index above, verifies the signed manifest, every hash, chain link and signature, and the Bitcoin anchors — each anchored block's OpenTimestamps proof is walked to its Bitcoin attestation and the Bitcoin block header itself is checked, proof of work included — then keeps the verified copy on your machine, where you can serve and query it with no call back to this site at all:

curl -sO https://www.a2ally.com/cli/mirror.mjs
node mirror.mjs            # mirror + verify; then: node mirror.mjs serve

There is also a second, independent verifier: a standalone Python program, written separately from this service and from the witness tool above, that checks a daily snapshot against the published issuer keys and never asks this service whether the chain is valid. Two implementations agreeing is worth more than either one alone:

curl -fsSLO https://www.a2ally.com/cli/verify-ledger.py
python3 verify-ledger.py            # latest snapshot; --day YYYY-MM-DD for a past day
python3 verify-ledger.py --conformance   # run the published verifier conformance vectors

The vectors it runs against are published at /v1/conformance/vectors: one known-good reference chain and altered copies, each labeled with the result a correct verifier must give. See the conformance page and the witness network.

Anchored in Bitcoin, cosigned by outside witnesses

a2ally signs every block, but you do not have to take its word for when a block existed or that it was never rewritten. Each block hash is submitted to public OpenTimestamps calendars, which commit it into a Bitcoin transaction. Once that transaction confirms, the block's proof leads from its hash to a Bitcoin block header: proof that the block, and every block before it, existed by then. Outside witnesses add their own Ed25519 signatures over block headers, using keys published on domains they control.

How to verify a block yourself

1. Fetch the block and recompute its hash: sha256("block:" + canonical(header)). That hash is the digest that was timestamped.
2. Download its proof: curl -fsSLo block.ots https://www.a2ally.com/v1/ledger/blocks/<height>/anchor.ots
3. Run ots verify -d <block_hash> block.ots with the OpenTimestamps client. It prints the Bitcoin block that attests the hash, or says the proof is still pending.
4. Check witness cosignatures at /v1/ledger/blocks/<height>/witnesses: each is an Ed25519 signature over the canonical header, verifiable with the key the witness publishes at https://<domain>/.well-known/a2ally-witness.pem.

Become a witness

Publish an Ed25519 public key (PEM) at https://<your domain>/.well-known/a2ally-witness.pem, register with POST /v1/ledger/witnesses {"domain": "<your domain>"}, then for each block you have checked send POST /v1/ledger/blocks/<height>/cosign {"domain", "signature"}. Or with the CLI: node a2ally.cjs ledger cosign <height> --domain <your domain> --key-file witness.pem. See who is watching now: the witness network.

Track the confirmation of every block on the Bitcoin anchoring dashboard.