BIP 332 adds an optional staletip P2P message for announcing recent stale chain tips to peers that negotiated it via BIP 434.
Full branch: https://github.com/pseudoramdom/bitcoin/tree/bip332-staletip-relay Discussion: https://groups.google.com/g/bitcoindev/c/AwOPNxF15mU
Plan
Implementation
- PR 1 - Local tracking and RPC
- Validation notification, report cached stale tips in RPC.
- No P2P change
- PR 2 - Headers-mode relay
staletipmessage, BIP 434 negotiation.- Relays headers only, enough to observe stale rates.
- PR 3 - Stale-branch blocks
- Serve available blocks on tracked stale branches
-staletips=blocksadditionally downloads them, as best-effort requests.
- Fuzz tests
- Release note and
doc/bips.mdentry - Update the reference implementation link in the BIP
Live tests
- Regtest simulation - https://github.com/pseudoramdom/staletip-lab
- Mainnet
- Signet
- Testnet5 - https://github.com/pseudoramdom/bitcoin/tree/bip332-staletip-relay-testnet5
Open questions
- Does relaying stale block data affect mining incentives? See the mailing list discussion