Skip to content

Commit cde5032

Browse files
committed
Update zkEVM - forced batches
1 parent 3c1f8bf commit cde5032

File tree

1 file changed

+10
-9
lines changed

1 file changed

+10
-9
lines changed

docs/zkEVM/architecture/protocol/malfunction-resistance/sequencer-resistance.md

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -21,23 +21,24 @@ In order to ensure finality in the case of Trusted Sequencer's malfunction, the
2121

2222
Any user can publish a batch to be forced by directly calling `forceBatch` function:
2323

24-
```
25-
function forceBatch(
26-
bytes memory transactions ,
27-
uint256 maticAmount
24+
```bash
25+
function sequenceForceBatches(
26+
ForcedBatchData[] memory batches
2827
) public ifNotEmergencyState isForceBatchAllowed
2928
```
29+
in Etrog it is:
3030

31-
​where,
32-
33-
- `transactions` is the byte array containing the concatenated batch transactions (same as the normal batch transactions format)
34-
- `maticAmount` is the maximum amount of MATIC tokens the user is willing to pay as a forced batch publication fee. The fee for publishing a forced batch is the same as the fee for sequencing, and it is therefore set in the `batchFee` storage variable. Since the fee is paid when a forced batch is published, it will not be paid again when the batch is sequenced.
31+
```bash
32+
function sequenceForceBatches(
33+
BatchData[] calldata batches
34+
) external virtual isSenderAllowedToForceBatches
35+
```
3536

3637
In order to successfully publish forced batch to the `forcedBatches` mapping, the following conditions must be met, otherwise the transaction will revert;
3738

3839
- The contract must not be in emergency state,
3940
- The force batches must be allowed,
40-
- The `maticAmount` argument must be higher than the MATIC fee per batch,
41+
- The `maticAmount` argument must be higher than the MATIC fee per batch. It is the maximum amount of MATIC tokens the user is willing to pay as a forced batch publication fee. The fee for publishing a forced batch is the same as the fee for sequencing, and it is therefore set in the `batchFee` storage variable. Since the fee is paid when a forced batch is published, it will not be paid again when the batch is sequenced.
4142
- The length of the transactions byte array must be less than the value of `MAX_TRANSACTIONS_BYTE_LENGTH` constant (which is set at 120000).
4243

4344
The forced batch is entered in `forcedBatches` mapping keyed by its force batch index.

0 commit comments

Comments
 (0)