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
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ For most developers, using [our official RPC endpoint](/en/developers/developer-
18
18
19
19
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.
20
20
21
-
For the remainder of this guide, `VERSION` will denote the version tag. For example, `scroll-v5.5.0`.
21
+
For the remainder of this guide, `VERSION` will denote the version tag. For example, `scroll-v5.6.0`.
22
22
23
23
### Hardware Requirements
24
24
@@ -118,7 +118,7 @@ Running the node in Docker might have a significant impact on node performance.
Copy file name to clipboardExpand all lines: src/content/docs/en/technology/chain/rollup.mdx
+47-6Lines changed: 47 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,18 +52,19 @@ The rollup process can be broken down into three phases: transaction execution,
52
52
53
53
## Commit Transaction
54
54
55
-
The Commit Transaction submits the block information and transaction data to L1 for data availability. The transaction includes the parent batch header, chunk data, and a bitmap of skipped L1 messages. The parent batch header designates the previous batch that this batch links to. The parent batch must be committed before; otherwise, the transaction will be reverted. See the `commitBatch` function signature below.
55
+
The Commit Transaction submits the block information and transaction data to L1 for data availability. The transaction includes the parent batch header, chunk data, and a bitmap of skipped L1 messages. The parent batch header designates the previous batch that this batch links to. The parent batch must be committed before; otherwise, the transaction will be reverted. See the `commitBatchWithBlobProof` function signature below.
56
56
57
57
```solidity
58
-
function commitBatch(
58
+
function commitBatchWithBlobProof(
59
59
uint8 version,
60
60
bytes calldata parentBatchHeader,
61
61
bytes[] memory chunks,
62
-
bytes calldata skippedL1MessageBitmap
63
-
) external override OnlySequencer
62
+
bytes calldata skippedL1MessageBitmap,
63
+
bytes calldata blobDataProof
64
+
) external;
64
65
```
65
66
66
-
After the `commitBatch` function verifies the parent batch is committed before, it constructs the batch header of the batch and stores the hash of the batch header in the `ScrollChain` contract.
67
+
After the `commitBatchWithBlobProof` function verifies the parent batch is committed before, it constructs the batch header of the batch and stores the hash of the batch header in the `ScrollChain` contract.
67
68
68
69
```solidity
69
70
mapping(uint256 => bytes32) public committedBatches;
, where `block.l1TxHashes` are the concatenated transaction hashes of the L1 transactions in this block and `block.l2TxHashes` are the concatenated transaction hashes of the L2 transactions in this block. Note that the transaction hashes of L1 transactions are not uploaded by the rollup node, but instead directly loaded from the `L1MessageQueue` contract given the index range of included L1 messages in this block. The L2 transaction hashes are calculated from the RLP-encoded bytes in the `l2Transactions` field in the [`Chunk`](#Chunk-Codec).
87
88
88
-
In addition, the `commitBatch` function contains a bitmap of skipped L1 messages. Unfortunately, this is due to the problem of proof overflow. If the L1 transaction corresponding to an L1 message exceeds the circuit capacity limit, we won't be able to generate a valid proof for this transaction and thus cannot finalize it on L1. Scroll is working actively to eliminate the proof overflow problem through upgrades to our proving system.
89
+
In addition, the `commitBatchWithBlobProof` function contains a bitmap of skipped L1 messages. Unfortunately, this is due to the problem of proof overflow. If the L1 transaction corresponding to an L1 message exceeds the circuit capacity limit, we won't be able to generate a valid proof for this transaction and thus cannot finalize it on L1. Scroll is working actively to eliminate the proof overflow problem through upgrades to our proving system.
89
90
90
91
## Finalize Transaction
91
92
@@ -123,8 +124,48 @@ This section describes the codec of three data structures in the Rollup contract
123
124
The latest update to the codec was introduced in the [Bernoulli upgrade](/technology/overview/scroll-upgrades#bernoulli-upgrade).
Copy file name to clipboardExpand all lines: src/content/docs/en/technology/overview/scroll-upgrades.mdx
+103Lines changed: 103 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,6 +19,109 @@ The following contracts are used to initiate upgrades and execute upgrades after
19
19
20
20
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
21
22
+
## Darwin Upgrade
23
+
24
+
### Overview
25
+
26
+
This upgrade will reduce gas fees by 34% by using a single aggregated proof for multiple batches, eliminating the need to finalize each batch individually.
27
+
28
+
- Darwin uses a new [V3 batch codec](https://github.com/scroll-tech/da-codec/tree/main/encoding/codecv3).
29
+
- In addition to the previous notions of `chunk` and `batch`, we have introduced a new concept called `bundle`.
30
+
-`Chunk`: A unit of zkEVM proving, consisting of a list of L2 blocks.
31
+
-`Batch`: A collection of chunks encoded into one EIP-4844 blob, serving as the unit of Data Availability.
32
+
-`Bundle`: A series of batches that functions as the unit of finalization.
33
+
34
+
The main difference compared to Curie is that Scroll will now finalize multiple batches using a single aggregated bundle proof.
35
+
36
+
- The on-chain bundle proof verifier uses a new public input layout.
37
+
38
+
### Timeline
39
+
40
+
-**Scroll Sepolia**
41
+
- Network Upgrade: August 14th, 2024
42
+
-**Scroll Mainnet**
43
+
- Upgrade Initiation: August 5th, 2024
44
+
- Timelock Completion & Upgrade: August 21st, 2024
45
+
46
+
### Technical Details
47
+
48
+
#### Contract Changes
49
+
50
+
*Note: Since the previous Curie upgrade, we have migrated the Scroll contracts to a new repo at [scroll-contracts](https://github.com/scroll-tech/scroll-contracts).*
51
+
52
+
The code changes for this upgrade are implemented in [this PR](https://github.com/scroll-tech/scroll-contracts/pull/4). The key changes are as follows:
53
+
54
+
- We have introduced a new `BatchHeaderV3Codec`.
55
+
- We have changed how messages are processed in the `L1MessageQueue` contract. Prior to Darwin, we would process messages when a batch is finalized. After Darwin, most of this processing is moved to the commit step.
56
+
- We have introduced a new public input format for bundle proofs. This is implemented in a new contract `IZkEvmVerifierV2`, which is in turn added to `MultipleVersionRollupVerifier`.
57
+
- In the `ScrollChain` contract `version=3` batches will now be committed through a new function called `commitBatchWithBlobProof`. Bundles will be finalized using a new function called `finalizeBundleWithProof`.
58
+
59
+
See the contract [release notes](https://github.com/scroll-tech/scroll-contracts/releases/tag/v1.0.0) for more information.
60
+
61
+
#### Node Changes
62
+
63
+
The new node version is `v5.6.0`. See the [release notes](https://github.com/scroll-tech/go-ethereum/releases/tag/scroll-v5.6.0) for more information.
64
+
65
+
The main changes are:
66
+
67
+
- Implementation of timestamp-based hard forks.
68
+
- Processing V3 batch codec in rollup-verifier.
69
+
70
+
#### zkEVM circuit changes
71
+
72
+
The new version of zkevm circuits is `v0.12.0`. See [here](https://github.com/scroll-tech/zkevm-circuits/releases/tag/v0.12.0) for the release log.
73
+
74
+
We have introduced a `RecursionCircuit` that will bundle multiple sequential batches by recursively aggregating the SNARKs from the `BatchCircuit` (previously `AggregationCircuit`). The previously 5 layer proving system is now 7 layers as we introduce:
75
+
76
+
- 6th Layer (layer5): `RecursionCircuit` that recursively aggregates `BatchCircuit` SNARKs.
77
+
- 7th Layer (layer6): `CompressionCircuit` that compresses the `RecursionCircuit` SNARK and produce an EVM-verifiable validity proof.
78
+
79
+
The public input to the `BatchCircuit` is now context-aware of the “previous” `batch`, which allows us to implement the recursion scheme we adopted (described [here](https://scrollzkp.notion.site/Upgrade-4-Darwin-Documentation-05a3ecb59e9d4f288254701f8c888173) in-depth).
80
+
81
+
#### Audits
82
+
83
+
- TrailofBits: coming soon!
84
+
85
+
### Compatibility
86
+
87
+
#### Sequencer and Follower Nodes (l2geth)
88
+
89
+
This upgrade does not alter the state transition function and is therefore backward-compatible. However, we strongly recommend node operators to upgrade to [v5.6.0](https://github.com/scroll-tech/go-ethereum/releases/tag/scroll-v5.6.0).
90
+
91
+
#### Dapps and Indexers
92
+
93
+
There are some major changes to how we commit and finalize batches after Darwin.
94
+
95
+
- Batches will be encoded using the new [V3 batch codec](https://github.com/scroll-tech/da-codec/tree/main/encoding/codecv3). This version adds two new fields:
96
+
1.`lastBlockTimestamp` (the timestamp of the last block in this batch).
97
+
2.`blobDataProof` (the KZG challenge point evaluation proof).
98
+
99
+
This version removes `skippedL1MessageBitmap`. There will be no changes to how the blob data is encoded and compressed.
100
+
- Batches will be committed using the `commitBatchWithBlobProof` function (instead of the previous `commitBatch`).
- The semantics of the `FinalizeBatch` event will change: It will now mean that all batches between the last finalized batch and the event’s `_batchIndex` have been finalized. The event’s stateRoot and withdrawRoot values belong to the last finalized batch in the bundle. Finalized roots for intermediate batches are no longer available.
117
+
118
+
The semantics of the `CommitBatch` and `RevertBatch` events will not change.
119
+
120
+
Recommendations:
121
+
122
+
- Indexers that decode committed batch data should be adjusted to use the new codec and the new function signature.
123
+
- Indexers that track batch finalization status should be adjusted to consider the new event semantics.
0 commit comments