From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org
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
Date: Sat, 4 Mar 2017 08:27:32 +0000 [thread overview]
Message-ID: <201703040827.33798.luke@dashjr.org> (raw)
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
next reply other threads:[~2017-03-04 8:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 8:27 Luke Dashjr [this message]
2017-03-04 15:18 ` アルム カールヨハン
2017-03-06 5:37 ` Tim Ruffing
2017-03-06 7:09 ` Luke Dashjr
2017-03-06 8:14 ` Jonas Schnelli
2017-03-06 21:54 ` Tim Ruffing
2017-03-06 22:02 ` Tim Ruffing
2017-03-06 22:21 ` Luke Dashjr
2017-03-06 22:14 ` Luke Dashjr
2017-03-06 22:30 ` Tim Ruffing
2017-03-06 22:38 ` Tim Ruffing
2017-03-06 23:14 ` Andreas Schildbach
2017-03-07 9:29 ` Marcel Jamin
2017-03-13 18:10 ` Andrew LeCody
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201703040827.33798.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=btcparalelo@yahoo$(echo .)com \
--cc=contact@winkdex$(echo .)com \
--cc=contacto@bitcoinvenezuela$(echo .)com \
--cc=index@coindesk$(echo .)com \
--cc=info@bitso$(echo .)com \
--cc=info@itbit$(echo .)com \
--cc=kontakt@bitmarket$(echo .)pl \
--cc=support@bitpay$(echo .)com \
--cc=support@bitstamp$(echo .)net \
--cc=support@btcchina$(echo .)com \
--cc=support@coinbase$(echo .)com \
--cc=support@coinsecure$(echo .)in \
--cc=support@unocoin$(echo .)com \
--cc=team@bitcoinaverage$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox