From: Mike Hearn <mike@plan99•net>
To: slush <slush@centrum•cz>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Proposed BIP 70 extension
Date: Tue, 24 Jun 2014 17:06:34 +0200 [thread overview]
Message-ID: <CANEZrP0YV4xcK7y+H=gTmv_Hxs3nuACqEHWLUfcDdQeRhBF2Hw@mail.gmail.com> (raw)
In-Reply-To: <CAJna-HhX8HOci0KMe4ZScr4QW792S3n5twvU0QhbQe1N_3q7_w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 729 bytes --]
>
> 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.
[-- Attachment #2: Type: text/html, Size: 1218 bytes --]
next prev parent reply other threads:[~2014-06-24 15:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 13:27 Mike Hearn
2014-06-24 14:21 ` Jeff Garzik
2014-06-24 14:24 ` Mike Hearn
2014-06-24 14:32 ` slush
2014-06-24 15:06 ` Mike Hearn [this message]
2014-06-24 15:15 ` Gmail
2014-06-24 15:48 ` Jeff Garzik
2014-06-24 19:00 ` Gmail
2014-06-24 19:34 ` Andy Alness
2014-06-24 20:12 ` Gavin Andresen
2014-06-24 20:28 ` Gmail
2014-06-25 8:25 ` Mike Hearn
2014-06-25 13:33 ` Jorge Timón
2014-06-25 18:10 ` Jeff Garzik
2014-06-25 14:15 ` slush
2014-06-25 16:03 ` Gmail
2014-06-24 18:34 ` Roy Badami
2014-06-24 15:43 ` Andreas Schildbach
2014-06-24 15:59 ` Mike Hearn
2014-06-24 17:37 ` Drak
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='CANEZrP0YV4xcK7y+H=gTmv_Hxs3nuACqEHWLUfcDdQeRhBF2Hw@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=slush@centrum$(echo .)cz \
/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