OpenZeppelin adds confidential tokens to Stellar, with client tools still a demo

Reporting: sourced factual coverage reviewed by the editorial desk.

OpenZeppelin announced confidential-token contracts for Stellar on October 22, adding a way to hide balances and transfer amounts without hiding the addresses involved. The company says the contracts in its Stellar v0.8.0 release are audited and ready for mainnet deployment.

The distinction matters for ordinary payments. A business may want a payroll payment to settle on a public network without publishing every employee’s pay. This design aims to keep the figures private while allowing the network to verify that the transfer is valid. It is not anonymous money.

According to OpenZeppelin’s documentation, users deposit an existing SEP-41 token into a confidential contract. The contract records protected balances, and operations spending private state carry proofs checked onchain. The sender and recipient addresses remain visible.

That protection depends on more than the contract. Wallet software must generate proofs and retain the information needed to understand balances; an indexer preserves event history for recovery. OpenZeppelin says its client SDK, indexer and selective-disclosure layer are specified separately and are not included in the library.

The release announcement draws a further boundary: its audit covers the Soroban contracts and circuits. The SDK and client tooling remain a separate, unaudited demo under development. The standalone model for issuing a confidential token directly is also outside this release; the included approach wraps an existing token.

Compliance controls can preserve designated oversight, account freezing and authorized recovery. Privacy here therefore does not mean every participant is excluded from seeing amounts, or that an issuer loses its administrative powers.

For readers, this is a release of building blocks, not proof that a bank, employer or stablecoin issuer has deployed them. A production service still needs working wallets, recovery arrangements, secure client software and clearly explained access rights. The announcement does not establish customer adoption or a token-price outcome.

RailsRecord reviewed OpenZeppelin’s original release and technical documentation. We did not deploy the contracts, audit the software or interview customers. The original AI illustration is conceptual and shows no actual payment or workplace.

Sources & evidence

OpenZeppelin — confidential-token release ↗

OpenZeppelin — Confidential Token documentation ↗

Visual: original AI-generated conceptual illustration, created for this headline. It does not document an actual event.

Author disclosure

AI assisted primary-source research, drafting and review. No interviews, independent audit or deployment tests were conducted. The headline-specific illustration is original AI-generated conceptual art. RailsRecord is a Joaico publication; relevant publisher holdings and other material interests have not been established.

Corrections

Identify this article and the disputed claim in a correction request to corrections@railsrecord.com ↗. The publisher reviews supporting primary evidence.