From 5137d594423f79c8b3194216054b8b753dd35d0b Mon Sep 17 00:00:00 2001 From: Murch Date: Fri, 27 Feb 2026 13:29:59 -0800 Subject: [PATCH] BIP23: Fix anchor links --- bip-0023.mediawiki | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/bip-0023.mediawiki b/bip-0023.mediawiki index 7708a135..f2bb7d10 100644 --- 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#user-content-Optional_Long_Polling|BIP 22 Long Polling]] -* [[#user-content-Basic_Pool_Extensions|BIP 23 Basic Pool Extensions]] -* [[#user-content-Mutations|BIP 23 Mutation "coinbase/append"]] -* [[#user-content-Submission_Abbreviation|BIP 23 Submission Abbreviation "submit/coinbase"]] -* [[#user-content-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: -* [[#user-content-Mutations|BIP 23 Mutation "transactions/add"]] -* [[#user-content-Block_Proposals|BIP 23 Block Proposals]] +* [[#mutations|BIP 23 Mutation "transactions/add"]] +* [[#block-proposals|BIP 23 Block Proposals]] ===Basic Pool Extensions=== @@ -87,7 +87,7 @@ This is accomplished by calling getblocktemplate with two keys: The block data MUST be validated and checked against the server's usual acceptance rules (excluding the check for a valid proof-of-work). If it is found to be in violation of any of these rules, the server MUST return one of the following: * Null if it is acceptable as-is, with the same workid (if any) as provided. Note that this SHOULD NOT invalidate the old template's claim to the same workid. -* A String giving the reason for the rejection (see [[bip-0022.mediawiki#user-content-appendix-example-rejection-reasons|example rejection reasons]]). +* A String giving the reason for the rejection (see [[bip-0022.mediawiki#appendix-example-rejection-reasons|example rejection reasons]]). * A "delta" block template (with changes needed); in this case, any missing keys are assumed to default to those in the proposed block or, if not applicable, the original block template it was based on. This template MAY also include a "reject-reason" key with a String of the reason for rejection. It is RECOMMENDED that servers which merely need to track the proposed block for later share/* submissions, return a simple Object of the form: