[Stacks 2.1] Miner error for epoch `start_height` and `pox_2_activation` config values

[zone117x]

Initial context for this issue in the comments from another issue: #3261 (comment)

A regtest+krypton miner will error and fail to mine with certain epoch start_height and pox_2_activation (i.e. v1_unlock_height) config.toml values.

Once the pox_2_activation height is reached, the error Failure fetching recipient set: ChainstateError(ClarityError(Interpreter(Unchecked(NoSuchContract("ST000000000000000000002AMW42H.pox-2"))))) is logged in an indefinite loop.

Some config values do work, but approximately 3/4ths of different combinations of these config values will trigger this error.

See the full debug log output here from when this error happens.

Go to the end of the log to see where the miner loops with the error:

ERRO [1668778959.365802] [testnet/stacks-node/src/neon_node.rs:1674] [miner-block-http://0.0.0.0:20443] Relayer: Failure fetching recipient set: ChainstateError(ClarityError(Interpreter(Unchecked(NoSuchContract("ST000000000000000000002AMW42H.pox-2")))))

See here for the config.toml file used, and here for the btc-mining-script.sh script used.

I've also added pushed a docker setup so anyone can easily reproduce this locally, see hirosystems/stacks-regtest-env#16

[zone117x]

@jcnelson let me know if there's anything else I can provide to help with this. I can easily test different config values, and/or a potential fix branch if you push any.

cc @gregorycoppola who has also tested this and may have more context

[jcnelson]

Hey @zone117x , try this PR: #3409

[jcnelson]

We've added test coverage for appropriate values for start_height and pox_2_activation, and have done dress rehearsals. Going to go ahead and close this.

[blockstack-devops]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.