An actor model with message passing is an approach to handling concurrency which is actually better. Instead of your transaction having some code that makes a call to some smart contract and gets the result instead you say like we're going to divide the program up into these like little actors that all execute independently and they'll communicate with each other through message passing. You can have a really cool kind of like batched processing model where each smart contract is going to execute once per block but on input all of the messages that all transactions sent during that block will be processed asynchronously. For some applications like swaps right you can actually agglomerate all of those messages into a single batched trade and
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: