specs
specs copied to clipboard
**Description** Adds a way for the `L2ToL2CrossDomainMessenger` to "send-back" failed messages. These failed messages are stored on the origin domain's `L2ToL2CrossDomainMessenger`. This enables smart contracts to handle "failed" messages. e.g....
## Overview Introduces an addition to the `Granite` hardfork, where upon activation, consensus will require L2 block headers to contain the 32 byte account storage root of the `L2ToL1MessagePasser` predeploy...
**Description** Fixing a typo: `interopability` -> `interoperability` **Tests** It's just a documentation typo fix. **Additional context** Nope **Metadata** None
since `ADD_DEPENDENCY` and `REMOVE_DEPENDENCY` are prefixed by a verb, changing `GAS_PAYING_TOKEN` to `SET_GAS_PAYING_TOKEN` leads to greater consistency
this makes the behavior explicit for attempting to add a chain id already in the dependency set
**Description** Adds a way for the `CrossDomainMessenger` to "send-back" failed messages. These failed messages are stored on the origin domain in a `RollbackInbox` contract. This enables smart contracts to handle...
We can simplify derivation by having the pipeline always ensure safe head progression when processing payloads pulled from L1. 1. Always Valid (empty deposits-only block) 3. A proper L2 block...
**Description** This PR proposes a minimal standardized interface for block construction and transaction management between the Sequencer and a local Block Builder. Separating Block Building from the Sequencer's Execution Engine...
**Description** Explore what applying a predicate to the inputs as part of the derivation pipeline would look like. The predicate is defined using evm bytecode and can therefore be quite...
# Description Specify the "driver" component of the rollup node. The "driver" is a concept from bedrock, except it used to be very synchronous, and parts of the functionality were...