Trust
Transparency dashboard
The state of the platform, including the parts that are not finished.
| Platform status | Development |
|---|---|
| Current Accord version | 1.1 |
| Total active signatures | 4 |
| Identity verified | 0 |
| Email verified only | 0 |
| Countries represented | 3 |
| Counters last recalculated | 16 days ago |
| Audit chain | Intact, 304 events verified |
| Bot challenge | Active |
| Signing attempts, last 24h | 0 |
| Challenged, last 24h | 0 |
| Blocked, last 24h | 0 |
| Last daily manifest | None yet |
| Manifest chain | No manifests yet |
| Manifest signing key | Ed25519, public key published |
| Methodology version | 1.0 |
| Independent security audit | Not yet performed |
Daily signed manifests
Each day’s totals, hashed together with the previous day’s manifest, forming an append-only chain that anyone can verify, without putting a single person’s data on a public ledger.
None yet. The first manifest is published after the first full day. We do not backfill manifests for days that were never signed at the time.
Check it yourself
You do not have to take our word for any of this. Everything needed to verify the chain is public.
- /api/v1/transparency/manifests , every manifest, with its hash and the hash it links to
- /api/v1/transparency/public-key , the Ed25519 key the signatures are made with
/api/v1/transparency/manifests/<date>, one day’s document, in the exact canonical bytes the hash was taken over/api/v1/transparency/verify-receipt?receipt=<id>&date=<date>, proof that one signature was counted on a given day
Changing a past number breaks that day’s hash and every hash after it. Recomputing the hashes to match requires the private signing key. The Merkle root lets an individual signer prove their own signature was included, without us ever publishing a list of who signed.