Attestation transparency
Nested under the public audit checklist: QSDM validators may optionally publish a signed NVIDIA NGC proof bundle as a transparency signal. The widget below shows how many validators on this network have published a fresh attestation within the last 15 minutes, over the total number of publicly-known validators.
Scope: NVIDIA-lock is an opt-in, per-operator API policy —
not a consensus rule. Consensus is designed to run on CPU via Proof-of-Entanglement + BFT
and to admit validators without a GPU. A missing or stale attestation never causes
a validator to be excluded from consensus, block proposal, or finality. Today the pilot
network (pre-mainnet) runs a single block producer during recovery. Signed consensus is
enforced (since block 827,000 every BFT vote and message must carry a valid ML-DSA signature),
but there are no independent validators yet, so multi-validator BFT is not yet running;
see live status and network upgrades.
See NVIDIA_LOCK_CONSENSUS_SCOPE.md.
Attestation API is on the internal audit checklist.
Six
trust_api checklist rows pin
/api/v1/trust/attestations/*.
See audit.html?category=trust_api.
Attested validators
— of —
Fresh window: —
Last attested: —
Last checked: —
Recent attestations
| Node ID (redacted) | Age | GPU arch. | HMAC | Region |
|---|---|---|---|---|
| loading… | ||||
Node IDs are redacted to the first 8 + last 4 characters. Region is coarse-grained (eu / us / apac / other). The scraper aggregates public peer state only; inside the network, each validator holds the same information unredacted for reconciliation.