Skip to content

Supernode: Finalized Label SuperAuthorization #19188

@axelKingsley

Description

@axelKingsley

Following from:

#18976

Now, when the CL attempts to mark some block finalized by its rules, we must also block it by additional rules:

https://www.notion.so/oplabs/Supervisor-V2-Main-Loop-and-Logic-Flow-Diagrams-265f153ee162804388dac933f525de7b

The node will appear with an L2/L1 block to finalize, and we will need to make sure that verification is complete considerate of that L1. What this means is:

  • Every Verification Activity stores a notion of the latest L2 timestamp it verified, the L2 heads, and importantly - The L1 block used to do so
  • When finalization would occur in the Virtual Node, the SuperAuthority can be consulted CanFinalize?
  • Chain Container can satisfy that query by consulting the Verifications and ensuring that the L2 block is correct, and the L1 block is known to be in the verified range for all Verifiers

Like other authority signals, a simple approve/deny is returned, and the node simply does not finalize data which it is not permitted to.

Metadata

Metadata

Labels

M-needs-triageMeta: this issue needs to be labelled

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions