fix(vendor): correct Privacy Pools deployment status and GitHub link - #192
Merged
Conversation
Privacy Pools v1 has been live on Ethereum mainnet since March 2025, operated by 0xbow. The card still said "Not yet deployed at large scale". Replace that line with the verified status and keep the governance caveat, which is still open. The GitHub link pointed at ameensol/privacy-pools, the research repo. Point it at 0xbow-io/privacy-pools-core and keep the research repo as a secondary reference. Reported by 0xbow in #92.
rymnc
approved these changes
Sep 8, 2026
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.
The card said "Not yet deployed at large scale". Privacy Pools v1 has been live
on Ethereum mainnet since March 2025. The GitHub link also pointed at
ameensol/privacy-pools, the research repo, instead of0xbow-io/privacy-pools-core.Both reported by @0xmikemcc in #92, which we closed for inactivity. #92 also
covered pattern cross-references, a mention in
approach-private-payments.md,and glossary entries for Association Set / ASP. Those still look worth doing and
a follow-up PR is welcome. (
pattern-l1-zk-commitment-pool.mdwas removed in#111, so that one needs a new home.)