Vault registry
ChainConfig of per-chain confirmation-policy overrides applied on top of the protocol defaults (confirmation times). Live vault addresses are also served offchain by GET /registry/vaults.
Attestation
The Credential Manager pins which TEE software may run and verifies hardware attestations against it.- Measurement profiles are the approved code measurements.
mrtdmust always match; eachrtmris checked only when non-zero, so one profile can admit several attestation patterns (e.g. different TEE providers). Profiles are added or toggled by the council under a 7-day timelock. - Operator keys. Each operator binds an identity key (an EOA) to a hardware-attested key with
registerAttestedKey; both are required, and the leader must have a registered attested key. - Quote verification is delegated to an external DCAP verifier (
automataVerifier): an SP1 ZK proof establishes that a TDX quote came from genuine Intel hardware running the measured code, and the contract then matches the quote’smrtdandrtmrvalues against an active profile. The verifier address is itself replaceable only under a 7-day timelock.
Restart
After a full quorum outage the protocol restarts from a checkpoint, and the Credential Manager certifies which recovered node becomes leader. It holds anepoch (an era counter bumped on every restart) and the latestCheckpointHash. Certification is a permissionless three-step window:
initiateRestartopens a one-hour gathering window and clears any prior candidate. Anyone may call it.submitRestartProofsubmits a recovered node’s ZK-attested TDX quote, with the claimed leader, checkpoint hash, and epoch bound into the quote’s report data. The contract verifies the proof and measurements, requires the quote’s epoch to be strictly newer than the current on-chain epoch, and keeps the highest-epoch candidate. Two candidates at the same epoch with different checkpoint hashes mark the restart ambiguous — a detected split brain.resolveRestart, callable once the window closes, installs the best candidate as the new leader, stores its checkpoint hash, and advancesepoch— unless the restart is ambiguous, in which case it reverts and no leader is certified.
Governance
High-risk changes are timelocked:
Vault registration, operator-set changes, and committee thresholds are quorum-gated council operations. Operator constraints, attestation, and the recovery council: trust model.