Skip to content

Stellar: Confidential Token - #244

Open
brozorec wants to merge 3 commits into
mainfrom
docs/stellar-confidential-token
Open

brozorec wants to merge 3 commits into
mainfrom
docs/stellar-confidential-token

Conversation

@brozorec

@brozorec brozorec commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

Adds docs for the Stellar confidential token (stellar-confidential, split into its own crate in OpenZeppelin/stellar-contracts#922): overview and installation, operations, spenders, auditing, compliance, clawback, proof system, wallet integration, indexing, and selective disclosure. Also adds the pages to the Stellar navigation and lists the confidential and ZK Email error-code ranges in the index.

Add docs for the confidential token (stellar-confidential crate): overview
and installation, operations, spenders, auditing, compliance, clawback,
proof system, wallet integration, indexing, and selective disclosure.
Register the pages in the Stellar navigation and list the confidential
and ZK Email error-code ranges.
@brozorec
brozorec requested review from a team and stevep0z as code owners October 6, 2026 12:42
@netlify

netlify Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for openzeppelin-docs-v2 ready!

Name Link
🔨 Latest commit 5d55608
🔍 Latest deploy log https://app.netlify.com/projects/openzeppelin-docs-v2/deploys/6ad0829dddd36217d3f19f00
😎 Deploy Preview https://deploy-preview-244--openzeppelin-docs-v2.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Add the privacy model page and best-practices pages for account holders, administrators and auditors, wire them into the navigation, and revise the existing confidential token pages.

Prose that only restated what a code snippet does (reverts, effects, field meanings, bb flags) now lives as comments in the snippet. Also fix the bb proving lead-in, which miscounted non-default settings, and explain the Installation link on the auditing page.
Rewrite the Zero-Knowledge Setting section to match the package README after #945: the circuits close the fixed-base lookup channel only, whether other parts of a non-zk proof reveal private values has not been established, and the one known case is the BN254 relation on the prover's long-term key. Note that zk verification is in progress upstream. Say a viewing key opens the transfers an account originated, per keys-and-commitments.md.

@stevep0z stevep0z left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Great job and thanks for making this large addition to the docs regarding the Confidential Token work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants