一个*真正*扩展以太坊的Rollup 在这一集的《Deeply Intents》中，我与@_prestwich、@init4tech和@signetsh进行了交谈。这一集是关于rollup的硕士课程。 在这一集中，我们讨论了： - 什么是rollup？ - rollup的历史 - 从基本原理看@signetsh - 条件交易 - 应用程序控制执行 - （重新）基于的rollup 时间戳 0:00 - 以完全不同的方式构建rollup 3:14 - 什么是rollup？ 6:17 - rollup的历史 9:57 - Plasma 14:34 - 最小可行合并共识 18:45 - 从基本原理看Signet 21:27 - 无证明 23:01 - 条件交易 27:42 - 即时桥接 31:47 - 应用程序控制执行（ACE） 37:45 - 第三方本地发行 39:44 - 一个真正扩展以太坊的rollup 41:16 - 排序和区块构建 45:33 - 比以太坊更多的构建者 48:08 - 找到合适的合作伙伴 53:45 - 应用链+通用链的好处 56:03 - （重新）基于的rollup 1:00:04 - rollup未探索的设计空间 1:03:41 - 在以太坊上构建产品的错误 1:07:39 - 制作开发者工具 1:11:37 - 比特币重复历史

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!