public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "David Barnes | Bitcoin Co. Ltd." <david.barnes@bitcoin.co.th>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] BIP0074 Draft (Dynamic Rate Lookup)
Date: Fri, 17 Jul 2015 09:26:01 +0700	[thread overview]
Message-ID: <55A867B9.202@bitcoin.co.th> (raw)

Please take a look at my BIP0074 draft proposal (this is my first one so
may be incorrectly formatted)
https://github.com/bitcoincoltd/bips/blob/master/bip-0074.mediawiki

This proposal will make it possible for a simpler form of Bitcoin
payment at physical shop locations.

Currently when making a Bitcoin payment at a shop the merchant needs to
have an app of some kind so that they can calculate the amount of
bitcoins you need to pay them to cover your purchase (of for example:
$9.99).

The problem is that many employees are not properly trained on the
Bitcoin app, or the owner is the one with the app and he is often not
there.  When visiting "Bitcoin Accepting" estabishments you will often
run into this problem.  The businesses often don't get enough Bitcoin
business to warrant training sessions or dedicate hardware to run the app.

A simpler way to accept payments would be for the merchant to have a
fixed QR code, and no app at all.  However a printed QR code can't
calculate any exchange rates, and so it would be up to the customer to
choose how much to pay.

This can be result in some problems as the customer may be using their
default wallet exchange rates, or their preferred international
exchange. While the merchant may be actually using a local exchange or
service to exchange the coins to local currency, and there may be some
discrepancy between what the customer thinks the rate should be and what
the merchant thinks the rate should be.

Enter BIP0074, so that the merchant can specify which exchange rates
they are using, and the customer and then look up the rates from this
source and pay according to these rates.

David Barnes



             reply	other threads:[~2015-07-17  2:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-17  2:26 David Barnes | Bitcoin Co. Ltd. [this message]
     [not found] ` <CADu7o8OAicbtXwkxbsN=joirurBKt2ta-XwMYY622pUjR+drZQ@mail.gmail.com>
2015-07-17  3:30   ` [bitcoin-dev] BIP0074 Draft (Dynamic Rate Lookup) David Barnes | Bitcoin Co. Ltd.
     [not found] ` <CAAmoQf113y=Xd9R+b5yS=d9yo5SAX8+Nrv3gQt-R7Jih0UBOBg@mail.gmail.com>
2015-07-17  8:50   ` David Barnes | Bitcoin Co. Ltd.
2015-07-17 12:24     ` Matt Whitlock
2015-07-17 12:40       ` David Barnes | Bitcoin Co. Ltd.
     [not found]     ` <CAHv+tb5B=i9FeCX-NXkTpRE_j8hwam_aWupEA_3xtBH8366sww@mail.gmail.com>
2015-07-17 15:47       ` David Barnes | Bitcoin Co. Ltd.

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=55A867B9.202@bitcoin.co.th \
    --to=david.barnes@bitcoin.co.th \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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