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!