From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WzStL-0000gL-TD for bitcoin-development@lists.sourceforge.net; Tue, 24 Jun 2014 15:44:15 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of m.gmane.org designates 80.91.229.3 as permitted sender) client-ip=80.91.229.3; envelope-from=gcbd-bitcoin-development@m.gmane.org; helo=plane.gmane.org; Received: from plane.gmane.org ([80.91.229.3]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1WzStI-0004De-8f for bitcoin-development@lists.sourceforge.net; Tue, 24 Jun 2014 15:44:15 +0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WzSt8-0001Gb-PF for bitcoin-development@lists.sourceforge.net; Tue, 24 Jun 2014 17:44:02 +0200 Received: from f052086168.adsl.alicedsl.de ([78.52.86.168]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 24 Jun 2014 17:44:02 +0200 Received: from andreas by f052086168.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 24 Jun 2014 17:44:02 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: bitcoin-development@lists.sourceforge.net From: Andreas Schildbach Date: Tue, 24 Jun 2014 17:43:51 +0200 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: f052086168.adsl.alicedsl.de User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 In-Reply-To: X-Enigmail-Version: 1.5.2 X-Spam-Score: -0.4 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [80.91.229.3 listed in list.dnswl.org] -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_HELO_PASS SPF: HELO matches SPF record 1.1 DKIM_ADSP_ALL No valid author signature, domain signs all mail -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -0.0 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1WzStI-0004De-8f Subject: Re: [Bitcoin-development] Proposed BIP 70 extension X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2014 15:44:16 -0000 I think it should be made more clear what's the reference price for the discount. In Germany, we generally don't use credit cards but rather "EC-Cards", which is already much cheaper. Or maybe for some merchants the only alternative is cash, and they would still offer a Bitcoin discount. Also, currently PR are created by the payment processors afaik. How can they know what other payment option the merchant provides and what's the conditions? Maybe we should first solve the signature delegation problem so that the merchant can create the request. Although I'm sure this feature will get abused, I (as a wallet author) would be willing to give it a try. I agree with Jeff that the name of the field should start with something like "marketing". On 06/24/2014 03:27 PM, Mike Hearn wrote: > Coinbase have started allowing merchants to set discounts for purchasing > with Bitcoin. Seeing an individual discount is not very motivating as > they tend to be small. Seeing them stack up over time can be more > motivating because it feels like free money. Many businesses exploit > this effect with loyalty points, etc. Bitcoin should do this too - show > the user how much they're saving by using Bitcoin instead of credit cards. > > I suggested to Charlie Lee (who pushed this through at Coinbase) and > Stephen Pair the following minor BIP 70 extension: > > > message PaymentDetails { > // Size in satoshis of any discount provided by the merchant ONLY > // because the user chose to pay using Bitcoin or other similar > // digital currency. Other kinds of discounts, loyalty bonuses and > // so on should not be recorded here, rather they could be mentioned > // in the memo field. This field exists so wallets can show the user > // a running total of how much money they have saved by avoiding > // credit cards and bank payments; the goal is to encourage people to > // use Bitcoin. Putting other kinds of discounts here would make the > // running total calculated meaningless; so don't do it! > optional uint64 currency_usage_discount_size = 8; > } > > Wallets would then be able to persist this data to disk and compete on > cool visualisations for how much money you saved over time. > > We haven't formalised how to extend BIP 70 yet, that's my fault. We > should do that. In the meantime, what do people think of this proposal? > > > ------------------------------------------------------------------------------ > Open source business process management suite built on Java and Eclipse > Turn processes into business applications with Bonita BPM Community Edition > Quickly connect people, data, and systems into organized workflows > Winner of BOSSIE, CODIE, OW2 and Gartner awards > http://p.sf.net/sfu/Bonitasoft > > > > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development >