Skip to content

fix(vendor): correct Privacy Pools deployment status and GitHub link - #192

Merged
oskarth merged 1 commit into
masterfrom
fix/privacypools-staleness
Sep 8, 2026
Merged

fix(vendor): correct Privacy Pools deployment status and GitHub link#192
oskarth merged 1 commit into
masterfrom
fix/privacypools-staleness

Conversation

@oskarth

@oskarth oskarth commented Sep 8, 2026

Copy link
Copy Markdown
Collaborator

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 of
0xbow-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.md was removed in
#111, so that one needs a new home.)

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.
@oskarth
oskarth requested a review from rymnc September 8, 2026 08:02
@oskarth
oskarth merged commit 0b85263 into master Sep 8, 2026
4 checks passed
@oskarth
oskarth deleted the fix/privacypools-staleness branch September 8, 2026 08:13
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.

2 participants