The Privacy Salon at @EthereumDenver is the highlight of this week in privacy. Alongside @AleoHQ, @MidnightNtwrk and @Ledger, we gathered the who and who in the privacy space for a range of topics, from compliance to private stablecoins. Things got spicy with a spirited debate on cypherpunk privacy vs practical privacy. To keep the focus, it was a fully private event with phones locked away, encouraging everyone to engage directly with the speakers, panelist and debaters. Outside the salon, the privacy ship continued to sail. Let's dive in:

Name & Symbol: Midnight ($NIGHT)
Address: 0xfe930c2d63aed9b82fc4dbc801920dd2c1a3224f

It is absolutely possible to write DeFi protocols (and much more) while relying on ZKPs for privacy - this is exactly what Miden was designed to do. The main trick is to reimagine how the state works and instead of using a monolithic state adapt the Actor Model (something used in distributed systems for decades). Then we can have private actors that can interact with public actors which control the shared state. Or we could have semi-private actors (the state is known to some set of users, but not to the entire network) and these can also interact both with fully private actor or public actors. This is a very powerful model that covers a large number of DeFi use cases - from anonymous AMMs and CLBOs, to private compliant stablecoins. And one other nice thing: to write these DeFi protocol, we don't need engineers who understand ZKPs - you can write everything in Rust. I do like FHE - really cool technology and it does enable a few use cases which ZKPs cannot address (i.e., having truly private shared state) - but it also comes with huge performance overhead for the network. The beauty of ZKPs is that they actually reduce the network load - a transaction proven locally does not need to be executed by the network (verifying ZK proofs is very cheap) - we call this concept the Edge blockchain. While with FHE, every transaction becomes 100x (or 1000x) more expensive for the network. ASICs will help here for sure, but this also means that every validating node will need to run these ASICs or otherwise they won't be able to follow the network. And requiring every node to have an ASIC is kind of like requiring every Bitcoin node to be a miner.

Name & Symbol: Mind Network ($FHE)
Address: 0xd55c9fb62e176a8eb6968f32958fefdd0962727e

As much as Kaito gets flack for all the people trying to farm on Twitter, it’s just as fair to say the real issue lies with how campaigns are designed. Kaito is a tool. Like any tool, how it’s used can be sophisticated and nuanced, or lazy and broad. One team that clearly nailed a thoughtful approach was Boundless. You could tell from how intentional every detail was leading up to their TGE. Maybe instead of blaming users, we should ask protocols to take more accountability for the campaigns driving the “AI slop” everyone loves to complain about.

Name & Symbol: Boundless ($ZKC)
Address: 0x15247e6e23d3923a853ccf15940a20ccdf16e94a