1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
|
Return-Path: <david.barnes@bitcoin.co.th>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 772AFACB
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 17 Jul 2015 02:57:52 +0000 (UTC)
X-Greylist: delayed 00:31:43 by SQLgrey-1.7.6
Received: from bitcoin.co.th (support.bitcoin.co.th [162.213.249.178])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id BFF59150
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 17 Jul 2015 02:57:51 +0000 (UTC)
Received: from node-n84.pool-101-108.dynamic.totbb.net
([101.108.117.148]:19727 helo=[192.168.1.174])
by server1.advancedstyle.com with esmtpsa
(TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85)
(envelope-from <david.barnes@bitcoin.co.th>) id 1ZFvLh-0000z6-6W
for bitcoin-dev@lists.linuxfoundation.org;
Thu, 16 Jul 2015 22:26:05 -0400
Message-ID: <55A867B9.202@bitcoin.co.th>
Date: Fri, 17 Jul 2015 09:26:01 +0700
From: "David Barnes | Bitcoin Co. Ltd." <david.barnes@bitcoin.co.th>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-AntiAbuse: This header was added to track abuse,
please include it with any abuse report
X-AntiAbuse: Primary Hostname - server1.advancedstyle.com
X-AntiAbuse: Original Domain - lists.linuxfoundation.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bitcoin.co.th
X-Get-Message-Sender-Via: server1.advancedstyle.com: authenticated_id:
david.barnes@bitcoin.co.th
X-Spam-Status: No, score=-3.2 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
Subject: [bitcoin-dev] BIP0074 Draft (Dynamic Rate Lookup)
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jul 2015 02:57:52 -0000
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=
=2E
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
|
