[BIP Proposal] Stale Tip Relay

Jul 29 - Nov 16, 2026

  • The `staletip` proposal represents an important advancement in enhancing Bitcoin network transparency by allowing nodes to share information on recently observed stale tips.

Stale blocks, which arise when two valid blocks are found at the same height almost simultaneously, are often overlooked due to existing relay technologies that prioritize quick propagation of the main chain. As a result, the detection and evaluation of stale branches remain challenging, limiting insights into their origins—be it network delays, partitions, or adversarial strategies. The staletip protocol introduces an optional peer-to-peer messaging system where nodes can indicate support for this feature using BIP 434 feature messages. Messages transmitted include the fork point, a sequence of compressed headers, and a flag indicating if the sender possesses the full block data. Operational parameters restrict relayed information to tips within 1000 blocks of the active tip and limit header sequences to 20, with each node maintaining a cache of up to 10 recent stale tips. This structured approach aims to balance observability with efficiency, preventing network overload while promoting improved diagnostics and more responsive handling of reorganizations. For those interested in further technical specifics, direct references to the Draft BIP and an accompanying Proof-of-concept implementation are available.

A parallel initiative documents mainnet stale blocks through continuous monitoring of long-running nodes, compensating for the absence of mechanisms to recover these blocks directly from the network. Public contributions are encouraged via this repository, supporting research into stale block occurrences and their implications. While this documentation provides valuable data, concerns have been raised about its potential to increase the network’s exposure to Denial of Service (DoS) attacks and fingerprinting strategies. Additionally, scenarios involving multiple competing chains, especially prevalent in signet and testnets, present communication challenges since the current messaging system only supports single-branch reporting. These complexities suggest there is room for refinement to ensure the solution effectively addresses both security and functional requirements while minimizing unintended risks.

From a security perspective, the proposal has been scrutinized for possible DoS and fingerprinting vulnerabilities. Although transmitting small messages or invalid data as part of a DoS attack is not new, the proposed protocol does not introduce novel vectors for resource exhaustion or bandwidth amplification. Processing and retention limits built into the proposal minimize such risks, and nodes can apply stricter controls or disable features if necessary. Fingerprinting risk is acknowledged as an inherent trade-off in enabling staletip, typical of optional peer-to-peer capabilities; nodes may simply opt out if they deem the trade unfavorable. The protocol assumes that announcements regarding competing chains will be made distinctly, with each message describing a linear branch from a known fork point, thereby addressing much of the concern over cross-branch communication.

Adopting an incremental deployment strategy, the initial recommendation is to relay only stale headers rather than full block data. Sharing headers enhances network observability with minimal impact on the mining incentive landscape, enabling researchers and participants to detect wasted hashrate and anticipate possible reorganizations. While this approach increases transparency, it does not significantly alter miners' expected revenues nor meaningfully accelerate reorg processes. Full block relay would provide additional clarity—shedding light on double spends, censored transactions, or unique inclusions—but carries higher bandwidth overhead and could marginally delay new tip propagation for some node configurations. Thus, evaluating the effects of header-only relay before escalating to block-level data sharing ensures a measured assessment of benefits versus operational costs.

The reference implementation of staletip offers three modes: no stale relay (default), stale header relay only, and stale block relay. Debate continues over whether block relay should be enabled by default, remain optional, or be omitted. Analysis indicates that facilitating stale block relay does not substantially incentivize new mining strategies, as propagation speed improvements yield only minor expected gains and are already attainable by miners willing to invest in private relay infrastructure. Stale block relay enhances transparency by exposing alternative chains and mitigating suspicions of block withholding during reorganizations. It also enables prompt detection of issues like double-spending or censorship attempts, as demonstrated during notable real-world reorg events where public access to stale block data would have clarified misunderstandings and quelled unfounded rumors. Public discussions and social media commentary underscore the importance of timely stale block relay in providing robust evidence against allegations of malicious activity (bnoc.xyz, x.com, Stacker News), reinforcing the value of this feature for both research and operations.

While adding configuration options for relay features could be considered, their

Link to Raw Post
Bitcoin Logo

TLDR

Join Our Newsletter

We’ll email you summaries of the latest discussions from high signal bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.

Explore all Products

ChatBTC imageBitcoin searchBitcoin TranscriptsSaving SatoshiDecoding BitcoinWarnet
Built with 🧡 by the Bitcoin Dev Project
View our public visitor count

We'd love to hear your feedback on this project.

Give Feedback