Mitchell Tracy

@Crypto_Goblinz @LayerZero_Labs Canary is one of the 3 👍

@mitchellftracy @LayerZero_Labs would be great if you add canary DVN in the config.x.com/Crypto_Goblinz…

I set up the LZ connection for $AZTEC between ethereum and hyperliquid. Based on guidance from @LayerZero_Labs, it uses a 3/3 DVN, none of which are LZ Labs. The team was clear from day 1 about the risks of relying on their validator.

@aztecnetwork @CiaraNightingal @NoirLang So glad you took the time to make this. What do you think is the roughest edge of the development process today?

How to Build Private Smart Contracts on Aztec is live on YouTube! 🧑‍💻 Course creator and host @CiaraNightingal provides a complete course for Solidity developers, covering @NoirLang + Aztec.nr, writing, testing, and deploying on Aztec. 📺: youtube.com/watch?v=cQIPG_…

Thank you @CiaraNightingal for showing how easy it is to write private, programmable contracts on Aztec!

11/ Issues or feature requests? Reply or file an issue github.com/AztecProtocol/…

10/ Next stable release should be out in ~4 weeks. Nightlies are published with the latest and greatest. Full release and migration notes: github.com/AztecProtocol/…

1/ v4.2.0 of Aztec Labs' smart contract framework for building on Aztec is out. Big changes: - kernelless simulations by default - `.send()` estimates gas for you - offchain messages + custom handlers - iframe wallets SDK + `cli-wallet` More below 🧵

Huge proposed improvement to block building on Aztec from coming @smpalladino . Pipelining on a distributed network building/publishing means TPS up, latency down, and more slashing conditions. Comments are welcome. github.com/AztecProtocol/…

@nero_eth Really neat, thanks for putting this together. Any thoughts on having a separate section on blob transactions?

txdelay.xyz is live. See how long Ethereum transactions wait on average to land on-chain. Let me provide some additional context: how the website works, what Glamsterdam (the next hardfork), in particular ePBS (EIP-7732), changes, and what this means for different stakeholders. With 12s slots, the average inclusion delay is ~6s. Shortening slot time reduces it. This number will increase by ~2s with ePBS, which is an unfortunate downside, degrading UX. Under ePBS, builders should wait until the beacon block committing to their payload has enough attestations before releasing it. Thus, ePBS has a similar effect to increasing slot time to 16s, and Ethereum would need ~8s slots just to get back to today’s inclusion delay. A similar effect applies to zkEVM provers: if provers are separate from builders, they effectively lose ~2s of proving time, delaying real-time proving and slowing down the rollout of zkEVMs. With shorter slots (e.g. 8s), this means provers would need to be ~25% faster. The data is sourced from @ethPandaOps’ Xatu nodes, comparing when transactions are first seen in the mempool vs when they are included in a block. It filters for transactions that can afford the base fee and pay at least $0.01 in priority fees. If you're a dApp builder, infra provider, zkEVM prover, exchange, power user, etc., I'd be curious how much every second of inclusion delay matters. Drop your thoughts in the comments or reach out via dm.

corona muralis

So excited for the world will build. docs.aztec.network