Privacy Guardians 2.0

I just published Privacy Guardians, and I’m open-sourcing the design. I spent a lot of time writing the twitter thread to explain it in as few words as possible, so you’ll get, by far, the best description just by reading it (3 min) x.com leoglisic.eth (@Leo_Glisic) on X @Leo_Glisic Corpo Consortium recently announced OUSD: on-chain payments. Visible by everyone. Freezable by them. Thanks, but no thanks. Not Today. I present Privacy Guardians, the decentralized version. Designed for maximum achievable privacy. And I’m open-sourcing it 1 / ? The white paper is linked at the end of it, or you can skip ahead if that’s your style: glisic.xyz privacy-guardians-whitepaper-7-16-26.pdf 1059.04 KB I’ll now assume you’ve read the twitter thread, but not the white paper. The reason I’m posting here is because this is just a newborn baby. V1 is never the final version (or we’d still be on PoW). There are a lot of novel mechanisms in this design that interplay with one another. I know it can be made better. More cryptographically sound, and more elegant in terms of the mechanisms. And better incentive alignment. Better capital efficiency. And so on. There are a lot of areas to tackle. It’s going to take a village. There’s the private payment mechanism, the insurance mechanism, the honeypot and how it is claimed, the exchange rates, the liquidity pools, how metadata is handled, and the list just continues. This is less about breaking the scheme / mechanism in terms of finding vulnerabilities or critiques. It’s more about improving it altogether across many dimensions. It’s clear to me (and hopefully to you after reading the white paper) that this is the right direction to go. We should design and build the best possible version. As I said, it’ll take a village. Go team. 1 post - 1 participant Read full topic