Skip to content

Fix broken Confidential Token repo link on Privacy page - #2915

Draft
kaankacar wants to merge 1 commit into
mainfrom
docs/confidential-token-stable-release
Draft

kaankacar wants to merge 1 commit into
mainfrom
docs/confidential-token-stable-release

Conversation

@kaankacar

Copy link
Copy Markdown
Contributor

Closes #2914

What

  • docs/build/apps/privacy.mdx: replaced the dead link to OpenZeppelin's deleted feat/confidential-verifier-ultrahonk branch with the confidential token package at packages/confidential on main. Added links to the deployment guide and examples and to the design overview.
    • The demo bullet now says "(developer preview)". The demo still targets the deleted branch.
    • "Implementation on Stellar is in progress." now points to the stellar-contracts library.
    • The caution is unchanged. The contracts are still unaudited.
  • docs/tools/openzeppelin-contracts.mdx: no change yet.

Verification

Notes

  • Downstream: stellar/ecosystem-resources picks this up on the triage bot's next daily sync after merge.
  • Draft until OpenZeppelin tags the stable release. Then links get pinned from main to the tag and the caution/"Coming Soon" updates are applied in this same PR.
  • Draft PR 🔒 Refresh Privacy on Stellar guide #2673 edits the same lines. One of the two PRs will need a rebase.

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
@github-actions github-actions Bot added the preview Preview builds for PRs by SDF employees. label Oct 13, 2026
@github-actions

Copy link
Copy Markdown
Contributor

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

Labels

preview Preview builds for PRs by SDF employees.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Privacy page: point Confidential Token resources to OpenZeppelin's stable release

1 participant