From 46f010a414b7fbd2257c502ce8856c329a9a7d0f Mon Sep 17 00:00:00 2001 From: oskarth Date: Tue, 8 Sep 2026 14:52:46 +0800 Subject: [PATCH] fix(vendor): correct Privacy Pools deployment status and GitHub link 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. --- CHANGELOG.md | 1 + vendors/privacypools.md | 5 +++-- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 0fe6c7f..78d4c7a 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,6 +4,7 @@ All notable changes to the EthSystems Map are documented here. ## [Unreleased] +- fix(vendor): [Privacy Pools](vendors/privacypools.md) -- v1 has been live on Ethereum mainnet since March 2025; replace the stale "not yet deployed at large scale" line and point the GitHub link at [0xbow-io/privacy-pools-core](https://github.com/0xbow-io/privacy-pools-core) (reported by 0xbow in [#92](https://github.com/ethsystems/map/pull/92)) - feat(approach): link private-stocks, private-commodities, private-fx, and private-repo to [Private Trade Settlement](approaches/approach-private-trade-settlement.md), and private-treasuries to [Private Payments](approaches/approach-private-payments.md), as explicit variants ([#190](https://github.com/ethsystems/map/pull/190), part of [#138](https://github.com/ethsystems/map/issues/138)) - feat(pattern): add [CMTAT](https://cmta.ch/standards/cmta-token-cmtat) as an alternative to ERC-3643 in [ERC-3643 Tokenized RWAs](patterns/pattern-erc3643-rwa.md), a blockchain-agnostic compliant-tokenization standard with an Aztec/Noir privacy-preserving implementation, cross-referenced in GLOSSARY.md and [Private RWA Tokenization](use-cases/private-rwa-tokenization.md) ([#190](https://github.com/ethsystems/map/pull/190), closes [#174](https://github.com/ethsystems/map/issues/174)) - feat(vendor): [Gateway Open Privacy Suite](vendors/gateway-open-privacy-suite.md) — governed JSON-RPC access, selective disclosure, and compliance controls for private EVM networks and Gateway L2/validium deployments ([#189](https://github.com/ethsystems/map/pull/189)) diff --git a/vendors/privacypools.md b/vendors/privacypools.md index 3c5277b..71fd7f5 100644 --- a/vendors/privacypools.md +++ b/vendors/privacypools.md @@ -65,10 +65,11 @@ Instead of merely unlinking deposits and withdrawals, users can provide **member - Privacy depends on **set size and accuracy**: small or poorly curated sets reduce anonymity. - Requires trust in Association Set Providers (risk of manipulation or censorship). - No native cross-chain support. -- Not yet deployed at large scale; governance of set definitions is unresolved. +- Governance of set definitions is unresolved; 0xbow operates the ASP for the Ethereum mainnet deployment, live since March 2025. ## Links -- [Privacy Pools GitHub](https://github.com/ameensol/privacy-pools) +- [Privacy Pools Core (0xbow) GitHub](https://github.com/0xbow-io/privacy-pools-core) +- [Original Privacy Pools research repo (ameensol)](https://github.com/ameensol/privacy-pools) - [SSRN Paper: Blockchain Privacy and Regulatory Compliance](https://ssrn.com/abstract=4563364) - [Vitalik blog on Privacy Pools](https://vitalik.eth.limo/general/2023/09/06/privacy.html)