You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/en/developers/guides/running-a-scroll-node.mdx
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ For most developers, using [our official RPC endpoint](/en/developers/developer-
19
19
20
20
We recommend using the latest release at https://github.com/scroll-tech/go-ethereum/releases. The required version for Scroll Mainnet is `scroll-v5.5.0` or higher, and for Scroll Sepolia it is `scroll-v5.4.2` or higher. If you'd like to keep up with new node releases, go to https://github.com/scroll-tech/go-ethereum, click on **Watch**, **Custom**, and make sure that **Releases** is selected.
21
21
22
-
For the remainder of this guide, `VERSION` will denote the version tag. For example, `scroll-v5.8.0`.
22
+
For the remainder of this guide, `VERSION` will denote the version tag. For example, `scroll-v5.8.34`.
As the team continues to progress on Scroll's roadmap, we will be upgrading the Scroll network to include new features and improvements.
10
12
11
13
The following contracts are used to initiate upgrades and execute upgrades after the two-week timelock period:
@@ -19,6 +21,69 @@ The following contracts are used to initiate upgrades and execute upgrades after
19
21
20
22
You can join our [Telegram channel for technical updates](https://t.me/scroll_tech_updates), which includes future upgrade announcements and on-chain operation events.
21
23
24
+
## Euclid Upgrade
25
+
26
+
<Asidetype="note"title="Note">
27
+
Detailed impacts and action items for partner can be found in this [Note for Partners](https://scrollzkp.notion.site/Euclid-Upgrade-5-Note-for-Partners-1ad7792d22af808cad5ac643a5ecdaf0)
28
+
</Aside>
29
+
30
+
### Overview
31
+
This upgrade contains five main changes:
32
+
- Migration to OpenVM Prover.
33
+
- Migration to MPT state commitment.
34
+
- Optimized rollup process.
35
+
- EIP-7702 and RIP-7212 support.
36
+
- Stage-1 readiness.
37
+
38
+
These changes will result in lower fees, higher throughput, better security, better compatibility, and more advanced features that users and developers on Scroll can enjoy.
39
+
40
+
### Timeline
41
+
42
+
-**Scroll Sepolia**
43
+
- Phase 1: March 11th, 2025
44
+
- Phase 2: March 13th, 2025
45
+
-**Scroll Mainnet**
46
+
- Phase 1: April 16th, 2025
47
+
- Phase 2: April 22nd, 2025
48
+
49
+
### Features
50
+
51
+
#### OpenVM Prover
52
+
Scroll has been among the pioneers of ZK technology through our EVM bytecode compatible halo2 zkEVM. ZK technology has continued to progress rapidly ever since, and now general-purpose RISC-V zkVMs are becoming practical. In the Euclid upgrade we are deprecating our halo2 circuits in favor of a new prover built on top of [OpenVM](https://scroll.io/blog/the-first-release-of-the-openvm-framework-is-live).
53
+
54
+
The new OpenVM prover offers numerous benefits. Prover code is easier to reason about and to audit. We can better reuse code among different components. We can also reduce proving costs and latency. Finally, the new prover will enable us to prove arbitrarily complex transactions, allowing us to remove the circuit capacity checker module that has been a major bottleneck on sequencer throughput.
55
+
56
+
#### MPT State Commitment
57
+
Scroll currently uses a zk-friendly state commitment data structure called [zktrie](https://docs.scroll.io/en/technology/sequencer/zktrie/). With the new OpenVM prover, it is now practical to prove Ethereum’s state structure: the [Merkle-Patricia Trie](https://ethereum.org/en/developers/docs/data-structures-and-encoding/patricia-merkle-trie), also known as MPT. Scroll is now deprecating the zktrie and adopting MPT.
58
+
59
+
MPT unlocks better sequencer performance and offers better compatibility for dapps relying on L2 state proofs.
60
+
61
+
#### Optimized Rollup Process
62
+
In Euclid, we are rolling out a series of optimizations to the rollup process. These result in major reductions in Data Availability (DA) overhead, and ultimately lower fees for users.
63
+
64
+
The main optimizations are:
65
+
- Move blob verification from contract code to zk circuits.
66
+
- Amortize message queue commitment cost.
67
+
- Move L2 block header data from calldata to blobs.
68
+
- Commit multiple blobs in a single transaction.
69
+
- These changes combined are estimated to reduce batch commitment costs by up to 90%.
70
+
71
+
In addition, Scroll L2 nodes will deprecate Clique (the current Proof-of-Authority consensus) and will start reading the authorized L2 block signer from the new system config contract on L1.
72
+
73
+
#### Powerful Smart Accounts
74
+
75
+
In Euclid, Scroll is adopting [EIP-7702](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-7702.md) and [RIP-7212](https://github.com/ethereum/RIPs/blob/master/RIPS/rip-7212.md). Adopting 7702 in parallel with Ethereum’s [Pectra upgrade](https://blog.ethereum.org/2025/02/14/pectra-testnet-announcement) ensures that Scroll maintains a high degree of compatibility with Ethereum. These features will also allow Scroll users and developers to tap into the latest technologies in smart accounts: Users can add smart contract functionalities to their existing accounts, use passkeys for signing authorizations, and benefit from the emerging UX improvements that these new standards enable.
76
+
77
+
#### Stage-1
78
+
79
+
In Euclid, we are rolling out important safety guarantees that will allow Scroll to reach Stage-1 based on the [standard defined by L2BEAT](https://medium.com/l2beat/introducing-stages-a-framework-to-evaluate-rollups-maturity-d290bb22befe).
80
+
81
+
Enforced transaction inclusion is a censorship resistance mechanism. It allows users to enqueue a transaction directly from Ethereum, forcing the sequencer to include it.
82
+
Permissionless batch submission is a mechanism to prevent liveness failure. In the unlikely scenario that the Scroll sequencer stops posting or finalizing batches for an extended period of time, this mechanism allows anyone to step up and start posting and finalizing batches.
83
+
Both mechanisms force the Scroll sequencer to do its job. As such, they serve as deterrents, and they offer important safety guarantees to the users.
84
+
85
+
We have also recently transferred control to the [Security Council](https://scroll.io/blog/introducing-scroll-security-council), an independent body of 12 reputable members, forming a 9/12 multisig. The Euclid upgrade will be the first upgrade to be executed by the Security Council.
86
+
22
87
## DarwinV2 Upgrade
23
88
24
89
### Overview
@@ -340,4 +405,5 @@ The original gas price oracle contract will be deprecated: it will no longer be
0 commit comments