Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id C6387412 for ; Sat, 4 Mar 2017 08:31:55 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from zinan.dashjr.org (zinan.dashjr.org [192.3.11.21]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 50295123 for ; Sat, 4 Mar 2017 08:31:55 +0000 (UTC) Received: from ishibashi.localnet (unknown [IPv6:2001:470:5:265:a45d:823b:2d27:961c]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id D92CA38ABEA6; Sat, 4 Mar 2017 08:27:34 +0000 (UTC) X-Hashcash: 1:25:170304:bitcoin-dev@lists.linuxfoundation.org::UuDOf7TdnaF0dW29:m1/q X-Hashcash: 1:25:170304:team@bitcoinaverage.com::PjWggV/jQ6OfkJC7:Qhci X-Hashcash: 1:25:170304:contacto@bitcoinvenezuela.com::UIrRemrQgQKGhBKE:po/4 X-Hashcash: 1:25:170304:btcparalelo@yahoo.com::VR7ejiFoEa2RGbG/:brqOA X-Hashcash: 1:25:170304:info@bitso.com::F1tp2qDnJzsQxExc:YAuC X-Hashcash: 1:25:170304:kontakt@bitmarket.pl::dvh1bBJGcTDMZQd5:bp3xE X-Hashcash: 1:25:170304:support@bitpay.com::NepLSUaOfiEB/Z82:HzG9 X-Hashcash: 1:25:170304:support@bitstamp.net::8B5xC4+LB4B3G8Ts:intK8 X-Hashcash: 1:25:170304:support@btcchina.com::RtBZDXj6wdm39bmh:alFf6 X-Hashcash: 1:25:170304:support@coinbase.com::F7ZupxS7uL4ydaSC:antwu X-Hashcash: 1:25:170304:index@coindesk.com::B65Ws8dlypcBSWXM:scWy X-Hashcash: 1:25:170304:support@coinsecure.in::l=cDS=sHdvgEWQro:cGa9Z X-Hashcash: 1:25:170304:support@unocoin.com::GbwUDBhiJ0uMuXta:0Yqp X-Hashcash: 1:25:170304:info@itbit.com::k4ck=HedMVGGelM4:CuWU X-Hashcash: 1:25:170304:contact@winkdex.com::D8tbHTqTBRp6az7d:bJz=M From: Luke Dashjr To: bitcoin-dev@lists.linuxfoundation.org Date: Sat, 4 Mar 2017 08:27:32 +0000 User-Agent: KMail/1.13.7 (Linux/4.4.45-gentoo; KDE/4.14.28; x86_64; ; ) X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F X-PGP-Key-ID: BD02942421F4889F X-PGP-Keyserver: hkp://pgp.mit.edu MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201703040827.33798.luke@dashjr.org> X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Sat, 04 Mar 2017 12:12:50 +0000 Cc: support@unocoin.com, contacto@bitcoinvenezuela.com, info@itbit.com, index@coindesk.com, btcparalelo@yahoo.com, support@coinbase.com, support@bitpay.com, support@btcchina.com, team@bitcoinaverage.com, kontakt@bitmarket.pl, contact@winkdex.com, support@coinsecure.in, info@bitso.com, support@bitstamp.net Subject: [bitcoin-dev] Currency/exchange rate information API X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Mar 2017 08:31:55 -0000 Investigating what it would take to add fiat currency information to Bitcoin Knots, I noticed Electrum currently has many implementations, one for each exchange rate provider, due to lack of a common format for such data. Therefore, I put together an initial draft of a BIP that could standardise this so wallets (or other software) and exchange rate providers can simply interoperate without a lot of overhead reimplementing the same thing many ways. One thing I am unsure about, is that currently this draft requires using XBT (as BTC) for Bitcoin amounts. It would seem nicer to use satoshis, but those don't really have a pseudo-ISO currency code to fit in nicely... Current draft here: https://github.com/luke-jr/bips/blob/bip-xchgrate/bip-xchgrate.mediawiki Thoughts? Anything critical missing? Ways to make the interface better? Luke