Run an enclave

An operator runs the enclave runtime, receives grants to sealed models, and is paid a share of every call the enclave settles.

What an operator runs

One process: the enclave runtime. It makes its own keys, attests on chain, registers, watches for grants, fetches a model’s ciphertext from chain and opens it in memory, answers encrypted calls, signs each answer and settles it.

There is no deal to strike with a model’s owner. The owner lists the measurements allowed to open the model, and any enclave running that software can be granted it, by the owner or by an enclave that already holds it.

Run the enclave runtime
Enclaves registered
0
Calls settled
0
each with a receipt
Paid to operators
0
from the first settled call

Attestation records and runtime modes

An enclave is trusted because of its onchain attestation record. Mainnet launches with the attest program verifying signed reports for standard-server enclaves (dev) without TDX or SEV-SNP hardware.

Voynich reads the record from whichever verifier Config.attestation_program names at registration, at every grant and at every settlement. Once Solana Confidential Compute’s mainnet verifier opens, set_config switches to it for Intel TDX and AMD SEV-SNP confidential VMs.

Hardware in the docs
  • Standard server (dev)Active on attest
  • Intel TDXVia set_config when verifier opens
  • AMD SEV-SNPVia set_config when verifier opens

From boot to a paid call

The operator starts the runtime. From there the enclave attests, registers and serves on its own, and the grant comes to it.

Register and get granted
  1. Boot
    Signing and encryption keys

    The runtime starts on a standard server (or a confidential VM) and makes its keys.

  2. Attest
    Attestation record

    The report is verified on chain by attest (or Confidential Compute after set_config): key, type, measurement, expiry.

  3. Register
    Enclave

    With the operator’s wallet and the endpoint it answers on.

  4. Receive a grant
    Model key, wrapped

    From the owner or from a granted enclave. It fetches the ciphertext and opens it in memory.

  5. Serve
    Receipt

    Every settled call pays the operator’s wallet its share of the price.

  6. Refresh
    Next record

    It attests again before the expiry slot and goes on serving.

What a call pays and where it lands

A model’s owner sets its price per call and the operator share of that price. The caller’s payment waits in escrow until the enclave settles the call with its signed answer.

Settlement splits the price in one instruction: the operator share to the operator’s wallet, the protocol share, and the rest to the owner. There is nothing to claim afterwards. The payment and the receipt arrive together.

Earnings in the docs

No model is sealed under the name sketch-32.

The runtime attests on its first start. Registration takes the operator’s wallet and an endpoint.