Skip to content

Merge protocol table commitment consistency checks #1351

@ledwards2225

Description

@ledwards2225

A consistency check is needed to ensure that the full ecc op table constructed at step $i$ of the merge protocol is identical to the "previous" ecc op table utilized at step $i+1$. This can be done via a commitment consistency check in the circuit that recursively verifies the $i+1$th merge proof. The mechanism is similar to that used for the Databus consistency checks.

Metadata

Metadata

Labels

merge protocolHaving to do with the goblin EC op merge protocolprioSuggested to prioritized

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