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/technology/chain/rollup.mdx
+9-6Lines changed: 9 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ function commitBatchWithBlobProof(
61
61
bytes[] memory chunks,
62
62
bytes calldata skippedL1MessageBitmap,
63
63
bytes calldata blobDataProof
64
-
) external;
64
+
) external override OnlySequencer;
65
65
```
66
66
67
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.
@@ -90,24 +90,27 @@ In addition, the `commitBatchWithBlobProof` function contains a bitmap of skippe
90
90
91
91
## Finalize Transaction
92
92
93
-
The Finalize Transaction finalizes the previously-committed batch with a validity proof. The transaction also submits the state root and the withdraw root after the batch. Here is the function signature of `finalizeBatchWithProof`:
93
+
The Finalize Transaction finalizes the previously-committed batch with a validity proof. The transaction also submits the state root and the withdraw root after the batch. Here is the function signature of `finalizeBatchWithProof4844`:
94
94
95
95
```solidity
96
-
function finalizeBatchWithProof(
96
+
function finalizeBatchWithProof4844(
97
97
bytes calldata batchHeader,
98
-
bytes32 prevStateRoot,
98
+
bytes32,
99
99
bytes32 postStateRoot,
100
100
bytes32 withdrawRoot,
101
+
bytes calldata blobDataProof,
101
102
bytes calldata aggrProof
102
103
) external override OnlyProver
103
104
```
104
105
105
-
The `finalizeBatchWithProof` function first verifies if the batch has been committed in the contract. It then calculates the public input hash as follows
106
+
The `finalizeBatchWithProof4844` function first verifies if the batch has been committed in the contract. It then calculates the public input hash as follows
, where the `prevStateRoot` is read from the `finalizedStateRoots` map variable on the contract and `blobVersionedHash` is as described in the [Codec](#batchheader-codec) section.
113
+
111
114
The public input hash and the validity proof are sent to the plonk solidity verifier. Once the verification passes, the new state root and withdraw root are stored in the `ScrollChain` contract.
0 commit comments