For developers

Verify it yourself

The ledger is a transparency log: every event is signed (DSSE, Ed25519), hashed into an RFC 6962 Merkle tree and sealed by a signed checkpoint. Three commands:

1. Mirror the log

   The raw entries, the signed checkpoint and the public key — static files on this site.

   mkdir ew && cd ew && curl -sf --remote-name-all https://vitalearth.io/ledger/entries.jsonl https://vitalearth.io/ledger/checkpoint && curl -sf https://vitalearth.io/ledger/pub -o ledger.pub

2. Re-derive everything

   Checks every signature, the canonical form of every entry, every trust rule (no publication without confirmation and review), and that the root matches the checkpoint.

   EARTHDECK_LEDGER_DIR=. npx -y earthdeck ledger verify

3. Prove history wasn’t rewritten

   Keep today’s checkpoint. Next time, check that the new log extends it — a consistency proof, not a promise.

   EARTHDECK_LEDGER_DIR=. npx -y earthdeck ledger verify --trusted ../saved-checkpoint

Signed root

98f501ea7b18…03d8f3

Entries

23

Data feeds & API

• feed.jsonpublished cases (JSON Feed)
• feed.geojsonpublished cases as GeoJSON
• api/ledger.jsonevery finding, public or not
• api/stats.jsoncounts and false-positive rate per rule
• api/pulse.jsonworld pulse snapshot (when available)
• ledger/checkpointsigned checkpoint
• ledger/publedger public key
• ledger/entries.jsonlthe full log
• schema/finding-event.v1.jsonevent schema (JSON Schema)
• Trust policywhat gets published, and why

Source code

Source code: coming.