Skip to content

Create a state containing post-NU5 blocks #8534

Open
@upbqdn

Description

Address

// We need to set the NU5 activation height higher than the height of the last block for
// this test because we currently have only the first 10 blocks from the public Testnet,
// none of which are compatible with NU5 due to the following consensus rule:
//
// > [NU5 onward] hashBlockCommitments MUST be set to the value of
// > hashBlockCommitments for this block, as specified in [ZIP-244].
//
// Activating NU5 at a lower height and using the 10 blocks causes a failure in
// [`zebra_state::populated_state`].

Being able to create a state containing blocks for which we could activate NU5 is beneficial for tests, see: #8535.

Blocks #8535.

Metadata

Assignees

No one assigned

    Labels

    A-stateArea: State / database changesC-testingCategory: These are testsNU-5Network Upgrade: NU5 specific tasksrustPull requests that update Rust code

    Type

    Projects

    • Status

      New

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions