In order to get certain properties or avoid certain bad cenarios, you actually do have to reason about how the consensus protocol interacts with the application. So in the liveness case, it really boils down to your choice of mechanism for liquidity provision iis implicitly reliant on some sort of bound on the maximum time the network goes down and the maximum price deviation. And ten, then you're not thinking of the threat model of, well, ok, what if the person whos actualyre trying to deanonymize is also a validator? That's just myn because it kind of exemplifies this fact that, like, you can't really design these things without thinking about consensus at some
This week, Anna catches up with Guillermo Angeris, Alex Evans and Tarun. The conversation charts their research on CFMMs, AMMs and related primitives and explores the goals and methodology of this work. They also revisit the topic of private AMMs and specifically their recent work on using differential privacy to achieve a more private system.
Here are some links for the episode:
Learn ->> ZK Hack - learn - now until December 7th, attend ZK workshops & solve ZK puzzles
Build ->> ZK Jobs Board - find new opportunities in the ZK space!
Meet ->> ZK Jobs Fair - December 2nd, meet top zk projects that are hiring.
Today’s episode is sponsored by Aztec.
Aztec aims to be the privacy layer for Ethereum. They believe that unlocking programmable privacy is the next frontier for blockchains. Aztec is the first zero knowledge rollup built from the ground up for anonymous payments and DeFi transactions.
Join the thousands of users already sending funds privately on zk.money.
If you like what we do:
Follow us on Twitter - @zeroknowledgefm
Join us on Telegram
Catch us on Youtube
Read up on the r/ZKPodcast subreddit
Give us feedback! -https://forms.gle/iKMSrVtcAn6BByH6A
Support our Gitcoin Grant
Support us on the ZKPatreon
Donate through coinbase.commerce