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/ethereum-and-scroll-differences.mdx
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ Opcodes from the Cancun upgrade are not yet available on Scroll, including `MCOP
38
38
39
39
## EVM Precompiles
40
40
41
-
The `RIPEMD-160` (address `0x3`) `blake2f` (address `0x9`), and `point evaluation` (address `0x0a`) precompiles are currently not supported. The `SHA2-256` (address `0x2`) is currently supported on Scroll Sepolia, but will soon be supported on Scroll Mainnet. Calls to unsupported precompiled contracts will revert. We plan to enable these precompiles in future hard forks.
41
+
The `RIPEMD-160` (address `0x3`) `blake2f` (address `0x9`), and `point evaluation` (address `0x0a`) precompiles are currently not supported. Calls to unsupported precompiled contracts will revert. We plan to enable these precompiles in future hard forks.
42
42
43
43
The `modexp` precompile is supported but only supports inputs of size less than or equal to 32 bytes (i.e. `u256`).
Copy file name to clipboardExpand all lines: src/content/docs/en/developers/guides/running-a-scroll-node.mdx
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -16,9 +16,9 @@ For most developers, using [our official RPC endpoint](/en/developers/developer-
16
16
17
17
### Finding the latest version
18
18
19
-
We recommend using the latest release at https://github.com/scroll-tech/go-ethereum/releases. The required version is `scroll-v5.2.0` 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
-
{/* TODO: update min required version for mainnet after Bernoulli upgrade, also update mainnet genesis info */}
21
-
For the remainder of this guide, `VERSION` will denote the version tag. For example, `scroll-v5.2.0`.
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.3.0` or higher, and for Scroll Sepolia it is `scroll-v5.2.0` 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
+
21
+
For the remainder of this guide, `VERSION` will denote the version tag. For example, `scroll-v5.3.0`.
Copy file name to clipboardExpand all lines: src/content/docs/en/developers/transaction-fees-on-scroll.mdx
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -178,7 +178,7 @@ On Sepolia, an upgraded `L1MessageQueueWithGasPriceOracle` should be used, deplo
178
178
If your system supports off-chain mechanisms, you can also call `eth_estimateGas` and `eth_gasPrice` on any Scroll RPC node to get an estimate of the gas required for a given transaction.
179
179
180
180
<Asidetype="danger"title="Upgrade Notice">
181
-
After the February 2024 Bridge Upgrade, `L1GasPriceOracle` will be deprecated in favor of `L1MessageQueueWithGasPriceOracle`, which will be available at [`0x0d7E906BD9cAFa154b048cFa766Cc1E54E39AF9B`](https://etherscan.io/address/0x0d7E906BD9cAFa154b048cFa766Cc1E54E39AF9B).
181
+
After the February 2024 Bridge Upgrade, `L2GasPriceOracle` will be deprecated in favor of `L1MessageQueueWithGasPriceOracle`, which will be available at [`0x0d7E906BD9cAFa154b048cFa766Cc1E54E39AF9B`](https://etherscan.io/address/0x0d7E906BD9cAFa154b048cFa766Cc1E54E39AF9B).
182
182
183
183
The upgrade is expected to be finalized on February 21, 2024, after a two-week timelock. Scroll Sepolia has already undergone this upgrade. Read more [here](https://scroll.io/blog/protocol-upgrade-bridging-cost-reduction).
, 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).
88
88
89
-
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 a 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 `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.
90
90
91
91
## Finalize Transaction
92
92
@@ -121,18 +121,22 @@ At this stage, the state root of the latest finalized batch can be used trustles
121
121
122
122
This section describes the codec of three data structures in the Rollup contract: `BatchHeader`, `Chunk`, and `BlockContext`.
123
123
124
-
### Scroll Mainnet
124
+
The latest update to the codec was introduced in the Bernoulli upgrade.
|`version`| 1 |`uint8`| 0 | The batch header version |
130
133
|`batchIndex`| 8 |`uint64`| 1 | The index of the batch |
131
-
|`l1MessagePopped`| 8 |`uint64`| 9 | The number of L1 messages poped in the batch |
134
+
|`l1MessagePopped`| 8 |`uint64`| 9 | The number of L1 messages popped in the batch |
132
135
|`totalL1MessagePopped`| 8 |`uint64`| 17 | The number of total L1 messages popped after the batch |
133
136
|`dataHash`| 32 |`bytes32`| 25 | The data hash of the batch |
134
-
|`parentBatchHash`| 32 |`bytes32`| 57 | The parent batch hash |
135
-
|`skippedL1MessageBitmap`| dynamic |`uint256[]`| 89 | A bitmap to indicate which L1 messages are skipped in the batch |
137
+
|`blobVersionedHash`| 32 |`bytes32`| 57 | The versioned hash of the blob with this batch’s data |
138
+
|`parentBatchHash`| 32 |`bytes32`| 89 | The parent batch hash |
139
+
|`skippedL1MessageBitmap`| dynamic |`uint256[]`| 121 | A bitmap to indicate which L1 messages are skipped in the batch |
136
140
137
141
#### `Chunk` Codec
138
142
@@ -143,8 +147,7 @@ This section describes the codec of three data structures in the Rollup contract
143
147
| ... | ... | ... | ... | ... |
144
148
|`block[i]`| 60 |`BlockContext`|`60*i+1`| The block information of `i+1`-th block |
145
149
| ... | ... | ... | ... | ... |
146
-
| `block[n-1]` | 60 | `BlockContext` | `60*n-59` | The block information of the last block
147
-
| `l2Transactions` | dynamic | `bytes` | `60*n+1` | The concatenated RLP encoding of L2 transactions with signatures. The byte length (`uint32`) of RLP encoding is inserted before each transaction. | |
150
+
|`block[n-1]`| 60 |`BlockContext`|`60*n-59`| The block information of the last block |
148
151
149
152
#### `BlockContext` Codec
150
153
@@ -157,20 +160,18 @@ This section describes the codec of three data structures in the Rollup contract
157
160
|`numTransactions`| 2 |`uint16`| 56 | The number of transactions in this block, including both L1 & L2 txs |
158
161
| `numL1Messages` | 2 | `uint16` | 58 | The number of L1 messages in this block
|`version`| 1 |`uint8`| 0 | The batch header version |
167
169
|`batchIndex`| 8 |`uint64`| 1 | The index of the batch |
168
-
|`l1MessagePopped`| 8 |`uint64`| 9 | The number of L1 messages poped in the batch |
170
+
|`l1MessagePopped`| 8 |`uint64`| 9 | The number of L1 messages popped in the batch |
169
171
|`totalL1MessagePopped`| 8 |`uint64`| 17 | The number of total L1 messages popped after the batch |
170
172
|`dataHash`| 32 |`bytes32`| 25 | The data hash of the batch |
171
-
|`blobVersionedHash`| 32 |`bytes32`| 57 | The versioned hash of the blob with this batch’s data |
172
-
|`parentBatchHash`| 32 |`bytes32`| 89 | The parent batch hash |
173
-
|`skippedL1MessageBitmap`| dynamic |`uint256[]`| 121 | A bitmap to indicate which L1 messages are skipped in the batch |
173
+
|`parentBatchHash`| 32 |`bytes32`| 57 | The parent batch hash |
174
+
|`skippedL1MessageBitmap`| dynamic |`uint256[]`| 89 | A bitmap to indicate which L1 messages are skipped in the batch |
174
175
175
176
#### `Chunk` Codec
176
177
@@ -181,7 +182,8 @@ This section describes the codec of three data structures in the Rollup contract
181
182
| ... | ... | ... | ... | ... |
182
183
|`block[i]`| 60 |`BlockContext`|`60*i+1`| The block information of `i+1`-th block |
183
184
| ... | ... | ... | ... | ... |
184
-
|`block[n-1]`| 60 |`BlockContext`|`60*n-59`| The block information of the last block |
185
+
| `block[n-1]` | 60 | `BlockContext` | `60*n-59` | The block information of the last block
186
+
| `l2Transactions` | dynamic | `bytes` | `60*n+1` | The concatenated RLP encoding of L2 transactions with signatures. The byte length (`uint32`) of RLP encoding is inserted before each transaction. | |
185
187
186
188
#### `BlockContext` Codec
187
189
@@ -193,5 +195,3 @@ This section describes the codec of three data structures in the Rollup contract
193
195
|`gasLimit`| 8 |`uint64`| 48 | The gas limit of this block |
194
196
|`numTransactions`| 2 |`uint16`| 56 | The number of transactions in this block, including both L1 & L2 txs |
195
197
| `numL1Messages` | 2 | `uint16` | 58 | The number of L1 messages in this block
Copy file name to clipboardExpand all lines: src/content/docs/en/technology/overview/scroll-upgrades.mdx
+13-9Lines changed: 13 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -30,28 +30,31 @@ This upgrade features a significant reduction in transaction costs by introducin
30
30
-**Scroll Sepolia**
31
31
- Network Upgrade: April 15th, 2024
32
32
-**Scroll Mainnet**
33
-
- TBD
33
+
- Upgrade Initiation: April 15th, 2024
34
+
- Timelock Completion & Upgrade: April 29th, 2024
34
35
35
36
### Technical Details
36
37
37
38
#### Contract changes
38
39
39
-
The contract changes for this upgrade are in [this PR](https://github.com/scroll-tech/scroll/pull/1179).
40
+
The contract changes for this upgrade are in [this PR](https://github.com/scroll-tech/scroll/pull/1179), along with the audit fixes [here](https://github.com/scroll-tech/scroll/pulls?q=is%3Apr+created%3A2024-04-10..2024-04-11+fix+in%3Atitle+label%3Abug). The main changes are as follows:
40
41
41
-
{/* As well as the audit fixes listed here [TODO] */}
42
+
-`ScrollChain` now accepts batches with either calldata or blob encoding in `commitBatch`.
43
+
-`ScrollChain` now supports finalizing blob-encoded batches through `finalizeBatchWithProof4844`.
44
+
-`MultipleVersionRollupVerifier` can now manage different on-chain verifiers for each batch encoding version.
42
45
43
46
#### Node changes
44
47
45
-
The new node version is v5.2.0. See [here](https://github.com/scroll-tech/go-ethereum/releases/tag/scroll-v5.2.0) for the changelog.
48
+
The new node version is `v5.3.0`. See [here](https://github.com/scroll-tech/go-ethereum/releases/tag/scroll-v5.3.0) for the release log.
46
49
47
-
{/*#### Prover changes
50
+
#### zkEVM circuit changes
48
51
49
-
[TODO]
52
+
The new version of zkevm circuits is `v0.10.3`. See [here](https://github.com/scroll-tech/zkevm-circuits/releases/tag/v0.10.3) for the release log.
@@ -61,7 +64,7 @@ This upgrade is a hard fork as it introduces the new blob data type and the SHA2
61
64
62
65
#### Indexers and Bridges
63
66
64
-
This upgrade changes the format that Scroll uses to publish data to Ethereum. Projects that rely on this data should carefully review [the new data format](https://docs.scroll.io/en/technology/chain/rollup/#codec), and check whether their decoders need to be adjusted. A summary of the new format:
67
+
This upgrade changes the format that Scroll uses to publish data to Ethereum. Projects that rely on this data should carefully review [the new data format](/en/technology/chain/rollup/#codec), and check whether their decoders need to be adjusted. A summary of the new format:
65
68
66
69
- The format of [`BlockContext`](https://github.com/scroll-tech/scroll/blob/5362e28f744093495c1c09a6b68fc96a3264278b/common/types/encoding/codecv1/codecv1.go#L125) will not change.
67
70
-`Chunks` will [no longer include](https://github.com/scroll-tech/scroll/blob/5362e28f744093495c1c09a6b68fc96a3264278b/common/types/encoding/codecv1/codecv1.go#L162) the L2 transaction data. This will instead be [stored in a blob](https://github.com/scroll-tech/scroll/blob/5362e28f744093495c1c09a6b68fc96a3264278b/common/types/encoding/codecv1/codecv1.go#L284) attached to the `commitBatch` transaction.
@@ -71,6 +74,7 @@ This upgrade changes the format that Scroll uses to publish data to Ethereum. Pr
71
74
72
75
This upgrade involves a breaking change in [zkevm-circuits](https://github.com/scroll-tech/zkevm-circuits). Operators running a prover node are required to upgrade.
0 commit comments