From: Gavin Andresen <gavin@bitcoinfoundation•org>
To: Jeff Garzik <jgarzik@exmulti•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] UUID to identify chains (payment protocol and elsewhere)
Date: Wed, 22 May 2013 11:59:53 -0400 [thread overview]
Message-ID: <CABsx9T3iS4m_SOvZG0FDkrMojKTjH0WxbieKGNzR49ZBi4d1BA@mail.gmail.com> (raw)
In-Reply-To: <CA+8xBpf4HLnNrxt+8mMJiiemKcrDyppzgLkmmJNr3o9o5k6sRQ@mail.gmail.com>
Getting back to the original proposal:
RE: uuid instead of "main" / "test" in the payment protocol:
I vote no.
The payment protocol will become at least 3 BIPs:
1) Protocol messages (current gist, essentially)
2) MIME type
3) bitcoin: URI extension
An alt coin will need its own version of (2) and (3), so when you
click on a foocoin: link a foocoin-specific MIME type is fetched and
foocoin.exe is launched to handle the request.
... or a specific MIME type is fetched and delivered to the
HandlesLotsOfCoins application (... and it knows what MIME type it is
getting, so can Do the Right Thing).
If a payment request is delivered via HTTP or email, it will be
bundled up in an envelope of some sort with the MIME type attached.
So, after further thought, I've changed my mind: which coin would be
encoded in the MIME type. Which chain for that coin would be encoded
in PaymentDetails.network.
--
--
Gavin Andresen
Chief Scientist, Bitcoin Foundation
https://www.bitcoinfoundation.org/
prev parent reply other threads:[~2013-05-22 16:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 23:59 Mark Friedenbach
2013-05-21 2:45 ` Jeff Garzik
2013-05-21 3:30 ` Mike Hearn
2013-05-21 4:00 ` Mark Friedenbach
2013-05-21 4:04 ` Luke-Jr
2013-05-22 10:27 ` Melvin Carvalho
2013-05-22 14:07 ` Jeff Garzik
2013-05-22 14:12 ` Melvin Carvalho
2013-05-22 14:20 ` Jeff Garzik
2013-05-22 14:29 ` Luke-Jr
2013-05-22 14:55 ` Jeff Garzik
2013-05-22 15:59 ` Gavin Andresen [this message]
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=CABsx9T3iS4m_SOvZG0FDkrMojKTjH0WxbieKGNzR49ZBi4d1BA@mail.gmail.com \
--to=gavin@bitcoinfoundation$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jgarzik@exmulti$(echo .)com \
/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