A Rollup that *Actually* Scales Ethereum In this episode of Deeply Intents, I chat with @_prestwich of @init4tech @signetsh. This episode is a masterclass on rollups. In this episode we discuss: - What is a rollup? - History of rollups - @signetsh from first principles - Conditional Transactions - Application Controlled Execution - (Re)Based Rollups Timestamps 0:00 - Build a rollup in a completely different way 3:14 - What is a rollup? 6:17 - History of rollups 9:57 - Plasmas 14:34 - Minimum viable merged consensus 18:45 - Signet from first principles 21:27 - No proofs 23:01 - Conditional Transactions 27:42 - Instant bridging 31:47 - App Controlled Execution (ACE) 37:45 - Third party native issuance 39:44 - A rollup that actually scales Ethereum 41:16 - Sequencing and block building 45:33 - More Builders than Ethereum 48:08 - Finding the right partners 53:45 - Benefits of app chain + general purpose chain 56:03 - (Re)Based Rollups 1:00:04 - Unexplored design space for rollups 1:03:41 - Mistakes building products on Ethereum 1:07:39 - Making developer tools 1:11:37 - Bitcoin repeating history

As we're seeing now, L2 stacks face a fundamental problem: they have tokens. Once those tokens vest, the engineers and business development teams often lose the incentive to continue supporting the project. This is already happening with several L2 stacks and is likely to happen with the rest. Additionally, many of these stacks suffer from unmaintainable codebases. They're either excessively large, sometimes exceeding 500,000 lines of code, or poorly written, having been rushed into production to launch the token. In many cases, the token was treated as the product, not the codebase itself. @ethrex_client doesn't have this problem. The codebase was designed to be minimal and easily maintainable so that @class_lambda can keep developing it in the long run. The design of Ethrex took account the cost of maintaining it long term. We also designed it as an L1 and L2 client from day one. These two features will make it stand out long term. Another interesting thing of not having a token associated with your piece of infrastracture is that. You don't need to talk with me, @class_lambda, or anybody to launch your own L2 with @ethrex_client. You just do it with one command. With dozens of engineers we are now writing a small book on how Ethrex and Ethereum works so that anybody can change any part of the code without talking with us. Let's go Ethereum. Let's go Ethrex!