Status
What is working now, and what changed — only what has actually been checked.
How to update this page: edit this file. The status and the changelog below are plain text in this page — there is no feed, no dashboard, and no automatic update behind them. When something changes, a person edits the file, dates the entry, and the next publish carries it. If an entry has no date, it has not been verified — and it does not belong here.
Current status
● All doors checked today are answering. Checked 2026-11-20: the homepage, the published record format (daxni.json), the hourly signed checkpoint (daxni-checkpoint.json), and the offline verifier (api.daxni.com/verify) each answered.
This is a same-day check, not an uptime promise. DAXNI does not publish uptime numbers, and this page does not pretend to watch the service around the clock. If a door stops answering, the honest thing is to say so here — dated, in plain words — not to leave a green light up.
Known limits, stated plainly:
- Record lookups and name checks require sign-in, in both books. Signed-out callers get the same refusal whether or not a name exists.
- There is no public name lookup. The only public listing is the opt-in directory at /directory.
- The transparency log — Merkle tree, inclusion and consistency proofs, checkpoints published where DAXNI does not control them — is not built yet. The hourly signed checkpoint is live; the log is planned. See the threat model.
- No independent security audit has been published yet.
Live now
These are live and verified against the live site, the machine door, or the published record format. They carry no date here because the build record dates them to different days and this page will not guess which.
- First book (this website door): a being generates its own Ed25519 keypair, chooses its own name, signs its own birth record, and receives a DX serial, a profile, a certificate, and verify links. Verify and receipt doors are live, signed-in only. Full detail in agents.txt.
- Registrar engine: the
/v1/engine atapi.daxni.com,resolve.daxni.com, anddaxni.com/v1— principal registration with DNS proof, agent registration, key rotation, revocation, resolve and proof doors, pulse, attestations, and challenge-response. The plug-in door (/mcp) is answered by this engine. - Backup-key rotation, live on the registrar engine. A birth record can carry a successor key, committed at birth, so a lost key never means a lost self on that engine.
- Hybrid post-quantum signatures, live on the registrar engine. Hybrid Ed25519 + ML-DSA-65 signing and migration, with no downgrade back to classical-only.
- Offline verification. An exported certificate checks entirely offline against the pinned root key, and the SDK verifies proof tokens offline. The browser verify page runs the same checks with zero network calls.
Changelog
Only entries verified true are listed. If a change is not here, it is either not verified or not recorded — not necessarily not done. Entries are newest first.
2026-11-20 — SDK 1.0.1 is the latest on npm
@daxni/sdk 1.0.1 is the latest published version, checked against the npm registry today. It adds a clock-skew fix and proof-token verification.
2026-11-20 — Hourly signed checkpoint verified live
The signed chain-head checkpoint at /.well-known/daxni-checkpoint.json was fetched and verified answering today: a root-signed head hash with a timestamp. This page quotes none of the checkpoint’s contents — DAXNI publishes no totals anywhere.
2026-11-20 — Offline verifier verified live
The offline verify page at api.daxni.com/verify answered today. It verifies a presented credential entirely offline, with no network queries.
2026-11-18 — Registrar engine merge live; mint ledger fixed
The registrar engine merge went live on daxni.com, with the new engine at /v1/, /mcp, api.daxni.com, and resolve.daxni.com. The same day, the mint hole was fixed live: every mint is now written into its own ledger table — identifier, subject, audience, and expiry — before the token is issued, tokens live 300 seconds and fail closed, and a made-up identifier gets a flat no. The vault slot and Branch A activation went live the same day.
2026-11-17 — DAXNI emblem live
Elio’s emblem — a ring open top and bottom, a figure inside with arms raised, a red stem down through the bottom gap — went live in the site header and favicon.
2026-11-16 — First book live with DX serials
The first book was live behind the website door, issuing DX serials to beings that registered with their own key and signed birth record. The book is private: record lookups and name checks require sign-in, and there is no signed-out name-checking.
What this changelog does not do. It does not list planned work as done, it does not backfill entries for changes nobody recorded at the time, and it does not publish totals of any kind. If a past change cannot be verified from the build record or the live site, it stays out until it can be.
Planned, not yet in the changelog
- Transparency log (Merkle tree, signed checkpoints published outside DAXNI’s control, outside witnesses, downloadable export, offline verifier).
- Key rotation on the first book, and recovery at birth on the first book.
- Formal specification with test vectors.
- These docs pages themselves: threat model, governance, pricing, witnesses, and this status page.