Un Rollup che *Realmente* Scala Ethereum In questo episodio di Deeply Intents, parlo con @_prestwich di @init4tech @signetsh. Questo episodio è una masterclass sui rollup. In questo episodio discutiamo: - Cos'è un rollup? - Storia dei rollup - @signetsh dai primi principi - Transazioni Condizionali - Esecuzione Controllata dall'Applicazione - Rollup (Re)Basati Timestamp 0:00 - Costruire un rollup in un modo completamente diverso 3:14 - Cos'è un rollup? 6:17 - Storia dei rollup 9:57 - Plasmas 14:34 - Consenso minimo vitale fuso 18:45 - Signet dai primi principi 21:27 - Nessuna prova 23:01 - Transazioni Condizionali 27:42 - Bridging istantaneo 31:47 - Esecuzione Controllata dall'Applicazione (ACE) 37:45 - Emissione nativa di terze parti 39:44 - Un rollup che scala realmente Ethereum 41:16 - Sequenziamento e costruzione di blocchi 45:33 - Più Costruttori che Ethereum 48:08 - Trovare i partner giusti 53:45 - Vantaggi della catena dell'app + catena a scopo generale 56:03 - Rollup (Re)Basati 1:00:04 - Spazio di design inesplorato per i rollup 1:03:41 - Errori nella costruzione di prodotti su Ethereum 1:07:39 - Creare strumenti per sviluppatori 1:11:37 - Bitcoin che ripete la storia

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!