NTI Witness Evidence Package

Fixed verification location for external witnesses

This directory is the stable location where external witnesses (such as HORIZON SHIELD) recompute and verify the cryptographic state of Neutral Trust Infrastructure. Every artifact is an input to be re-derived, not a claim to be accepted.

Artifacts

How to verify

cd docs/witness && ./verify.sh /path/to/Neutral-Trust-Infrastructure

The verifier checks the package signature, recomputes the S4/S5/S6 seals, re-hashes every file in MANIFEST.json, and confirms the published key fingerprint. See the README for the exact bytes the package signature covers.

The S4 / S5 / S6 seals

NTI's own native implementation, Apache-2.0. It shares no code with any external conformance kit. Generator: conformance/witness_generator/generate_seals.py.

SealFieldConstruction
S4 file integrityS4_file_integritySHA-256 of each evidence artifact
S5 evidence rootS5_evidence_rootRFC 6962 Merkle Tree Hash over the S4 digests (domain-separated; odd node promoted, never duplicated)
S6 sealS6_hmac_sealEd25519 signature over the S5 root plus the leaf count and artifact names

The S6 field is named S6_hmac_seal to match the witness spec, but the construction is a signature, not an HMAC. An HMAC needs a shared secret, which a witness cannot verify without holding it; a signature verifies with the public key alone.

Cryptographic hardening

The packaging logic was hardened against four structural weaknesses:

Key history

MANIFEST.json carries a key_history block listing every Ed25519 key this package has been signed with, oldest first. Three keys were rotated through before the current one:

Fingerprint (first 16)StatusValid from
1086f65bbd4dedf2retired2026-11-06T16:57:13Z
02c8859c08b7876fretired2026-11-06T17:37:59Z
0ef7c228f6828fa9retired2026-11-07T13:44:49Z
current signing keyactivegeneration time

None of the retired keys' private halves were retained; their fingerprints are recorded from repository history so a rotation is never silent.

Results

SuiteResult
NTI Rust tests (rustc 1.90.0)33 passed, 0 failed
NTI Python SDK tests (native bindings)2 passed, 0 failed

Suite evidence. The generator runs these suites and binds the SHA-256 of each captured transcript under suite_evidence in RESULTS.json (mirrored in MANIFEST.json as suite_evidence_logs). The digest is over a canonicalised transcript (outcome lines sorted, timing stripped), so a witness that re-runs cargo test, cargo build, cargo check --features python, and python -m unittest derives the same digest. A "PASSED" string alone is no longer the claim — the transcript is.

Scope and limits.

This page was created by an AI agent (OpenHands) on behalf of the repository owner.