bitcoin · EthanHeilman · Jan 24, 2026 · Feb 27, 2026 · Feb 27, 2026 · Feb 27, 2026
diff --git a/bip-0001.mediawiki b/bip-0001.mediawiki
@@ -36,7 +36,7 @@ BIP authors are responsible for collecting community feedback on both the initia
 
 It is highly recommended that a single BIP contain a single key proposal or new idea. The more focused the BIP, the more successful it tends to be. If in doubt, split your BIP into several well-focused ones.
 
-The BIP editors assign BIP numbers and change their status. Please send all BIP-related email to the BIP editor, which is listed under [[#BIP_Editors|BIP Editors]] below. Also see [[#BIP_Editor_Responsibilities__Workflow|BIP Editor Responsibilities & Workflow]]. The BIP editor reserves the right to reject BIP proposals if they appear too unfocused or too broad.
+The BIP editors assign BIP numbers and change their status. Please send all BIP-related email to the BIP editor, which is listed under [[#bip-editors|BIP Editors]] below. Also see [[#bip-editor-responsibilities--workflow|BIP Editor Responsibilities & Workflow]]. The BIP editor reserves the right to reject BIP proposals if they appear too unfocused or too broad.
 
 Authors MUST NOT self assign BIP numbers, but should use an alias such as "bip-johndoe-infinitebitcoins" which includes the author's name/nick and the BIP subject.
 

diff --git a/bip-0002.mediawiki b/bip-0002.mediawiki
@@ -110,11 +110,11 @@ BIPs should be written in mediawiki or markdown format.
 
 Each BIP should have the following parts:
 
-* Preamble -- Headers containing metadata about the BIP ([[#BIP header preamble|see below]]).
+* Preamble -- Headers containing metadata about the BIP ([[#bip-header-preamble|see below]]).
 
 * Abstract -- A short (~200 word) description of the technical issue being addressed.
 
-* Copyright -- The BIP must be explicitly licensed under acceptable copyright terms ([[#BIP licensing|see below]]).
+* Copyright -- The BIP must be explicitly licensed under acceptable copyright terms ([[#bip-licensing|see below]]).
 
 * Specification -- The technical specification should describe the syntax and semantics of any new feature. The specification should be detailed enough to allow competing, interoperable implementations for any of the current Bitcoin platforms.
 

diff --git a/bip-0020.mediawiki b/bip-0020.mediawiki
@@ -32,7 +32,7 @@ Graphical bitcoin clients SHOULD register themselves as the handler for the "bit
 
 === BNF grammar ===
 
-(See also [[#Simpler syntax|a simpler representation of syntax]])
+(See also [[#simpler-syntax|a simpler representation of syntax]])
 
  bitcoinurn      = "bitcoin:" bitcoinaddress [ ";version=" bitcoinversion ] [ "?" bitcoinparams ]
  bitcoinaddress  = base58 *base58
@@ -53,7 +53,7 @@ Graphical bitcoin clients SHOULD register themselves as the handler for the "bit
 *label: Label for that address (e.g. name of receiver)
 *address: bitcoin address
 *message: message that is shown to the user after scanning the QR code
-*size: amount of base bitcoin units ([[#Transfer amount/size|see below]])
+*size: amount of base bitcoin units ([[#transfer-amountsize|see below]])
 *send: used to send bitcoin, rather than to request them
 *(others): optional, for future extensions
 
@@ -95,7 +95,7 @@ Make it possible for later generations to improve our work, to mend our errors,
 === Simpler syntax ===
 
 This section is non-normative and does not cover all possible syntax.
-Please see the [[#BNF grammar|BNF grammar]] above for the normative syntax.
+Please see the [[#bnf-grammar|BNF grammar]] above for the normative syntax.
 
 [foo] means optional, &lt;bar&gt; are placeholders
 

diff --git a/bip-0021.mediawiki b/bip-0021.mediawiki
@@ -62,7 +62,7 @@ The scheme component ("bitcoin:") is case-insensitive, and implementations must
 
 *label: Label for that address (e.g. name of receiver)
 *address: bitcoin address
-*message: message that describes the transaction to the user ([[#Examples|see examples below]])
+*message: message that describes the transaction to the user ([[#examples|see examples below]])
 *(others): optional, for future extensions
 
 ==== Transfer amount ====

diff --git a/bip-0022.mediawiki b/bip-0022.mediawiki
@@ -24,15 +24,15 @@ This BIP is licensed under the BSD 2-clause license.
 
 A JSON-RPC method is defined, called "getblocktemplate".
 It accepts exactly one argument, which MUST be an Object of request parameters.
-If the request parameters include a "mode" key, that is used to explicitly select between the default "template" request or a [[bip-0023.mediawiki#Block Proposal|"proposal"]].
+If the request parameters include a "mode" key, that is used to explicitly select between the default "template" request or a [[bip-0023.mediawiki#block-proposal|"proposal"]].
 
 Block template creation can be influenced by various parameters:
 {| class="wikitable"
 !colspan=4|template request
 |-
 ! Key !! Required !! Type !! Description
 |-
-| capabilities || No || Array of Strings || SHOULD contain a list of the following, to indicate client-side support: [[#Optional: Long Polling|"longpoll"]], "coinbasetxn", "coinbasevalue", [[bip-0023.mediawiki#Block Proposal|"proposal"]], [[bip-0023.mediawiki#Logical Services|"serverlist"]], "workid", and any of the [[bip-0023.mediawiki#Mutations|mutations]]
+| capabilities || No || Array of Strings || SHOULD contain a list of the following, to indicate client-side support: [[#optional-long-polling|"longpoll"]], "coinbasetxn", "coinbasevalue", [[bip-0023.mediawiki#block-proposal|"proposal"]], [[bip-0023.mediawiki#logical-services|"serverlist"]], "workid", and any of the [[bip-0023.mediawiki#mutations|mutations]]
 |-
 | mode || No || String || MUST be "template" or omitted
 |}
@@ -55,17 +55,17 @@ getblocktemplate MUST return a JSON Object containing the following keys:
 |-
 | sizelimit || No || Number || number of bytes allowed in blocks
 |-
-| transactions || Should || Array of Objects || Objects containing [[#Transactions Object Format|information for Bitcoin transactions]] (excluding coinbase)
+| transactions || Should || Array of Objects || Objects containing [[#transactions-object-format|information for Bitcoin transactions]] (excluding coinbase)
 |-
 | version || Yes || Number || always 1 or 2 (at least for bitcoin) - clients MUST understand the implications of the version they use (eg, comply with [[bip-0034.mediawiki|BIP 0034]] for version 2)
 |-
 | coinbaseaux || No || Object || data that SHOULD be included in the coinbase's scriptSig content. Only the values (hexadecimal byte-for-byte) in this Object should be included, not the keys. This does not include the block height, which is required to be included in the scriptSig by [[bip-0034.mediawiki|BIP 0034]]. It is advisable to encode values inside "PUSH" opcodes, so as to not inadvertently expend SIGOPs (which are counted toward limits, despite not being executed).
 |-
-| coinbasetxn || this or ↓ || Object || [[#Transactions Object Format|information for coinbase transaction]]
+| coinbasetxn || this or ↓ || Object || [[#transactions-object-format|information for coinbase transaction]]
 |-
 | coinbasevalue || this or ↑ || Number || total funds available for the coinbase (in Satoshis)
 |-
-| workid || No || String || if provided, this value must be returned with results (see [[#Block Submission|Block Submission]])
+| workid || No || String || if provided, this value must be returned with results (see [[#block-submission|Block Submission]])
 |}
 
 ==== Transactions Object Format ====

diff --git a/bip-0023.mediawiki b/bip-0023.mediawiki
@@ -27,15 +27,15 @@ Something can be said to have BIP 23 Level 1 support if it implements at least:
 * [http://www.ietf.org/rfc/rfc1945.txt RFC 1945]
 * [http://json-rpc.org/wiki/specification JSON-RPC 1.0]
 * [[bip-0022.mediawiki|BIP 22 (non-optional sections)]]
-* [[bip-0022.mediawiki#Optional: Long Polling|BIP 22 Long Polling]]
-* [[#Basic Pool Extensions|BIP 23 Basic Pool Extensions]]
-* [[#Mutations|BIP 23 Mutation "coinbase/append"]]
-* [[#Submission Abbreviation|BIP 23 Submission Abbreviation "submit/coinbase"]]
-* [[#Mutations|BIP 23 Mutation "time/increment"]] (only required for servers)
+* [[bip-0022.mediawiki#optional-long-polling|BIP 22 Long Polling]]
+* [[#basic-pool-extensions|BIP 23 Basic Pool Extensions]]
+* [[#mutations|BIP 23 Mutation "coinbase/append"]]
+* [[#submission-abbreviation|BIP 23 Submission Abbreviation "submit/coinbase"]]
+* [[#mutations|BIP 23 Mutation "time/increment"]] (only required for servers)
 
 It can be said to have BIP 23 Level 2 support if it also implements:
-* [[#Mutations|BIP 23 Mutation "transactions/add"]]
-* [[#Block Proposals|BIP 23 Block Proposals]]
+* [[#mutations|BIP 23 Mutation "transactions/add"]]
+* [[#block-proposals|BIP 23 Block Proposals]]
 
 ===Basic Pool Extensions===
 

diff --git a/bip-0036.mediawiki b/bip-0036.mediawiki
@@ -24,7 +24,7 @@ Two new fields are added to the <code>version</code> command, after <code>extra_
 {|class="wikitable"
 ! Field Size !! Description !! Data type !! Comments
 |-
-| 1+ || service_count || [[Protocol_specification#Variable_length_integer|var_int]] || Number of extra services
+| 1+ || service_count || [[Protocol_specification#variable-length-integer|var_int]] || Number of extra services
 |-
 | ? || service_list || service[] || List of service definitions
 |}
@@ -34,11 +34,11 @@ The service definitions <code>service[]</code> are given in the following format
 {|class="wikitable"
 ! Field Size !! Description !! Data type !! Comments
 |-
-| ? || service_name || [[#Variable length string|var_str]] || Unique service identifier
+| ? || service_name || [[#variable-length-string|var_str]] || Unique service identifier
 |-
 | 4 || service_version || uint32_t || Identifies service version being used by the node
 |-
-| ? || service_data || [[#Variable length string|var_str]] || Additional service-specific data
+| ? || service_data || [[#variable-length-string|var_str]] || Additional service-specific data
 |}
 
 A node MUST NOT announce two services with the same <code>service_name</code>. If a remote node sends such a <code>version</code> message the client MAY disconnect.

diff --git a/bip-0046.mediawiki b/bip-0046.mediawiki
@@ -76,7 +76,7 @@ For <tt>index</tt>, addresses are numbered from 0 in a sequentially increasing m
 
 === Timelock derivation ===
 
-The timelock used in the time-locked address is derived from the <tt>index</tt>. The timelock is a unix time. It is always at the start of the first second at the beginning of the month (see [[#Test vectors|Test vectors]]). The <tt>index</tt> counts upwards the months from January 2020, ending in December 2099. At 12 months per year for 80 years this totals 960 timelocks. Note that care must be taken with the year 2038 problem on 32-bit systems.
+The timelock used in the time-locked address is derived from the <tt>index</tt>. The timelock is a unix time. It is always at the start of the first second at the beginning of the month (see [[#test-vectors|Test vectors]]). The <tt>index</tt> counts upwards the months from January 2020, ending in December 2099. At 12 months per year for 80 years this totals 960 timelocks. Note that care must be taken with the year 2038 problem on 32-bit systems.
 
 <pre>
 year = 2020 + index // 12

diff --git a/bip-0054.md b/bip-0054.md
@@ -225,7 +225,7 @@ notably of Bitcoin Core but also of all other implementations the authors are aw
 [BIP16 specs]: https://github.com/bitcoin/bips/blob/master/bip-0016.mediawiki#specification
 [SE timewarp]: https://bitcoin.stackexchange.com/questions/75831/what-is-time-warp-attack-and-how-does-it-work-in-general/75834#75834
 [Delving Murch-Zawy]: https://delvingbitcoin.org/t/zawy-s-alternating-timestamp-attack/1062#variant-on-zawys-attack-2
-[BIP94 timewarp]: https://github.com/bitcoin/bips/blob/master/bip-0094.mediawiki#user-content-Time_Warp_Fix
+[BIP94 timewarp]: https://github.com/bitcoin/bips/blob/master/bip-0094.mediawiki#time-warp-fix
 [Sjors grace period]: https://delvingbitcoin.org/t/timewarp-attack-600-second-grace-period/1326
 [grace period debate summary]: https://delvingbitcoin.org/t/great-consensus-cleanup-revival/710/66
 [O'Connor OP_CODESEPARATOR]: https://gnusha.org/pi/bitcoindev/CAMZUoKneArC+YZ36YFwxNTKsDtJhEz5P2cosXKxJS8Rf_3Nyuw@mail.gmail.com