|
1 | 1 | # Introduction |
2 | 2 |
|
3 | | -Welcome to Evolve. Launch Fast. Build Your Own Network. |
| 3 | +Evolve is the fastest way to launch your own modular network — without validator overhead or token lock-in. |
4 | 4 |
|
5 | | -Evolve enables developers a direct path to shipping custom networks — faster than standing up a full L1, and more flexible than constrained rollup frameworks. |
| 5 | +Built on Celestia, Evolve offers L1-level control with L2-level performance. |
6 | 6 |
|
7 | 7 | This isn't a toolkit. It's a launch stack. |
8 | 8 |
|
9 | 9 | No fees. No middlemen. No revenue share. |
10 | 10 |
|
11 | | -## About Evolve |
| 11 | +## What is Evolve? |
12 | 12 |
|
13 | | -Our mission is to provide developers with the fastest path to launching their own networks. Built on Celestia, Evolve gives you full control over execution without the overhead of validator operations. |
| 13 | +Evolve is a launch stack for L1s. It gives you full control over execution — without CometBFT, validator ops, or lock-in. |
14 | 14 |
|
15 | | -## What is Evolve? |
| 15 | +It's [open-source](https://github.com/evstack/ev-node), production-ready, and fully composable. |
16 | 16 |
|
17 | | -Evolve is how you launch your network. Modular. Production-ready. Yours. |
| 17 | +At its core is \`ev-node\`, a modular node that exposes an [Execution interface](https://github.com/evstack/ev-node/blob/main/core/execution/execution.go), — letting you bring any VM or execution logic, including Cosmos SDK or custom-built runtimes. |
18 | 18 |
|
19 | | -Some still call them rollups. You'll just call it your network. |
| 19 | +Evolving from Cosmos SDK? |
20 | 20 |
|
21 | | -Evolve reframes the conversation: these aren't second-class layers. These are networks — with full execution freedom, developer control, and modular power. |
| 21 | +Migrate without rewriting your stack. Bring your logic and state to Evolve and shed validator overhead — all while gaining performance and execution freedom. |
22 | 22 |
|
23 | | -Evolve is an [open-source framework](https://github.com/evstack/ev-node). It features ev-node, a modular node that can run networks and exposes an [ABCI-compatible client interface](https://github.com/cometbft/cometbft/tree/main/abci), which can be used as a substitute for CometBFT in any ABCI-compatible blockchain application. |
| 23 | +Evolve is how you launch your network. Modular. Production-ready. Yours. |
24 | 24 |
|
25 | 25 | With Evolve, you get: |
26 | 26 |
|
27 | | -- Full control over execution |
28 | | -- No validator ops overhead |
29 | | -- Speed to traction |
| 27 | +- Full control over execution \- use any VM |
| 28 | +- Low-cost launch — no emissions, no validator inflation |
| 29 | +- Speed to traction — from local devnet to testnet in minutes |
| 30 | +- Keep sequencer revenue — monetize directly |
| 31 | +- Optional L1 validator network for fast finality and staking |
30 | 32 |
|
31 | 33 | Powered by Celestia — toward 1GB blocks, multi-VM freedom, and execution without compromising flexibility or cost. |
32 | 34 |
|
33 | 35 | ## What problems is Evolve solving? |
34 | 36 |
|
35 | | -### 1. Scalability and customizability |
| 37 | +### 1\. Scalability and customizability |
36 | 38 |
|
37 | 39 | Deploying your decentralized application as a smart contract on a shared blockchain has many limitations. Your smart contract has to share computational resources with every other application, so scalability is limited. |
38 | 40 |
|
39 | | -Plus, you're restricted to the execution environment that the shared blockchain uses, so developer flexibility is limited. |
| 41 | +Plus, you're restricted to the execution environment that the shared blockchain uses, so developer flexibility is limited as well. |
40 | 42 |
|
41 | | -### 2. Security and time to market |
| 43 | +### 2\. Security and time to market |
42 | 44 |
|
43 | 45 | Deploying a new chain might sound like the perfect solution for the problems listed above. While it's somewhat true, deploying a new layer 1 chain presents a complex set of challenges and trade-offs for developers looking to build blockchain products. |
44 | 46 |
|
45 | | -Deploying a new layer 1 requires significant resources, including time, capital, and expertise, which can be a barrier to entry for some developers. |
| 47 | +Deploying a legacy layer 1 has huge barriers to entry: time, capital, token emissions and expertise. |
46 | 48 |
|
47 | | -In order to secure the network, developers must bootstrap a sufficiently secure set of validators, incurring the overhead of managing a full consensus network. This requires paying validators with inflationary tokens, putting the business sustainability of the network at risk. A strong community and network effect are also critical for success, but can be challenging to achieve as the network must gain widespread adoption to be secure and valuable. |
| 49 | +In order to secure the network, developers must bootstrap a sufficiently secure set of validators, incurring the overhead of managing a full consensus network. This requires paying validators with inflationary tokens, putting the network's business sustainability at risk. Network effects are also critical for success, but can be challenging to achieve as the network must gain widespread adoption to be secure and valuable. |
48 | 50 |
|
49 | 51 | In a potential future with millions of chains, it's unlikely all of those chains will be able to sustainably attract a sufficiently secure and decentralized validator set. |
50 | 52 |
|
51 | 53 | ## Why Evolve? |
52 | 54 |
|
53 | | -Evolve solves the challenges encountered during the deployment of a smart contract or a new layer 1, by minimizing these tradeoffs through the implementation of sovereign chains. |
| 55 | +Evolve solves the challenges encountered during the deployment of a smart contract or a new layer 1, by minimizing these tradeoffs through the implementation of evolve chains. |
54 | 56 |
|
55 | 57 | With Evolve, developers can benefit from: |
56 | 58 |
|
57 | | -- **Shared security**: |
58 | | -Chains inherit security from a data availability layer, by posting blocks to it. Chains reduce the trust assumptions placed on chain sequencers by allowing full nodes to download and verify the transactions in the blocks posted by the sequencer. For optimistic or zk chains, in case of fraudulent blocks, full nodes can generate fraud or zk proofs, which they can share with the rest of the network, including light nodes. Our roadmap includes the ability for light clients to receive and verify proofs, so that everyday users can enjoy high security guarantees. |
| 59 | +- **Shared security**: Chains inherit security from a data availability layer, by posting blocks to it. Chains reduce the trust assumptions placed on chain sequencers by allowing full nodes to download and verify the transactions in the blocks posted by the sequencer. For optimistic or zk-chains, in case of fraudulent blocks, full nodes can generate fraud or zk-proofs, which they can share with the rest of the network, including light nodes. Our roadmap includes the ability for light clients to receive and verify proofs, so that everyday users can enjoy high security guarantees. |
59 | 60 |
|
60 | | -- **Scalability:** |
61 | | -Evolve chains are deployed on specialized data availability layers like Celestia, which directly leverages the scalability of the DA layer. Additionally, chain transactions are executed off-chain rather than the data availability layer. This means chains have their own dedicated computational resources, rather than sharing computational resources with other applications. |
| 61 | +- **Scalability:** Evolve chains are deployed on specialized data availability layers like Celestia, which directly leverages the scalability of the DA layer. Additionally, chain transactions are executed off-chain rather than on the data availability layer. This means chains have their own dedicated computational resources, rather than sharing computational resources with other applications. |
62 | 62 |
|
63 | | -- **Customizability:** |
64 | | -Evolve is built as an open source modular framework, to make it easier for developers to reuse the four main components and customize their chains. These components are data availability layers, execution environments, proof systems, and sequencer schemes. |
| 63 | +- **Customizability:** Evolve is built as an open source modular framework, to make it easier for developers to reuse the four main components and customize their chains. These components are data availability layers, execution environments, proof systems, and sequencer schemes. |
65 | 64 |
|
66 | | -- **Faster time to market:** |
67 | | -Evolve eliminates the need to bootstrap a validator set, manage a consensus network, incur high economic costs, and face other trade-offs that come with deploying a new layer 1. Evolve's goal is to make deploying a chain as easy as it is to deploy a smart contract, cutting the time it takes to bring blockchain products to market from months or even years to just minutes. |
| 65 | +- **Faster time-to-market:** Evolve eliminates the need to bootstrap a validator set, manage a consensus network, incur high economic costs, and face other trade-offs that come with deploying a legacy layer 1\. Evolve's goal is to make deploying a chain as easy as it is to deploy a smart contract, cutting the time it takes to bring blockchain products to market from months (or even years) to just minutes. |
68 | 66 |
|
69 | | -- **Sovereignty**: Evolve also enables developers to deploy sovereign chains for cases where communities require sovereignty. |
| 67 | +- **Sovereignty**: Evolve also enables developers to deploy chains for cases where communities require sovereignty. |
70 | 68 |
|
71 | 69 | ## How can you use Evolve? |
72 | 70 |
|
73 | | -As briefly mentioned above, Evolve could be used in many different ways. From sovereign chains, to settlement layers, and in the future even to L3s. |
| 71 | +As briefly mentioned above, Evolve could be used in many different ways. From chains, to settlement layers, and in the future even to L3s. |
74 | 72 |
|
75 | | -### Chain with any execution environment |
| 73 | +### Chain with any VM |
76 | 74 |
|
77 | 75 | Evolve gives developers the flexibility to use pre-existing ABCI-compatible state machines or create a custom state machine tailored to their chain needs. Evolve does not restrict the use of any specific virtual machine, allowing developers to experiment and bring innovative applications to life. |
78 | 76 |
|
79 | | -### Sovereign chain with Cosmos SDK |
| 77 | +### Cosmos SDK |
80 | 78 |
|
81 | | -Similarly to how developers utilize the Cosmos SDK to build a sovereign layer 1 chain, the Cosmos SDK could be utilized to create a Evolve-compatible chain. |
82 | | -Cosmos-SDK has great [documentation](https://docs.cosmos.network/main) and tooling that developers can leverage to learn. |
| 79 | +Similarly to how developers utilize the Cosmos SDK to build a layer 1 chain, the Cosmos SDK could be utilized to create a Evolve-compatible chain. Cosmos-SDK has great [documentation](https://docs.cosmos.network/main) and tooling that developers can leverage to learn. |
83 | 80 |
|
84 | | -Another possibility is taking an existing layer 1 built with the Cosmos SDK and deploying it as a Evolve chain. This can provide a great opportunity for experimentation and growth. |
| 81 | +Another possibility is taking an existing layer 1 built with the Cosmos SDK and deploying it as a Evolve chain. Evolve gives your network a forward path. Migrate seamlessly, keep your logic, and evolve into a modular, high-performance system without CometBFT bottlenecks and zero validator overhead. |
85 | 82 |
|
86 | 83 | ### Build a settlement layer |
87 | 84 |
|
88 | | -[Settlement layers](https://celestia.org/learn/modular-settlement-layers/settlement-in-the-modular-stack/) are ideal for developers who want to avoid deploying sovereign chains. They provide a platform for chains to verify proofs and resolve disputes. |
89 | | -Additionally, they act as a hub for chains to facilitate trust-minimized token transfers and liquidity sharing between chains that share the same settlement layer. |
90 | | -Think of settlement layers as a special type of execution layer. |
| 85 | +[Settlement layers](https://celestia.org/learn/modular-settlement-layers/settlement-in-the-modular-stack/) are ideal for developers who want to avoid deploying chains. They provide a platform for chains to verify proofs and resolve disputes. Additionally, they act as a hub for chains to facilitate trust-minimized token transfers and liquidity sharing between chains that share the same settlement layer. Think of settlement layers as a special type of execution layer. |
91 | 86 |
|
92 | 87 | ## When can you use Evolve? |
93 | 88 |
|
94 | | -As of today, Evolve is still in the alpha stage. The framework currently provides a centralized sequencer, an execution interface (ABCI or Cosmos SDK), and a connection to a data availability layer. |
| 89 | +As of today, Evolve provides a single sequencer, an execution interface (Engine API or ABCI), and a connection to Celestia. |
95 | 90 |
|
96 | 91 | We're currently working on implementing many new and exciting features such as light nodes and state fraud proofs. |
97 | 92 |
|
98 | | -Head down to the next section to learn more about what's coming for Evolve. If you're ready to start building, you can skip to the [Guides](/guides/gm-world.md) section. |
| 93 | +Head down to the next section to learn more about what's coming for Evolve. If you're ready to start building, you can skip to the [Guides](/guides/quick-start.md) section. |
99 | 94 |
|
100 | | -Spoiler alert, whichever you choose, it's going to be a great rabbit hole! |
| 95 | +Spoiler alert, whichever you choose, it's going to be a great rabbit hole\! |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?v=4&size=40){kind=avatar}
0 commit comments