SPONSORED PARTNERMEXCExplore global spot and futures marketsEXPLORE MEXC →
CHARTING PARTNERTradingViewAdvanced charts, indicators and market analysisOPEN CHARTS →
TRADING PARTNERGMX via NetNapz TradeTrade decentralised perpetual marketsSTART TRADING →SOLANA · DEFI · PRIVACY
Helius Launches Solana Privacy Rings; Wallet Addresses Remain Public
The 10 November mainnet launch encrypts transfer assets and amounts. Public addresses, entry and exit flows, viewing access and unfinished security work still matter.

Helius announced the mainnet launch of Solana Privacy Rings on 10 November, adding a permissionless system for confidential transfers on Solana. Its default Ring encrypts the asset and amount while keeping sender and recipient wallet addresses public. The Solana Foundation separately published the launch, but the two announcements are ecosystem statements rather than independent technical validation.
The distinction is consequential for payments and DeFi: a transfer can conceal its financial detail without concealing who interacted. Helius describes deposits into encrypted balances, transfers between them and withdrawals back to public balances. Its documentation says execution occurs in a single Solana transaction, rather than through a separate sidechain or sequencer.
Confidential transfers have visible boundaries
The detailed privacy documentation says a deposit from a public balance exposes its source, asset and amount. A withdrawal exposes the destination, asset and amount. Within a default-Ring transfer, observers can see the addresses and encrypted records, but not the asset or amount. That makes the privacy boundary specific to the flow being used.
Key handling also changes what remains private. Local decryption keeps viewing access on the device; delegated decryption allows an authorised RPC provider to read balances and history. Sharing that viewing key does not grant spending authority. The documentation separately distinguishes a native wallet holding its own shielded keypair from an embedded setup where a wallet provider holds and operates it.
Institutional Custom Rings remain a separate release
Helius says the permissionless Ring is live, while Custom Rings for institutions are still being audited, with a targeted release in the fourth quarter. Those proposed environments can configure confidentiality, auditor access and compliance controls. Their planned availability should not be presented as a completed institutional rollout.
The launch materials describe integrations and potential applications involving swaps, lending, staking and conditional payments. Those examples do not establish that every named integration is finished or that every tokenised asset has acquired new legal rights. Encryption changes information visibility; it does not itself change an issuer’s redemption terms, asset ownership or an application’s financial risks.
Audit publication is uneven
Helius’s security documentation links a Certora report dated October 2026 and a zkSecurity report dated August 2026. The same table lists OtterSec as awaiting a report, although the launch announcement says three firms audited the programs and circuits. NetNapz verified the linked report locations, but did not audit their findings, reproduce the cryptography or match audited commits to deployed binaries.
The security page records a trusted setup completed on 2 November, with 15 accepted contributions per circuit. Helius also says formal verification is underway and expected to finish by year-end. Neither the existence of audits nor a completed setup is a guarantee against implementation failures or compromised keys.
NetNapz assessment
The useful advance is an opt-in confidentiality layer on the existing settlement network. Its practical value will depend on wallet design, application adoption and how well users understand entry, exit and viewing-key exposure. The default Ring should be assessed as confidential transfers with public counterparties, not as a promise of anonymous activity.
Follow-up evidence should include completed security-report publication, clearly identified deployed versions and specific integration launches. No transaction-volume, fee-saving or price-impact claim is made here. NetNapz checked the announcements and documentation; it did not connect a wallet, make a transfer or verify end-to-end production operation.
