Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion specs/protocol/isthmus/exec-engine.md
Original file line number Diff line number Diff line change
Expand Up @@ -278,7 +278,7 @@ of a transaction now includes the worst-case operator fee.

`operatorFeeScalar` and `operatorFeeConstant` are loaded in a similar way to the `baseFeeScalar` and
`blobBaseFeeScalar` used in the [`L1Fee`](../../protocol/exec-engine.md#ecotone-l1-cost-fee-changes-eip-4844-da).
calculation. In more detail, these parameters can be accessed in two interchangable ways.
calculation. In more detail, these parameters can be accessed in two interchangeable ways.

- read from the deposited L1 attributes (`operatorFeeScalar` and `operatorFeeConstant`) of the current L2 block
- read from the L1 Block Info contract (`0x4200000000000000000000000000000000000015`)
Expand Down
2 changes: 1 addition & 1 deletion specs/protocol/jovian/exec-engine.md
Original file line number Diff line number Diff line change
Expand Up @@ -129,7 +129,7 @@ As a result, blocks with high DA usage may cause the base fee to increase in sub
### Scalar loading

The `daFootprintGasScalar` is loaded in a similar way to the `operatorFeeScalar` and `operatorFeeConstant`
[included](../isthmus/exec-engine.md#operator-fee) in the Isthmus fork. It can be read in two interchangable ways:
[included](../isthmus/exec-engine.md#operator-fee) in the Isthmus fork. It can be read in two interchangeable ways:

- read from the deposited L1 attributes (`daFootprintGasScalar`) of the current L2 block
(decoded according to the [jovian schema](./l1-attributes.md))
Expand Down
2 changes: 1 addition & 1 deletion specs/protocol/superchain-upgrades.md
Original file line number Diff line number Diff line change
Expand Up @@ -103,7 +103,7 @@ The major/minor/patch versions should align with that of the upstream protocol t
Users of the protocol can choose to implement custom support for the alternative `<build>`,
but may work out of the box if the major features are consistent with that of the upstream protocol version.

The 8 byte `<build>` identifier may be presented as a string for human readability if the contents are alpha-numeric,
The 8 byte `<build>` identifier may be presented as a string for human readability if the contents are alphanumeric,
including `-` and `.`, as outlined in the [Semver] format specs. Trailing `0` bytes can be used for padding.
It may be presented as `0x`-prefixed hex string otherwise.

Expand Down