Skip to content

Regtest mode attempts to sign transactions using the wrong consensus branch id #3534

@bitcartel

Description

@bitcartel

@LarryRuane wrote a test which set activation heights for overwinter and sapling. The test passed but failed on master, so we bisected to find a problem with 40b9527.

The issue is that regtest mode cannot rely on release height, so the Sapling branch id was being selected instead of Overwinter when signing an Overwinter tx.

chainHeight = 377000
...chainActive.Height() + 1 = 202
...APPROX_RELEASE_HEIGHT = 377000
consensusBranchId = 76b809bb
Assertion failed: expected: <success> but was: <failed>

whereas the expected output is:

chainHeight = 202
...chainActive.Height() + 1 = 202
...APPROX_RELEASE_HEIGHT = 377000
consensusBranchId = 5ba81b19

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-rpc-interfaceArea: RPC interfaceI-regressionThis is a regression, i.e. something that previously worked but now does not due to a change we madeNU1-saplingNetwork upgrade: Sapling-specific tasks

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions