/ manifest
append-only · merkle-rooted · ceremony-signed
Manifest.
The 3DCIPHER manifest is the public record of cryptographic and AI-artifact state. Ceremony root, build keys, customer roots (by anonymous fingerprint), signing-scheme revisions, advisories, firmware hashes, AI model bundle hashes, and evidence-schema revisions. Append-only. Every revision signed by the build keys; the build keys themselves signed by the ceremony root. The revision below is the current head.
Current head.
revision: current
signed_at: 2026-05-19T03:00:14.082Z
signed_by: build_key_2026q2 (fingerprint 0x3B81...4A12)
merkle_root: 0x7c4a2f9b...e802d188
previous: 2026.05.r18 (2026-05-12T03:00:09Z, merkle 0x9d12...7f30)
height: 18,402
ceremony_root: 0xA1F4...9C2D
phase: 0 (Ed25519 + Dilithium-3 shadow)
Ceremony root.
| field | value |
|---|
| fingerprint | 0xA1F4…9C2D |
| created | 2024-09-14T11:38:00Z |
| scheme | Ed25519 (Dilithium-3 shadow per 3DC-2026-05-A1) |
| quorum | 5-of-9 across three jurisdictions |
| observer | Dr. M. Karras (formerly NCSC); observer report delivered in signed customer package |
| rotation policy | every 36 months; planned 2027-09 ceremony |
| compromise procedure | RB-01 (ceremony-key compromise); RB-09 (emergency quorum) |
Build keys.
Build keys sign manifest revisions, advisories, firmware, schemas, and SDK packages. Rotated quarterly; the rotation event is itself a manifest entry signed by the previous build key and counter-signed by the ceremony root.
| key id | fingerprint | active period | scheme | status |
|---|
| build_key_2026q2 | 0x3B81…4A12 | 2026-04-01 → 2026-06-30 | Ed25519 + Dilithium-3 shadow | current |
| build_key_2026q1 | 0xD207…6FE0 | 2026-01-01 → 2026-03-31 | Ed25519 + Dilithium-3 shadow | retired (verifies historical) |
| build_key_2025q4 | 0x4F18…A87C | 2025-10-01 → 2025-12-31 | Ed25519 | retired |
| build_key_2025q3 | 0xB7CC…5219 | 2025-07-01 → 2025-09-30 | Ed25519 | retired |
| build_key_2025q2 | 0x86A4…3DD7 | 2025-04-01 → 2025-06-30 | Ed25519 | retired |
| build_key_2025q1 | 0x2E0E…7C18 | 2025-01-01 → 2025-03-31 | Ed25519 | retired |
| build_key_2024q4 | 0x9F77…0BB6 | 2024-09-22 → 2024-12-31 | Ed25519 | retired (first post-ceremony) |
AI artifact registry.
Customer deployments pin AI model bundles and evidence schemas through the manifest. A verifier can check which model family prepared a TwinCert draft or MeshGuard detection result without trusting the UI.
| artifact | purpose | verification material |
|---|
| meshguard-detector-2026.05 | watermark detection and confidence scoring | model hash + signed threshold profile |
| evidence-extractor-2026.05 | inspection and material-lot field extraction | model hash + schema compatibility range |
| anomaly-scorer-2026.05 | printer posture and bundle-context triage | model hash + deployment policy id |
| audit-summarizer-2026.05 | reviewer-facing audit notes | model hash + prompt/policy bundle hash |
Customer root anchors.
Customer roots are published by anonymised fingerprint only. The customer themselves controls the name-to-fingerprint mapping; we do not disclose customer identity.
| customer fingerprint | anchor date | scheme | printers |
|---|
cust:0x4a02…1b88 | 2024-11-02 | Ed25519 + Dilithium-3 shadow | 11 |
cust:0xee71…7330 | 2024-12-19 | Ed25519 + Dilithium-3 shadow | 4 |
cust:0x9032…8a1c | 2025-01-30 | Ed25519 + Dilithium-3 shadow | 22 |
cust:0x18ad…5e62 | 2025-03-08 | Ed25519 + Dilithium-3 shadow | 6 |
| … 37 further customer roots, page 2 (signed roll-up); the customer console exposes per-customer roll-ups for entitled customers only. |
Signing scheme history.
| revision | scheme | active from | note |
|---|
| SCH-2026.01 | Ed25519 + Dilithium-3 shadow (phase 0) | 2026-01-09 | per 3DC-2026-05-A1 |
| SCH-2025.04 | Ed25519 (bundle schema v2 default) | 2025-04-18 | v1 deprecation announced |
| SCH-2024.09 | Ed25519 (bundle schema v1) | 2024-09-22 | first post-ceremony scheme |
Firmware manifest.
Production firmware hashes, current and the two preceding releases. Older releases live in the signed archive; the archive itself is referenced by Merkle root from the current head.
| release | date | SHA-256 | RB |
|---|
| fw 2026.05.r3 | 2026-05-12 | 2c8e…1c80 | RB-25 dual control |
| fw 2026.04.r2 | 2026-04-08 | 7a14…3a91 | RB-25 dual control |
| fw 2026.02.r1 | 2026-02-20 | 9b40…ff62 | RB-25 dual control |
Merkle proof for the current head.
# the head's Merkle root commits to the full leaf set;
# the verifier-CLI can produce a Merkle path for any leaf you care about.
$ 3dc-verify manifest path \
--manifest current \
--leaf "build_key_2026q2"
ok leaf "build_key_2026q2" committed to root 0x7c4a...d188
path: 18 hashes, depth 14
verifies under ceremony root 0xA1F4...9C2D
$ 3dc-verify manifest path \
--manifest current \
--leaf "cust:0x9032...8a1c"
ok leaf committed to root 0x7c4a...d188
path: 18 hashes, depth 14
verifies under ceremony root 0xA1F4...9C2D
Recent manifest revisions.
| revision | signed at | merkle root | notable |
|---|
| current | 2026-05-19T03:00:14Z | 0x7c4a…d188 | (current head) |
| 2026.05.r18 | 2026-05-12T03:00:09Z | 0x9d12…7f30 | 3DC-2026-05-A1 PQ plan announce |
| 2026.05.r17 | 2026-05-05T03:00:11Z | 0x2a08…ee61 | routine |
| 2026.04.r4 | 2026-04-28T03:00:08Z | 0x0ca7…ff20 | 3DC-2026-04-A2 MeshGuard field report |
| 2026.04.r3 | 2026-04-21T03:00:13Z | 0x7720…c813 | routine |
| 2026.04.r2 | 2026-04-15T03:00:10Z | 0xa402…1cd9 | 3DC-2026-04-N1 Magics attestation notice; fw 2026.04.r2 |
| 2026.04.r1 | 2026-04-07T03:00:09Z | 0xd811…5e02 | build_key rotation 2026q1 → 2026q2 |
| 2026.03.r2 | 2026-03-14T03:00:08Z | 0xb077…6a31 | 3DC-2026-03-A1 NIS2 profile |
| … | … | … | … |
Cadence and SLOs.
- Routine manifest revision: weekly, every Tuesday 03:00 UTC.
- Out-of-cadence revision: triggered by advisory issuance, firmware release, or key rotation. Notified via the signed advisory channel.
- Build-key rotation: quarterly (Q1/Q2/Q3/Q4 boundaries).
- Ceremony-root rotation: every 36 months; next planned 2027-09.
- Manifest publish latency SLO: revision signed and published within 5 minutes of the rotation event; live since 2025 Q1.