[Consensus][Masternode] Implement Adaptive Reward Boost and PoSe Status Telemetry - #2983
Closed
RainDeveloper69 wants to merge 9 commits into
Closed
Conversation
Old nonce never met the target for the April 30 timestamp so the genesis assert aborted on startup, remined with the same timestamp.
hashTarget held a reference to a temporary, so the miner ended up comparing the hash against itself and instantly submitting invalid blocks in a loop. Take it by value.
All at 201 meant the chain never crossed an upgrade boundary. Block version is gated per upgrade and the stake modifier changes at POS_V2, so none of it got exercised. Spread from 201 to 700.
Testnet was still on LLMQ_400_60, which needs 300 masternodes before a quorum forms. Testnet has nowhere near that so chainlocks could never form at all. LLMQ_50_60 needs 40, which a testnet fleet can actually reach.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary & Context
This PR directly builds upon PR #2982 (@Liquid369's Testnet6 genesis and LLMQ quorum staging) to introduce an Adaptive Masternode Fallback & Economic Self-Healing Mechanism for Version 6 (
UPGRADE_V6_0).Key Features & Modifications
1. Dynamic Masternode Incentive Boost (1,200 MN Threshold)
LLMQ_400_60) risk formation failure, preventing exchanges from offering 1-confirmation instant ChainLock settlements.src/validation.cpp(GetMasternodePayment), when active valid Masternodes drop below 1,200, the consensus engine dynamically scales the Masternode block reward by +25% (from 40% up to 50% per block).2. Enhanced Real-Time PoSe Status Telemetry
src/evo/deterministicmns.cpp(CDeterministicMNState::ToJson)"PoSeStatus"string output (OK_HEALTHY,WARNING_PENALIZED,BANNED) toprotx infoandgetmasternodestatusRPC endpoints, giving node operators clear visibility before silent node bans occur.3. Space-Path Build Compatibility Fix
contrib/devtools/hexdump_util.sh"$INFILE"and"$OUTFILE") to ensure builds succeed when workspace paths contain spaces.Relationship to PR #2982
Testing & Verification
libCOMMON_A,libSERVER_A,libWALLET_A).evo_deterministicmns_tests.