Skip to content

Propagate L2 -> L1 messages #381

@LHerskind

Description

@LHerskind

For L2 contracts that are transmitting messages to L1, we must take the L2 messages published as part of the kernel, and include it in the calldata hash. Likewise, it needs to be included in the L2 block that are inputted into the contract to update its method of deriving calldatahashes for the kernels

Require updates to:

  • Circuits
  • Contracts
  • Typescript

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions