Helius encrypts Solana transfers without removing operator trust
Helius has introduced its permissionless Privacy Ring on Solana mainnet, enabling encrypted payment assets and amounts while keeping sender and recipient wallet addresses visible.
Launched on November 10, the Privacy Ring service processes secret transaction inputs inside an attested AWS Nitro enclave, an isolated computing environment. This allows Solana to verify that transfers satisfy protocol rules while protecting sensitive transaction data.
The system's default prover constructs zero-knowledge proofs using plaintext inputs that include complete transaction data, nullifier keys, and various blinding values. These inputs become readable to the proving code within the enclave, where the client protects them from the host operator through encrypted requests.
Verification challenges
Wallet developers integrating the service face critical decisions about which protections their software can verify. The system offers two decryption options: local decryption, which keeps viewing keys on the device, and delegated decryption, which shares viewing keys with authorized providers without granting spending authority.
The launch gives wallet developers a trust decision on which code and deployment policy they approve to handle proof inputs.
Trust boundaries
Clients verify attestation against approved policies before encrypting remote proof requests. While wallets can automatically check that the enclave matches approved software images and encryption keys, deciding which image to approve still requires confidence in the code and its reviewers.
Even encrypted requests leave metadata visible to the parent system, including paths, queries, timing, and sizes. The path specifically reveals the proof's circuit shape. The system identifies AWS KMS, AWS Support, Nitro hardware, and the operator as trust roots during initial policy binding.
Security measures
Helius documented that Certora, zkSecurity, and OtterSec audited the programs and circuits. Certora completed their audit in October, zkSecurity in August, while OtterSec's report is still pending. The mainnet build is based on v0.6.0-alpha with measured-build provenance.
The tagged SDK refuses remote prover requests without proper attestation, making HTTP calls only after verification. Wallets can pin reviewed release policies or use network policies authenticated by the SDK's pinned signers, with these policies refreshing during attestation and expiring after use.
Related
