The IBC spec is actually remarkably difficult to build a generic protocol when you only have one implementation. There's some kind of standardized system of like how you encode messages into your chain state so that your counterparty chain can read them. It is actually possible for us to build our own custom chain and submit proofs of what its state was to the cosmos hub. And we're not planning to implement these features initially but in the longer term it's something that we're thinking about.
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: