# Helius Encrypts Solana Transfers, but Its Default Prover Protects Secrets Inside an Amazon Enclave

The design hides amounts and, in anonymous mode, the sender and recipient as well, but users still have to trust the hardware and the operator that run the default prover.

- Published: 2026-11-13T05:45:42.603Z
- Canonical: https://polylog.news/crypto/2026-11-13/helius-encrypts-solana-transfers-but-its-default-prover-prot
- Publisher: Polylog (Crypto desk)
- Section: crypto
- Sources: [CryptoSlate](https://cryptoslate.com/helius-encrypts-solana-transfers-without-removing-operator-trust/), [Solana Compass](https://solanacompass.com/news/helius-launches-solana-privacy-rings-on-mainnet-encrypting-balances-and-transfer-amounts), [Helius documentation](https://www.helius.dev/docs/privacy/concepts)

Helius, the largest independent remote procedure call (RPC) provider on Solana, has launched Privacy Rings. The system encrypts balances and transfer amounts, and [Solana Compass reported](https://solanacompass.com/news/helius-launches-solana-privacy-rings-on-mainnet-encrypting-balances-and-transfer-amounts) that it runs on Solana mainnet. Transactions execute on Solana itself and are verified by an on-chain privacy program, with no separate sequencer or layer-2. Three integrations were live at launch, including Decrypt's money account.

[Helius's documentation](https://www.helius.dev/docs/privacy/concepts) describes the system as a programmable shielded pool built on an open-source protocol that Helius Labs maintains. Confidential transfers hide the asset and the amount. Anonymous transfers also hide the sender and recipient. The default ring is permissionless and gives auditors no visibility. Custom rings can add their own policy and compliance controls.

The design has a trust limitation. [CryptoSlate found](https://cryptoslate.com/helius-encrypts-solana-transfers-without-removing-operator-trust/) that the default prover protects users' secret inputs inside an Amazon Web Services (AWS) secure enclave, a sealed area of the processor. Wallets approve the code and the policies that run there. The zero-knowledge proofs stop anyone from forging a transfer. They do not stop the prover operator, or someone who breaches the enclave, from seeing the inputs. Helius's documentation says that providers such as Helius index the encrypted state, generate the proofs and submit the transactions. A user who relies on the default path is therefore relying on Helius and AWS for confidentiality.

## What this means

Delegated proving makes private transfers fast enough for phones, but it places confidentiality under the control of one infrastructure company and one cloud vendor. Exposed are users who think "zero-knowledge" means no one else sees their data, and any compliance-minded integrator whose privacy guarantee depends on AWS staying secure. Helius gains control of the private-payments layer on the chain where it already handles much of the traffic. The precedent is Secret Network, whose privacy relied on Intel enclaves. In 2023 researchers showed they had extracted its network-wide decryption key using known enclave flaws, and every past transaction became readable. The likelier outcome is that Privacy Rings wins early payment volume on Solana because it is convenient, while privacy-sensitive users push for client-side proving over the next several months. That depends on whether wallets can generate proofs locally at acceptable speed. A shipped client-side prover that wallets turn on by default would remove the main objection.

## What to watch

- Whether Helius or wallet partners ship proving on the user's own device as the default. That would remove the operator from the confidentiality path.
- New research on enclave side-channel attacks on AWS hardware. Any working attack would put past default-ring transfers at risk.
- Whether custom rings with auditor access draw more volume than the permissionless default ring. That would show whether demand on Solana is for compliance-ready confidentiality or for anonymity.