Assign BIP 171: Currency/exchange rate information API

2 files changed, 10 insertions, 3 deletions

diff --git a/README.mediawiki b/README.mediawiki
index 1398ca3..f5f0db3 100644
--- a/README.mediawiki
+++ b/README.mediawiki
@@ -658,6 +658,13 @@ Those proposing changes should consider that ultimately consent may rest with th
 | Matt Corallo
 | Standard
 | Draft
+|-
+| [[bip-0171.mediawiki|171]]
+| Applications
+| Currency/exchange rate information API
+| Luke Dashjr
+| Standard
+| Draft
 |}
 
 <!-- IMPORTANT!  See the instructions at the top of this page, do NOT JUST add BIPs here! -->
diff --git a/bip-xchgrate.mediawiki b/bip-0171.mediawiki
index 00a96ed..237d233 100644
--- a/bip-xchgrate.mediawiki
+++ b/bip-0171.mediawiki
@@ -1,10 +1,10 @@
 <pre>
-  BIP: ?
+  BIP: 171
   Layer: Applications
   Title: Currency/exchange rate information API
   Author: Luke Dashjr <luke+bip@dashjr.org>
   Comments-Summary: No comments yet.
-  Comments-URI: ?
+  Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0171
   Status: Draft
   Type: Standards Track
   Created: 2017-03-04
@@ -28,7 +28,7 @@ Each result is always in JSON format, with a line-feed (never a carriage-return)
 Authentication for subscription-based services MAY be supported using standard HTTP authentication.
 It is recommended to use TLS (HTTPS), so that MITM attackers cannot deceive the client.
 
-To be BIP <FIXME> compatible, servers MUST support at least one currency-pair compared to XBT.
+To be BIP 171 compatible, servers MUST support at least one currency-pair compared to XBT.
 All inquiries for bitcoin amounts MUST be specified in XBT, even if the presentation to the end user is in another unit.
 (FIXME: or should this be satoshis?)