feat: masternode hard fork signal transaction payload #301
Conversation
This file contains 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
|
Reported as working here: https://discord.com/channels/484546513507188745/495696706638184482/1283807715013034074 |
This was referenced Sep 12, 2024
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.
Issue being fixed or feature implemented
Adds masternode hard fork signal special transaction payload based on the EHF DIP and docs.
What was done?
Used ChatGPT to create a PR modeled after #293.
Someone that knows what they're doing should thoroughly review this and test it (probably with dashcore-node on mainnet also to see if it will actually sync past the block containing the mnhftx).
How Has This Been Tested?
Includes tests that check against an actual mainnet mnhftx
Breaking Changes
None?
Checklist: