Skip to main content
A Confidential call runs inside a sealed, hardware-isolated environment. An attestation is the signed statement, produced by that hardware, describing what was running inside it. Attestation is what makes the claim checkable. You supply a fresh random value (a nonce) with the request. You get back the raw hardware evidence, a structured summary, and whether the evidence passed Nito’s baseline checks.

​
The Boundary to Understand First

Nito is a baseline verifier, not a full hardware-quote verifier. Nito checks that the evidence is present and well-formed, that the proof format and signing material are there, that the fresh value you supplied is echoed back, and that the binding between the evidence and your request holds. Nito does not verify the underlying hardware evidence: the raw hardware quotes, certificate chains, certificate revocation lists, or Trusted Computing Base policies. Those are yours to complete, on the raw evidence Nito returns. So a Nito result is baseline-verified, attested, and verifiable. It is never “fully verified,” because Nito alone does not establish full hardware trust.

​
Anti-Replay Is Caller-Driven

Nothing stores nonces between requests. Supply a fresh random value every time and the baseline enforces that the evidence was produced for this request. Omit it and an empty-binding report is permitted, which gives you no replay protection. Replay resistance is a property of the protocol you follow, not an unconditional guarantee. Full treatment: the report-data binding.

​
This Section

Confidential Level

The level attestation backs.

Attestation Pipeline

The end-to-end flow of a Confidential attestation.

Verify It Yourself

Become the final verifier.