Key security

Hardware enclave

Also called: Secure enclave, Trusted execution environment, TEE

An isolated compute environment, enforced by hardware, that even the machine's own operators can't read or log in to, and that can prove which code it runs.

A hardware enclave is a protected area of a machine with its own memory, separate from the host. The host's operating system and administrators can't look inside, change what's running or copy data out. Code inside talks to the outside only through a narrow channel.

What makes enclaves useful for custody:

  • Keys can be generated and used inside, never existing anywhere else.
  • The signing rules run inside too, so a compromised server can't make the enclave sign something the rules forbid.
  • The enclave can prove what it's running with remote attestation, a document signed by the hardware vendor.

On Valtu

Wallet seeds are generated and used only inside hardware enclaves with no disk, no network and no operator access. Secrets are released to an enclave only when its image matches the published measurement. Production runs two enclave hosts. With team signing on, the enclave itself verifies your approvers' passkey signatures before it signs, so not even Valtu's servers can push through a payout your rules don't allow. More on the security page.

Related terms

Keep reading.

More in key security: Reproducible build · Key ceremony · Shamir secret sharing · MPC wallet · Multisig · Approval policy · Passkey. The whole glossary.

Put it into practice.

Every workspace starts on testnets with free test coins: same dashboard, same API. Go live when your team is ready.