Repository navigation
Point Confidential Token resources to OpenZeppelin's stable release - #2915
Merged
Merged
Conversation
Contributor
OpenZeppelin deleted the feat/confidential-verifier-ultrahonk branch. The code now lives in packages/confidential on main. - Link the package, the deployment guide and examples, and the design overview. - Mark the demo as a developer preview. It still targets the old branch. - Point to the stellar-contracts library for the Stellar implementation. Refs #2914
OpenZeppelin released the confidential token in stellar-contracts v0.8.0. - Pin the Privacy page links to v0.8.0. Add crates.io, release notes, and the OpenZeppelin docs page. - Replace the developer-preview caution. The v0.8.0 audit covers the token, but proofs are not yet zero-knowledge. - Add a Confidential Token entry to the OpenZeppelin page and add confidential/ to the repository tree. - Remove "Coming Soon". Governor shipped in v0.7.0, so it moves to Utilities. Refs #2914
kaankacar
marked this pull request as ready for review
October 21, 2026 12:19
kaankacar
force-pushed
the
docs/confidential-token-stable-release
branch
from
October 21, 2026 12:20
b46e37a to
08e9b92
Compare
Contributor
Contributor
There was a problem hiding this comment.
🔵 Needs a closer look
The audit scope supporting removal of the unaudited warning still needs independent confirmation.
1 open issue
What changed in this PR
Updates Stellar’s Confidential Token documentation to reference OpenZeppelin’s stable release, addressing the broken resources reported in #2914.
Changes:
- Pins library resources to v0.8.0 and adds deployment and design references.
- Revises privacy limitations and identifies the demo as a developer preview.
- Lists Confidential Token and Governor as available modules.
Recommendation: NEEDS-HUMAN-REVIEW — confirm audit coverage before removing the unaudited warning.
| File | Description |
|---|---|
| docs/tools/openzeppelin-contracts.mdx | Adds Confidential Token, moves Governor to Utilities, and updates repository structure. |
| docs/build/apps/privacy.mdx | Replaces obsolete resources and updates audit and privacy guidance. |
Review effort: Balanced
The v0.8.0 interface exposes confidential_balance and confidential_transfer, not the SEP-41 balance and transfer methods.
Contributor
Author
|
On the audit scope in Copilot's summary: the v0.8.0 audit report covers the confidential token.
The caution keeps the zero-knowledge limit, because the README and audit finding CR-03 both state it. |
Contributor
ElliotFriend
approved these changes
Oct 21, 2026
Contributor
|
PR Preview: torn down |
This was referenced Oct 22, 2026
ElliotFriend
added a commit
that referenced
this pull request
Oct 22, 2026
* Point Confidential Token resources to OpenZeppelin's stable release (#2915) * Fix broken Confidential Token repo link on Privacy page OpenZeppelin deleted the feat/confidential-verifier-ultrahonk branch. The code now lives in packages/confidential on main. - Link the package, the deployment guide and examples, and the design overview. - Mark the demo as a developer preview. It still targets the old branch. - Point to the stellar-contracts library for the Stellar implementation. Refs #2914 * Point Confidential Token resources to OpenZeppelin's stable release OpenZeppelin released the confidential token in stellar-contracts v0.8.0. - Pin the Privacy page links to v0.8.0. Add crates.io, release notes, and the OpenZeppelin docs page. - Replace the developer-preview caution. The v0.8.0 audit covers the token, but proofs are not yet zero-knowledge. - Add a Confidential Token entry to the OpenZeppelin page and add confidential/ to the repository tree. - Remove "Coming Soon". Governor shipped in v0.7.0, so it moves to Utilities. Refs #2914 * Pin the stellar-confidential crates.io link to 0.8.0 * Describe the Confidential Token as a wrapper around a SEP-41 token The v0.8.0 interface exposes confidential_balance and confidential_transfer, not the SEP-41 balance and transfer methods. (cherry picked from commit fc4b3c9) * pr-preview: allow maintainer-approved previews for bot PRs (#2923) Members can apply the preview-approved label to build a preview for a PR opened by the stellar-triage-bot App. Needs stellar/actions#119. Refs stellar/ops#4953. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit a55db9e) * Stellar-rpc: Document the queryEvents beta RPC method (#2922) queryEvents is only served by the archive RPC node (stellar-rpc tag archive-node-beta). Keep it out of the main OpenRPC spec. Also drop the deprecated inSuccessfulContractCall field from the shared Event schema. (cherry picked from commit 8255fe9) * ci: add manual build of legacy-docs image for legacydocs.stellar.org (#2935) * ci: add manual build of legacy-docs image for legacydocs.stellar.org Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * ci: don't persist checkout credentials into the legacy docs build context Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit 17f2d69) * chore: reword the legacy docs banner Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs: point the legacy README at main's last Docusaurus commit Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Kaan Kacar <kaankacar02@gmail.com> Co-authored-by: Jonathan Eid <sevenmelee@gmail.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: urvisavla <urvi.savla@stellar.org>
ElliotFriend
added a commit
that referenced
this pull request
Oct 22, 2026
) Replaces the Docusaurus site with Mintlify's converted tree (base bcec501), with tooling trimmed to prettier, husky, redocly, the OpenRPC build, and the mint CLI. Commits that landed on main after bcec501 were ported by hand. Ported: Refs #2448 Refs #2671 Refs #2672 Refs #2727 Refs #2827 Refs #2828 Refs #2837 Refs #2856 Refs #2857 Refs #2869 Refs #2871 Refs #2878 Refs #2880 Refs #2881 Refs #2885 Refs #2886 Refs #2890 Refs #2892 Refs #2893 Refs #2895 Refs #2900 Refs #2901 Refs #2902 Refs #2903 Refs #2905 Refs #2912 Refs #2913 Refs #2915 Refs #2918 Refs #2922 Merged into the branch: Refs #2936 Refs #2937 Refs #2938 Refs #2940 Co-authored-by: alexistabak-cpu <alexis.tabak@stellar.org> Co-authored-by: Emir Ayral <73669654+emirayral@users.noreply.github.com> Co-authored-by: John Wooten <60260750+JFWooten4@users.noreply.github.com> Co-authored-by: Kaan Kacar <kaankacar02@gmail.com> Co-authored-by: Leigh <351529+leighmcculloch@users.noreply.github.com> Co-authored-by: maz <42838313+mmazco@users.noreply.github.com> Co-authored-by: Michael Lip <51033404+theluckystrike@users.noreply.github.com> Co-authored-by: Scopuly <39069225+Scopuly@users.noreply.github.com> Co-authored-by: stellar-triage-bot[bot] <333411864+stellar-triage-bot[bot]@users.noreply.github.com> Co-authored-by: Steph <91382964+oceans404@users.noreply.github.com> Co-authored-by: urvisavla <urvi.savla@stellar.org> Co-authored-by: water-k-max <codexsourcelogos@gmail.com> Co-authored-by: Wlademyr Mendes <wlademyr.mendes@gmail.com> Co-Authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Closes #2914
What
docs/build/apps/privacy.mdx:feat/confidential-verifier-ultrahonkbranch. The resources now point topackages/confidentialatv0.8.0. Added crates.io, release notes, the deployment guide and examples, the design overview, and the OpenZeppelin docs page.docs/tools/openzeppelin-contracts.mdx:confidential/to the repository-structure block.Verification
governance/src/governor.packages/governance/src/governorexists atv0.7.2andv0.8.0.pnpm check:mdxpasses.pnpm buildpasses locally. The new relative link renders as/docs/build/apps/privacy#confidential-tokens, and the anchor exists.Notes
stellar/ecosystem-resourcespicks this up on the triage bot's next daily sync after merge.