Skip to content

Commit 9ee9717

Browse files
committed
Use hyperlinks when mentioning bips
When mentioning a bip we use a hyperlink to the bip file to assist readers. There are two mentions of bips in BIP-0009 that do not use links, probably because links where provided above in the text, however, its a bit easier on the reader if we provide links again to save scrolling through the document. Use hyperlinks when mentioning BIP 34 and 141 in isolation.
1 parent 6a5c99f commit 9ee9717

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

bip-0009.mediawiki

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -197,7 +197,7 @@ Miners MAY clear or set bits in the block version WITHOUT any special "mutable"
197197
Softfork deployment names listed in "rules" or as keys in "vbavailable" may be prefixed by a '!' character.
198198
Without this prefix, GBT clients may assume the rule will not impact usage of the template as-is; typical examples of this would be when previously valid transactions cease to be valid, such as BIPs [[bip-0016.mediawiki|16]], [[bip-0065.mediawiki|65]], [[bip-0066.mediawiki|66]], [[bip-0068.mediawiki|68]], [[bip-0112.mediawiki|112]], and [[bip-0113.mediawiki|113]].
199199
If a client does not understand a rule without the prefix, it may use it unmodified for mining.
200-
On the other hand, when this prefix is used, it indicates a more subtle change to the block structure or generation transaction; examples of this would be BIP 34 (because it modifies coinbase construction) and 141 (since it modifies the txid hashing and adds a commitment to the generation transaction).
200+
On the other hand, when this prefix is used, it indicates a more subtle change to the block structure or generation transaction; examples of this would be [[bip-0034.mediawiki|BIP 34]] (because it modifies coinbase construction) and [[bip-0141.mediawiki|141]] (since it modifies the txid hashing and adds a commitment to the generation transaction).
201201
A client that does not understand a rule prefixed by '!' must not attempt to process the template, and must not attempt to use it for mining even unmodified.
202202

203203
==Support for future changes==

0 commit comments

Comments
 (0)