Helius launched its permissionless Privateness Ring on Solana mainnet on Nov. 10 with encrypted cost property and quantities, whereas sender and recipient pockets addresses stay seen.
Its documented default prover, the service that constructs zero-knowledge proofs, provides a {hardware} requirement the place secret transaction inputs are processed inside an attested AWS Nitro enclave, an remoted computing surroundings.
Solana can examine {that a} switch satisfies the protocol’s guidelines, however defending the inputs whereas that proof is made depends upon the prover’s isolation, code, and deployment insurance policies.
The sensible query for pockets builders integrating the launch is which of these protections their software program can confirm.
What reaches the Solana prover
Helius’s pockets integration information says proof era wants plaintext inputs masking the entire transaction information and nullifier keys. It identifies an attested AWS Nitro enclave because the SDKs’ default prover.
The protocol specification lists non-public inputs together with the asset, quantity, blinding values, and nullifier secret for notes being spent, together with paths proving these notes belong to the state tree. The proof additionally contains output property, quantities, and blinding values.
These inputs develop into readable to the proving code contained in the enclave, and the documented consumer protects them from the host operator by encrypting requests to a key held by the attested enclave.
The nullifier secret additionally derives the markers used to forestall repeat spending. Within the native pockets integration, the pockets retains the signing key, and the TypeScript SDK leaves signing of the completed Solana transaction with the applying’s signer.
Helius paperwork native decryption, which retains the viewing key on the system, and delegated decryption, which shares a viewing key with a certified supplier. Delegation offers that supplier learn entry to balances and historical past, with out granting spending authority.
AWS describes Nitro Enclaves as remoted environments whose reminiscence the dad or mum occasion’s processes or directors can’t entry. Enclaves haven’t any persistent storage, interactive entry, or exterior networking.
AWS’s signed doc comprises cryptographic fingerprints of its picture and software program. The documented Privateness Rings checks confirm the certificates chain, problem response and freshness, accepted measurements, and the binding of the request-encryption key.
The tagged SDK refuses a distant prover request with out one, earlier than making an HTTP name. A pockets can pin a reviewed launch coverage or use a community coverage authenticated by the SDK’s pinned signers. Signed insurance policies refresh throughout attestation and expire after use.
Examine the verification boundary
The consumer verifies attestation towards an accepted coverage earlier than encrypting distant proof requests.
Code assessment, AWS isolation and the operator’s preliminary KMS coverage binding underpin the documented confidentiality design.
Wallets examine an accepted enclave and key; code assessment and deployment coverage stay separate dependencies.
Documented default configuration solely, not impartial stay attestation or an audit. Different proving or authorization paths can differ. Native pockets signing, distant proving and balance-viewing entry have separate roles.
The place Solana’s deployment belief stays
A pockets can routinely examine that the enclave matches an accepted software program picture and encryption key, but deciding which picture to approve nonetheless requires confidence within the code and its reviewers.
The Nitro deployment information says the measured picture contains the prover, startup script, certificates bundle, allowed exterior hosts, indexer URL, and KMS key id. Its design makes use of AWS Key Administration Service to launch the shared encryption seed solely to matching attested enclaves.
The information says purchasers can’t learn the KMS key coverage and depend on the operator’s deployment for that assure. It identifies AWS KMS, AWS Assist, Nitro {hardware}, and the operator as belief roots throughout preliminary coverage binding.
Even accurately encrypted requests go away metadata seen to the dad or mum, equivalent to paths, queries, timing, and sizes. The trail reveals the proof’s circuit form.
The versioned TEE information data a mainnet construct primarily based on v0.6.0-alpha, with measured-build provenance, distinct from the ts-sdk-v0.8.0-alpha documentation tag.
The specification permits client-side proofs, and the repository provides localnet tooling and downloadable prover binaries.
Helius’s launch announcement says Certora, zkSecurity, and OtterSec audited packages and circuits. Its safety web page lists Certora in October and zkSecurity in August, whereas marking OtterSec as awaiting a report.
The launch offers pockets builders a belief determination on which code and deployment coverage they approve to deal with proof inputs.
