When we launched EthSystems we said each use case needs its own system, designed, specified, and hardened properly, and that someone has to do that work. Our specs site is now public: specs.ethsystems.org Starting small: a shielded pool for confidential payments, an attestation-gated profile of it, and the process behind both. Each spec states what the protocol does, what it assumes, and what it guarantees. This means engineers, auditors, and regulators can work from the same document.

Sep 23, 2026 · 11:34 AM UTC

10
14
131
23,648
Sort replies: Relevant Recent Liked
Replying to @eth_systems
this is close enough to our own approach that it's worth saying so directly rather than pretending otherwise — we split our docs the same way (what's protected, what's explicitly not, what assumptions the guarantee relies on) precisely because vague privacy claims are how projects lose trust later. genuinely curious how the attestation-gated profile differs from a viewKey-style disclosure model — different assumption, or just different UX on a similar guarantee?
5
81
Replying to @eth_systems
Great work!, thanks
191
Replying to @eth_systems
great work guys
9
461
Replying to @eth_systems
.@PG_CDG this fits for Cypherpunk Congress, btw
4
359
Replying to @eth_systems
Nghe cách bạn nói về việc mỗi trường hợp sử dụng cần hệ thống riêng làm mình thấy tò mò, ước gì xem được trang web specs đó nhỉ 😊
14
Replying to @eth_systems
The key insight most will miss: Tornado, Railgun, Privacy Pools each hardcoded WHERE screening happens. This spec hardcodes nothing - it names extension points and lets you compose compliance. Modular privacy that lawyers can actually audit. This is how shielded pools survive the next 5 years 🙏📖
3
4
14
319
Replying to @eth_systems
You guys ready for the explosion in use? It’s coming
88
Specs are now public.
68
Replying to @eth_systems
Publishing the specs up front makes the confidentiality model much easier to audit.
20