Posted by ajtowns
Jun 2, 2026/10:25 UTC
The recent implementation in the signet miner code introduces a method for creating regular, automatic blockchain reorganizations (reorgs). This technique is set to target a daily occurrence, though the exact timing of these events is determined by a cryptographically random trigger. The operation utilizes a bash script that evaluates whether the hexadecimal conversion of a hash meets specific criteria to initiate a reorg. This script first retrieves the current best block hash, then it applies a SHA-256 hash function combined with a secret value. If the resulting value modulo 144 equals zero, the script proceeds to invalidate the specified block, thereby triggering a reorganization.
Specifically, the implemented code was successful in causing a reorganization at block 307073, which resulted in a two-block reorganization. This incident exemplifies the operational mechanics and potential outcomes of the newly implemented reorg strategy.
Furthermore, the scenario presents an intriguing puzzle regarding the expected length of reorganizations under this mechanism. Given that each reorg's timing is based on randomly mining times, with a set delay (denoted as T seconds) before mining starts after each reorg, the system’s behavior becomes a point of analysis. Additionally, the hardcoded constant $SECRET utilized within the hashing process also poses a computational challenge, inviting speculation or calculation concerning its possible value. These elements provide a rich ground for both theoretical exploration and practical application in understanding and predicting blockchain behaviors under modified conditions.
TLDR
We’ll email you summaries of the latest discussions from high signal bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.
We'd love to hear your feedback on this project.
Give Feedback