When things are fully private right is when you have the shared state should not be required directly in order to like perform the action you want to perform. often it's not known at the time of creation I mean that again just a restatement of what you were saying but that this is a huge problem with marketsright whenever you submit an order to a market you often won't know the price of the order lands at unless you can do many things. fundamentally yeah exactly but the the big problem is oh all these people who are making their transactions doing their execution on their own device and then submitting that to the chain they're all kind of trying trying to concurrently access or modify some kind of shared
In this week’s episode, Anna and Guillermo catch up with Henry de Valence from Penumbra. They discuss his thoughts on requirements for adoption of privacy systems and how these led to him to develop Penumbra. They explore how Penumbra aims to use privacy features not as ‘nice to haves' within the system, but rather as essential components that offer a new paradigm for how to think about DeFi in a Multichain Ecosystem.
Here are some additional links for this episode:
Find the Anoma Whitepaper here.
ZK Jobs Board – has a fresh batch of open roles from ZK-focused projects. Find your next opportunity working in ZK!
Today’s episode is sponsored by Aleo.
Aleo is a new Layer-1 blockchain that achieves the programmability of Ethereum, the privacy of Zcash, and the scalability of a rollup.
If you’re interested in building private applications then check out Aleo’s programming language called Leo. Visit leo-lang.org to start building.
You can also join Aleo’s incentivized testnet3 by downloading and running a snarkOS node. No sign-up is necessary to participate. For questions, join their Discord at aleo.org/discord.
If you like what we do: