Helius Launches Privacy Rings for Token Transfers on Solana

By Elena Vasquez

Helius has launched Privacy Rings on Solana mainnet, introducing token transfers that conceal asset type and amount while leaving wallet addresses visible. The permissionless protocol supports SOL, SPL assets and Token-2022 tokens, and transactions execute and settle on Solana mainnet.

What does the protocol conceal?

Privacy Rings encrypts the asset type and amount in a supported transfer, not the sending and receiving wallet addresses. That distinction leaves the participants visible on Solana even when the underlying payload is hidden. The feature therefore addresses transaction confidentiality rather than full anonymity.

The announcement neither describes the cryptographic construction nor identifies an independent reviewer for the permissionless deployment, leaving the basis of the privacy claim unstated. It also does not explain how the protocol addresses transaction linking, given that wallet addresses remain visible.

The practical distinction is simple: the protocol hides what moves and how much, not who transacts.

How do users move assets?

Users deposit assets into a private pool, send them to any Solana wallet and then return funds to a public balance. The entire sequence executes and settles on Solana mainnet.

• Supported assets include SOL, SPL assets and Token-2022 tokens.
• A transfer can reach any Solana wallet.
• The final withdrawal places funds back in a public balance.

The announcement presents the private pool as an intermediate step, not an alternative settlement network. The return to a public balance provides an explicit exit after the encrypted transfer. It does not specify how long assets remain in the pool or which parties can view the transfer details during the process. For users, the workflow requires a deposit, a transfer and a public withdrawal.

How do developers distribute it?

Developers can add Privacy Rings to existing applications through an API or software development kit. The announcement identifies Jupiter, Backpack and DFlow as integrating the protocol, creating three named distribution paths for the feature.

Embedding the feature in existing applications can reduce the work required to expose confidential transfers to users. That does not establish how many users will adopt the feature or what commercial terms, if any, accompany the integrations.

The launch materials give no integration timetable, interface description or confirmation that each application will support every listed token standard. Those details determine whether developers can enable Privacy Rings consistently across products. The immediate business question is whether those integrations turn a protocol release into actual user access.

What changes for institutions?

Helius is preparing Custom Rings, a permissioned version for institutions. The company said Custom Rings "is under audit" and is "expected to reach mainnet in the coming weeks." Planned features include selective disclosure, audit access and KYC-based whitelists.

That release would separate institutional use from the permissionless deployment through access controls, not through a separate blockchain. The whitelists narrow who can participate, while selective disclosure and audit access suggest designated information-sharing for approved participants.

The announcement does not name the auditor, define the audit scope or specify the jurisdiction governing identity checks. Those details determine how institutions evaluate operational and compliance risk, and none should be treated as settled. The institutional proposal therefore narrows the eligible participant base by design, although Helius has not published a fixed mainnet date. For institutions, Custom Rings remains a planned release rather than a verified deployment.

What remains unverified?

Several operational questions remain open for users and developers, including which assets each application supports, when the feature appears in each interface and how identity checks operate for Custom Rings. Helius has not disclosed an audit completion date, an auditor or a fixed deployment date for the permissioned version. The phrase "in the coming weeks" sets a near-term target rather than a guaranteed release schedule.

The next checkpoint is the coming-weeks mainnet target Helius has set for Custom Rings, which remains under audit. Until then, Privacy Rings is the only version Helius describes as already live, while institutional access and application-level availability remain contingent.