Skip to content

Commit 56e9094

Browse files
committed
bip-325: document signet minimum difficulty
This was implicit in the genesis block's nbits value, but better to be clearer.
1 parent 6ce21f4 commit 56e9094

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

bip-0325.mediawiki

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -75,6 +75,15 @@ A block is considered fully validated only if the to_sign transaction is a valid
7575

7676
There is one other acceptable special case: if a block's challenge is e.g. `OP_TRUE` (`0x51`), where an empty solution would result in success, the block is also considered valid if the signet commitment is absent.
7777

78+
=== Minimum Difficulty ===
79+
80+
The minimum difficulty for blocks in signet is approximately
81+
0.0011265, corresponding to a maximum target of
82+
<code>00000377ae000000000000000000000000000000000000000000000000000000</code>
83+
which is represented by an nBits value of <code>0x1e0377ae</code>.
84+
85+
This value is chosen so that multiplying the maximum target by maximum retarget timespan (8 weeks measured in seconds) does not overflow a uint256, making it easier to do difficulty adjustment calculations.
86+
7887
== Genesis Block and Message Start ==
7988

8089
The genesis block is the same for all signet networks, whereas the message start is defined as the first four bytes of the sha256d of the challenge script as a single data push (see below).

0 commit comments

Comments
 (0)