-
Notifications
You must be signed in to change notification settings - Fork 1.2k
feat: remove SPORK_3_INSTANTSEND_BLOCK_FILTERING and SPORK_9_SUPERBLOCKS_ENABLED #7278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Changes from all commits
afcf3d1
ee90879
3d9e80e
b2cde07
18b990b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,19 @@ | ||
| Removed Sporks | ||
| -------------- | ||
|
|
||
| * `SPORK_3_INSTANTSEND_BLOCK_FILTERING` and `SPORK_9_SUPERBLOCKS_ENABLED` have | ||
| been removed. These sporks were already effectively always enabled on mainnet | ||
| but continued to gate behavior on test networks (testnet, regtest, and devnet). | ||
| The associated functionality (InstantSend conflicting-block rejection and | ||
| superblock payments) is now permanently enabled across all networks, and the | ||
| sporks will no longer appear in the `spork` RPC output. | ||
|
|
||
| Updated RPCs | ||
| ------------ | ||
|
|
||
| * `getblocktemplate` now always reports `superblocks_enabled` as `true`. The | ||
| field is retained for backwards compatibility. | ||
|
|
||
| * `getblocktemplate` now requires a fully synced node at superblock heights. | ||
| This check is skipped on test networks. Previously it was gated by | ||
| `SPORK_9_SUPERBLOCKS_ENABLED` which was already always active on mainnet. | ||
|
Comment on lines
+4
to
+19
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🟡 Suggestion: Release notes still omit that This note covers the removed sporks disappearing from source: ['codex-general'] 🤖 Fix this with AI agents |
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💬 Nitpick: Release notes should mention
getblocktemplatesync requirement on test chainsThe release notes document that
getblocktemplatenow always reportssuperblocks_enabledastrue, and that the removed functionality is "permanently enabled across all networks." However, the practical consequence — thatgetblocktemplatenow throwsRPC_CLIENT_IN_INITIAL_DOWNLOADat superblock heights on regtest/testnet/devnet when the node hasn't completed masternode sync — is not called out. This is a subtle but potentially breaking change for test harnesses.💡 Suggested change
source: ['claude']