Where does the 33.33% threshold for selfish mining come from?

Posted by zawy

Jul 2, 2025/17:18 UTC

In the realm of blockchain and digital ledger technologies, the integrity and synchronization of node operation are paramount. A crucial aspect of maintaining this integrity is the handling of timestamps within the transmitted blocks. Nodes presenting timestamps significantly ahead of their arrival time cannot be considered as operating correctly. Such discrepancies necessitate a stringent response, including the potential for permanent rejection unless it is proven that the receiving node's clock was inaccurately set. This measure ensures that only nodes adhering to the network's time constraints continue to participate actively in the ledger's maintenance.

Similarly, issues arise with timestamps that are far behind the current network time. While initial reactions might lean towards immediate dismissal of such data, considerations must be made for genuine delays in data propagation. In cases where delays can be substantiated, a timeout period may be instituted to accommodate verification before deciding on the appropriateness of the block's inclusion in the chain. This approach balances the need for timely data with the realities of network transmission times.

The process of Proof of Work (PoW) plays a vital role in resolving disputes over which blockchain partition accurately reflects the majority of computational effort, otherwise known as hashrate. When faced with conflicting data, especially concerning timestamps, PoW mechanisms can identify the chain segment supported by the most significant mining effort. However, the adoption of new blocks based on their timestamp's validity can introduce complexities in scenarios where network partitions or delays are genuine. The decision to switch to a new partition, despite having encountered blocks with problematic timestamps, requires careful consideration of whether the delay was an intentional manipulation tactic or a result of genuine network issues.

Furthermore, the strategy of withholding blocks—a technique known as selfish mining—exploits the timing of block release to gain an unfair advantage in mining efforts. This behavior underscores the need for robust mechanisms to discern and mitigate instances where miners may attempt to leverage future-dated timestamps for personal gain. Despite these challenges, the overarching goal remains to ensure the blockchain operates seamlessly across all nodes, maintaining both its integrity and the trust of its participants.

Link to Raw Post
Bitcoin Logo

TLDR

Join Our Newsletter

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

Explore all Products

ChatBTC imageBitcoin searchBitcoin TranscriptsSaving SatoshiBitcoin Transcripts Review
Built with 🧡 by the Bitcoin Dev Project
View our public visitor count

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

Give Feedback