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: docs/zkEVM/architecture/protocol/malfunction-resistance/sequencer-resistance.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ mapping(uint64 => bytes32) public forcedBatches;
17
17
18
18
Although the Trusted Sequencer is incentivized to sequence the forced batches published in the `forcedBatches` mapping, this does not guarantee finality of the transactions' execution in those batches.
19
19
20
-
In order to ensure finality in the case of Trusted Sequencer's malfunction, the L1 `PolygonZkEVM.sol` contract has an alternative batch sequencing function called `sequenceForceBatches`. This function allows anyone to sequence forced batches that have been published in the `multiplierBatchFee` mapping for a time period, specified by the public constant `FORCE_BATCH_TIMEOUT`, yet they have not been sequenced. The timeout is set to 5 days.
20
+
In order to ensure finality in the case of Trusted Sequencer's malfunction, the L1 `PolygonZkEVM.sol` contract has an alternative batch sequencing function called `sequenceForceBatches`. This function allows anyone to sequence forced batches that have been published for a time period, specified by the public constant `forceBatchTimeout`, yet they have not been sequenced. The timeout is set to 5 days.
21
21
22
22
Any user can publish a batch to be forced by directly calling `forceBatch` function:
23
23
@@ -38,7 +38,7 @@ In order to successfully publish forced batch to the `forcedBatches` mapping, th
38
38
- The contract must not be in emergency state,
39
39
- The force batches must be allowed,
40
40
- The `maticAmount` argument must be higher than the MATIC fee per batch,
41
-
- The length of the transactions byte array must be less than the value of `MAX_TRANSACTIONS_BYTE_LENGTH` constant (which is set at 300000).
41
+
- The length of the transactions byte array must be less than the value of `MAX_TRANSACTIONS_BYTE_LENGTH` constant (which is set at 120000).
42
42
43
43
The forced batch is entered in `forcedBatches` mapping keyed by its force batch index.
44
44
@@ -76,7 +76,7 @@ function sequenceForceBatches(
76
76
77
77
The `sequenceForceBatches` function is similar to the `sequenceBatches` function, but it can be called by anyone if batch forcing is enabled.
78
78
79
-
The `sequenceForceBatches` function determines whether each batch in the submitted sequence has been published to the `forcedBatches` mapping for a period of time greater than the `FORCE BATCH TIMEOUT`.
79
+
The `sequenceForceBatches` function determines whether each batch in the submitted sequence has been published to the `forcedBatches` mapping for a period of time greater than the `forceBatchTimeout`.
80
80
81
81
Because the MATIC batch fee was paid at the time of publication, it will not be required to be paid again.
0 commit comments