Skip to content

[enhancement] Set DACommitment version byte based via onchain version #404

Open
@ethenotethan

Description

@ethenotethan

Currently we hard set the cert version that's prefix encoded in the returned DA commitment bytes to coretypes.VersionThree. To enable >=v4 cert migrations we'll need to update this to be set using the byte value returned from the certVersion method on the EigenDACertVerifier contract.

Also worth noting that the cert version returned from the verifier or coretypes will need to be decremented to reflect the existing version namespace defined for Proxy; ie the following bijective mapping:

  • v3 cert version -> 0x2 cert byte
  • v4 cert version -> 0x3 cert byte
  • v_n cert version -> 0xn-1 cert byte

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions