Skip to content

v0.1.1 — dual-vendor authenticated, measured-VM attestation

Choose a tag to compare

@ai-hpc ai-hpc released this 12 Jul 00:05
d474848

Hardens v0.1.0's proof of training into fully authenticated, measured-VM attestation. Every trust gap closeable with today's infrastructure is now closed — nothing in a submission is taken on the miner's word.

Highlights

Intel TDX measured-VM proof (#45#47)

  • On TDX guests (Targon CC VMs), eval.attestation captures an Intel TDX quote via configfs-tsm with the bundle's claim_sha256 in its 64-byte REPORTDATA; MRTD (guest-image measurement) recorded. eval.verify reports the binding as tdx_bound.
  • The baseline ledger run was re-attested with GPU + TDX binding.

Quote and token authenticity — dual vendor (#48, #49)

  • Intel DCAP verification (tdx_signature): the TDX quote's ECDSA signature, PCK certificate chain to Intel's root CA, QE identity, and platform TCB status validated against live Intel PCS collateral ("UpToDate" + no advisories is the clean pass).
  • NVIDIA JWKS verification (gpu_signature): every NRAS-signed JWT in the GPU attestation (platform + per-device, ES384) validated against NVIDIA's published JWKS with issuer and expiry enforced; the SDK-local overall JWT is intentionally not counted as evidence.
  • A hand-crafted attestation JSON now fails signature verification on both sides.

Verification robustness (#51)

  • Found by the full live function test: honest claims were rejected on 2.1pp of cross-server generation drift (3-problem triton quick set). Benchmarks gain per-benchmark claim_tolerance_pct (triton: 5pp while the problem set is tiny) and the eval server pins determinism (--seed 0 --no-enable-prefix-caching).

Verified live on the baseline run

claim_bound:           true              (claim digest in the GPU attestation nonce)
gpu_signature:         true, 2 tokens    (NVIDIA JWKS, ES384)
tdx_bound:             true              (claim digest in TDX REPORTDATA)
tdx_signature:         true, UpToDate    (Intel DCAP / PCS)
checkpoint_hash_match: true

Full details in CHANGELOG.md. The frontier to beat remains triton 0.4278 — see runs/frontier.json.