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-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WzSIz-0008LA-Sx for bitcoin-development@lists.sourceforge.net; Tue, 24 Jun 2014 15:06:41 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.219.47 as permitted sender) client-ip=209.85.219.47; envelope-from=mh.in.england@gmail.com; helo=mail-oa0-f47.google.com; Received: from mail-oa0-f47.google.com ([209.85.219.47]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WzSIy-0002jm-51 for bitcoin-development@lists.sourceforge.net; Tue, 24 Jun 2014 15:06:41 +0000 Received: by mail-oa0-f47.google.com with SMTP id n16so485374oag.34 for ; Tue, 24 Jun 2014 08:06:34 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.60.52.77 with SMTP id r13mr1447710oeo.55.1403622394580; Tue, 24 Jun 2014 08:06:34 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.35.234 with HTTP; Tue, 24 Jun 2014 08:06:34 -0700 (PDT) In-Reply-To: References: Date: Tue, 24 Jun 2014 17:06:34 +0200 X-Google-Sender-Auth: OWKZAxlkN6Grt5vL2gBZINhpv2c Message-ID: From: Mike Hearn To: slush Content-Type: multipart/alternative; boundary=001a11330d023a55be04fc964e73 X-Spam-Score: -0.5 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1WzSIy-0002jm-51 Cc: Bitcoin Dev 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:06:42 -0000 --001a11330d023a55be04fc964e73 Content-Type: text/plain; charset=UTF-8 > > Sounds like marketing bullshit to me. It does not have even statistical > meaning; well, you can "save" a lot of satoshis, but nobody tell you that > the merchant cut you on BTC/USD exchange rate in tens of %. > Your own wallet can look up the exchange rate and compare it to what you're getting (and in fact, wallets do!). Besides, assuming the customer is *always* being scammed seems extreme. There are plenty of merchants that genuinely care about their reputation and genuinely want people to pay with Bitcoin so they can avoid card fees. > Payment protocol should not contain these fictional data > Well, I think the protocol should contain whatever is useful. I'll probably draft a BIP for this next week or so. --001a11330d023a55be04fc964e73 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Sounds like marketing bullshit = to me. It does not have even statistical meaning; well, you can "save&= quot; a lot of satoshis, but nobody tell you that the merchant cut you on B= TC/USD exchange rate in tens of %.

Your own wallet can look up the exchange r= ate and compare it to what you're getting (and in fact, wallets do!).

Besides, assuming the customer is always=C2= =A0being scammed seems extreme. There are plenty of merchants that genuinel= y care about their reputation and genuinely want people to pay with Bitcoin= so they can avoid card fees.
=C2=A0
Payme= nt protocol should not contain these fictional data

Well, I think the protocol should contain whatever is useful.

I'll probably draft a BIP for this next week or = so.
--001a11330d023a55be04fc964e73--