Customers /
Uniswap
How Uniswap runs Unichain transaction signing on AWS Nitro Enclaves
INDUSTRY
Digital Assets
LOCATION
New York
SIZE
200+ employees
SOLUTION
Enclaves on AWS Nitro
OUTCOMES
Over twelve months of engineering time saved.
All Unichain transaction signing runs inside AWS Nitro Enclaves.
No operator at Uniswap or Evervault can access a signing key.
Uniswap is the largest onchain marketplace. Unichain is its Layer 2 network. Unichain transactions must be signed somewhere no one can access the signing key, not even Uniswap's own engineers.
The challenge: getting from Nitro to production
AWS Nitro Enclaves can provide that guarantee. But running a service inside one is a separate problem. You need to build and sign enclave images, provision certificates onto a machine with no disk, generate and verify attestation, and keep enclaves healthy through every deploy. Evervault built Enclaves after solving these problems for its own encryption engine.
Signing inside attested enclaves
Uniswap deployed Unichain's signing service into Evervault Enclaves. Signing now runs inside attested enclaves. Evervault handles deployment, scaling, certificate provisioning, and attestation. Uniswap's team wrote the signing service and didn't have to build any of the infrastructure underneath it.
The AWS architecture behind the signing service
This runs AWS Nitro Enclaves on Amazon EC2, one enclave per instance, orchestrated with Amazon ECS so no other tenant shares the machine. Clients verify the AWS-signed attestation document on every connection. The enclave authenticates against Evervault's encryption engine, which holds its root key material in AWS Key Management Service and only releases it against a valid Nitro attestation. Amazon S3, ECR, RDS, Lambda, and CloudWatch handle storage, deployment, and observability.
Build like Uniswap
Evervault Enclaves runs your most sensitive code where no one, including your own team, can access it.
© 2026 Evervault Inc. All rights reserved.