Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
oskarth merged 1 commit into from
Sep 8, 2026
Merged

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

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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))
Expand Down
5 changes: 3 additions & 2 deletions vendors/privacypools.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)
Loading