Vaulkry is a managed remote signer for Ethereum validators. Your signing keys are used only inside a confidential VM that has proved, with hardware-signed evidence, that it is running our published signer — and every launch of that signer needs your approval.
Request early access See how it worksEvery validator operator faces the same two risks: a stolen key, and a slashable double-sign. Vaulkry is built around both.
The signer runs in an AMD SEV-SNP confidential VM. Keys are released to it only after it proves its measurement, encrypted to a key that exists only inside that VM — so a relayed or replayed proof gets nothing it can open.
You hold your own authority key, generated on your own machine by the Vaulkry approver. A signer cannot start serving your validators until your approver confirms it. We never receive that key.
An EIP-3076 slashing database inside the signer, and a second high-water mark kept outside it. A restarted signer reconciles against both and waits two epochs before signing.
Have keys generated inside the enclave (you receive an encrypted backup), or import an encrypted key set you already hold. You choose at purchase.
Your validator client points at Vaulkry's remote-signing endpoint. Lighthouse configuration is provided; tell us your client and we will confirm support.
A signer's certificate lasts 24 hours and is re-earned by fresh attestation, so material from a signer that has stopped stops being useful within hours.
Five steps from purchase to signing. Plans are prepaid monthly by validator count, with a minimum of 10 validators; pilot pricing on request.
The number of validators (minimum 10), and whether keys are generated by Vaulkry or imported.
Run the Vaulkry approver on a machine you control. It creates your authority key and confirms each signer launch.
A confidential VM proves what it is running before any key is released to it.
Generated inside the enclave, or imported from an encrypted key set you upload to your own storage area.
The remote-signer URL and your own client certificate, pinned by your authority key.
We would rather state the trust you place in us than imply it away.
Vaulkry runs on Microsoft Azure confidential VMs. The AMD processor and Azure's platform firmware are part of the trust base.
So a signer can restart or move without you re-uploading, a backup of your key set is encrypted under a key specific to you, on a separate confidential custody host that releases it only to an attested signer you approved.
During the pilot, the published reference values are not yet signed and diagnostic logging is enabled. Both close before general availability.
Keys are used only inside the attested confidential VM's encrypted memory, and our operators have no access to that memory. Two honest qualifications: generated keys are also delivered to you as an encrypted backup (only you can open it), and the custody residual described under “What you are trusting” remains.
No. Vaulkry needs only validator signing keys. Never upload withdrawal keys or a seed phrase.
It attests again, your approver confirms the launch, its slashing record is reconciled against the external high-water mark, and it waits two epochs before signing. If your approver is offline, the signer waits for it.
Clients that support the Web3Signer remote-signing API. Lighthouse configuration is provided today; tell us your client and we will confirm before you join.
Yes — 10 validators per customer. Each customer's signer runs in its own confidential VM, the isolation the service is built on, and that sets a floor on what a plan can cost.
Yes: choose an import plan and upload your key set encrypted to your signer. Once your validators sign through Vaulkry, retire the old signer so the keys are never live in two places.
On Azure confidential VMs. Vaulkry is fully managed only: the guarantees depend on us controlling the platform end to end.
The key exchange and the custody path are modelled in ProVerif against published relay and diversion attack models. We will publish the models with the release; ask us for them in the meantime. They are a symbolic protocol analysis, not a proof about the hardware.
Vaulkry is built for operators running 10 or more validators. Tell us how many you run, which client you use, and whether you would generate or import keys. We will reach out about the pilot.
Request early access[email protected] · No commitment and no payment during early access.