The Succinct Prover Network is live on mainnet. Today, we PROVE them wrong.

Mainnet preconfirmation is a major engineering milestone for @taikoxyz. It enables our based rollup to offer much better user UX. We believe taiko is on the right track to scale Ethereum - good UX, permissionless, and properly governed.

After a lengthy period of testing on the Taiko Hekla testnet, we are excited to announce that Based Preconfirmations are coming soon to the Taiko Alethia Mainnet! In preparation for this upgrade, we strongly recommend that you upgrade your node software to the listed versions by August 11th UTC. If you fail to upgrade, you will not be able follow the chain in real time as blocks are preconfed, but you will still be able to sync once they are proposed to the L1. This upgrade requires some configuration changes, which will be outlined in this guide on the docs site: - With this upgrade, it will unfortunately mean that community proposers will no longer be able to arbitrarily propose blocks. Since we are starting in starting in the Whitelisted Preconfirmations stage, only our partnered whitelisted preconfirmers will be able to propose. However, if you wish to continue operating a L2 node and stay connected to the chain, please update to the following software versions. You may continue to run a prover, but will only be able to prove unassigned blocks: please have PROVE_UNASSIGNED_BLOCKS=true set in your .env if you plan to do so. If you previously ran a prover, your previous prover config will still function. Mandatory update for Taiko Alethia Node operators: - taiko-geth v1.17.0 - taiko-alethia-client v1.9.0 - simple-taiko-node v1.18.0 Read more about the Based Preconfirmations stages here: -

What does a user typically see on a Based Preconf UX? 1. User sends a transaction 2. Preconfer replies with a promise that the transaction is included. 2.a. If promise is broken, preconfer is slashed. 3. User interface is updated instantly 4. Transaction confirmed on-chain.

Personal update during EthCC: After +2.5 amazing years, yesterday was my last day at @OpenZeppelin . It’s been quite a journey— where I’ve had the privilege to work with some of the smartest people I’ve met and to lead some of our most important projects. It was precisely during that time, that I fell in love with based rollups and the idea of scaling Ethereum closer to its true values. I’m happy to share that I’m joining @taikoxyz as their director of engineering to lead the engineering team and bring Taiko—and based rollups in general—to the next level. Our main focus is shipping preconfirmations, but I’m incredibly bullish about what this team can deliver. I’ve had the chance to collaborate with them and meet in person over the past few months, and let me tell you—they’re top-notch.

Feel sorry for those who sold at $77k. Remember to look at a yearly chart instead of a 1 minute chart once in a while.

Ethereum contract devs: if we could 10x the gas limit but, to do so, we had to 10x the gas cost of CREATE, CREATE2 and SSTORE, would that still be a net improvement? Why or why not? IOW, if state growth is our main bottleneck to scale L1 gas, should we just fix it with pricing?

structures and checks involved when sequencing a block, @taikoxyz vs @base when blobs are ~free, @taikoxyz’s onchain costs per L2 tx are ~900x higher than @base ($0.00015 vs $0.00000016)