You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merge #7278: feat: remove SPORK_3_INSTANTSEND_BLOCK_FILTERING and SPORK_9_SUPERBLOCKS_ENABLED
18b990b refactor: move superblock sync check inside !IsTestChain() guard (UdjinM6)
b2cde07 test, doc: address review suggestions for spork removal (UdjinM6)
3d9e80e refactor: cleanup unused members, includes and forward declaration after sporks removal (Konstantin Akimov)
ee90879 doc: add release notes for SPORK_3/SPORK_9 removal (UdjinM6)
afcf3d1 spork: remove SPORK_3_INSTANTSEND_BLOCK_FILTERING and SPORK_9_SUPERBLOCKS_ENABLED (UdjinM6)
Pull request description:
## Issue being fixed or feature implemented
Both sporks have been effectively permanent fixtures of the network and their gating logic is no longer needed.
## What was done?
Drop the enum entries, spork definitions, the `AreSuperblocksEnabled()` helper, and all associated branches in governance, InstantSend, masternode payments and mining RPC. `getblocktemplate` now always reports `superblocks_enabled` as `true`.
Functional tests are updated to stop toggling the removed sporks; `feature_multikeysporks.py` now uses `SPORK_19_CHAINLOCKS_ENABLED` as its second spork under test.
## How Has This Been Tested?
Run tests
## Breaking Changes
n/a
## Checklist:
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have added or updated relevant unit/integration/functional/e2e tests
- [ ] I have made corresponding changes to the documentation
- [ ] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
ACKs for top commit:
PastaPastaPasta:
utACK 18b990b
Tree-SHA512: 2b84b1473ef1b81418fd29a0d14039ed98cda0cb7608bbf6798db62c72e76e11685ed1092cc5768c5ea95e6558b6909454fd6f5a3e2b46eb42a691294573e397
0 commit comments