MN_RR should not be auto-activated on Main net without intentional release of code (and not by spork), but they are need on test net to test platform

so is SPORK_24_EHF not longer need or is it a non-mainnet only spork now?

MN_RR should not be auto-activated on Main net without intentional release of code (and not by spork), but they are need on test net to test platform

so is SPORK_24_EHF not longer need or is it a non-mainnet only spork now?

Basically non-main net only, a value could still be set; but it doesn't (shouldn't) affect anything on mainnet

so is SPORK_24_EHF not longer need or is it a non-mainnet only spork now?

This spork has been introduced to prevent activation of mn_rr before platform is ready.

As discussed today:

• Asset Unlock transaction is not tested properly on testnet yet; not tested properly feature should not be potentially active on mainnet; also it may require consensus rules to chage
• 2 forks are confusing for dash users. Let's keep the rule "1 major version = 1 hard-fork"
• activation of a hard fork by spork is it bad idea; because it should relay on user's update, not DCG command to do anything.

So, mn_rr requires a new release v21 or v20.1; the spork maybe even dropped then.

For testnet it is needed for platform's need + to test EHF mechanism.

Issue created here: #5644