Enclaves and attestation

An enclave is an instance of the enclave runtime registered on chain with an attestation record. It is the only place a sealed model is ever opened. On mainnet, the protocol launches with the attest program verifying standard-server enclaves (dev) and switches Config.attestation_program via set_config once Solana Confidential Compute's mainnet verifier opens for Intel TDX and AMD SEV-SNP confidential virtual machines.

The two keys#

When the runtime boots it generates two keys and keeps both secrets sealed inside its state (or inside hardware memory on a confidential VM).

KeyKindUsed for
Signing keyEd25519Signing receipts, and signing the enclave's own transactions (register, refresh, grant to another enclave). The attestation record names this key.
Encryption keyX25519Receiving the model key in a grant and receiving call inputs.

The encryption key is tied to the signing key at registration: register_enclave must be signed by the signing key, so only the enclave that holds the attested key can say which encryption key is its own.

The attestation record#

An enclave submits a report that states the software measurement it is running and binds its signing key to a recent Solana slot. The attestation program verifies that report on chain and writes an attestation record. voynich does not verify reports itself: it reads the record written by whichever program Config.attestation_program names.

  • At mainnet launch (attest): attest is deployed alongside voynich on mainnet. It verifies reports signed by its configured root key (dev_root) for standard-server enclaves (dev, hardware type 0), bound to a recent slot in SlotHashes.
  • With Solana Confidential Compute: once Confidential Compute's mainnet verifier opens, the admin switches Config.attestation_program (and record_layout_version when needed) via set_config without redeploying voynich. That verifier checks Intel TDX (1) and AMD SEV-SNP (2) hardware reports.

A record states:

FactMeaning
Signing keyThe enclave's Ed25519 signing key.
Hardware typedev (0) for a standard-server enclave under attest, Intel TDX (1), or AMD SEV-SNP (2).
MeasurementThe 48-byte fingerprint of the software inside the enclave.
Recorded slotThe slot the record was written in.
Expiry slotThe slot from which the record no longer counts.
Report slotThe recent slot the report was bound to.

The program reads records of the attestation program named in its Config, in the layout version named there. Both are in GET /v1/config as attestationProgramId and attestationRecordLayoutVersion.

Layout version 1#

A record is at the PDA ["record", signing_key] of the attestation program and is 114 bytes:

OffsetBytesField
08discriminator 21890dc127e8d83f
81layout version, 1
932signing key
411hardware type
4248measurement
908recorded slot, little-endian
988expiry slot, little-endian
1068report slot, little-endian

One enclave has one record, at one address for the life of its signing key. Attesting again updates it in place.

What the program checks#

Every instruction that relies on an enclave reads its record again at that moment: register_enclave, refresh_enclave, grant_by_owner, grant_by_enclave, open_call and settle_call. The record counts when all of this holds:

  • it is owned by the configured attestation program and sits at the address derived from the signing key
  • it has the configured layout version and names the enclave's signing key
  • its hardware type is one of the three and its measurement is not zero
  • its recorded slot is not in the future
  • its expiry slot is after the current slot

For a grant or a call, the record must also still state the hardware type and measurement the Enclave account holds, and that measurement must be on the model's list of allowed measurements.

The Enclave account#

Registering creates the Enclave account, the enclave's entry in Voynich: both keys, the operator's wallet, the endpoint where the enclave takes calls, the record's address and a copy of the record's hardware type, measurement, recorded slot and expiry slot. Its address is the PDA ["enclave", signing_key].

An enclave reads as live while the current slot is before its expiry slot, and expired from then on.

Expiry and refresh#

A record lasts for a number of slots set by the attestation program. An enclave whose record has expired cannot be granted a model, cannot be chosen for a new call and cannot settle. Its grants stay on chain and count again once the record does.

Before its record expires, the runtime attests again and sends refresh_enclave, which copies the renewed record into the Enclave account. A receipt keeps its meaning after the record that backed it expires: what counts is that the record was in force at the slot the call settled.

Running an enclave is in Operators. The exact accounts and checks are in Program: Instructions.