From d9e890a8f27e46806238e298a346397871fd7e87 Mon Sep 17 00:00:00 2001
From: Peter Todd <pete@petertodd.org>
Date: Mon, 21 Oct 2013 02:18:47 -0400
Subject: Fix formatting

---
 bip-0023.mediawiki | 12 ++++--------
 1 file changed, 4 insertions(+), 8 deletions(-)

(limited to 'bip-0023.mediawiki')

diff --git a/bip-0023.mediawiki b/bip-0023.mediawiki
index 90bb3d7..4cdaa31 100644
--- a/bip-0023.mediawiki
+++ b/bip-0023.mediawiki
@@ -1,5 +1,3 @@
-{{bip}}
-
 <pre>
   BIP: 23
   Title: getblocktemplate - Pooled Mining
@@ -22,8 +20,8 @@ Note that all sections of this specification are optional extensions on top of [
 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|BIP 22 (non-optional sections)]]
-* [[BIP 0022#Optional: Long Polling|BIP 22 Long Polling]]
+* [[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"]]
@@ -83,7 +81,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#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:
@@ -295,6 +293,4 @@ What is the purpose of the "hash" transaction list format?
 * [https://github.com/bitcoin/bitcoin/pull/936/files bitcoind]
 
 ==See Also==
-* [[BIP 0022|BIP 22: getblocktemplate - Fundamentals]]
-
-[[Category:BIP|D]]
+* [[bip-0022.mediawiki|BIP 22: getblocktemplate - Fundamentals]]
-- 
cgit v1.2.3

