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
92
93
94
95
96
97
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1UfBSO-00075r-7L
for bitcoin-development@lists.sourceforge.net;
Wed, 22 May 2013 16:00:04 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.179 as permitted sender)
client-ip=209.85.212.179; envelope-from=gavinandresen@gmail.com;
helo=mail-wi0-f179.google.com;
Received: from mail-wi0-f179.google.com ([209.85.212.179])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UfBSN-0005Vb-50
for bitcoin-development@lists.sourceforge.net;
Wed, 22 May 2013 16:00:04 +0000
Received: by mail-wi0-f179.google.com with SMTP id hq7so1364028wib.6
for <bitcoin-development@lists.sourceforge.net>;
Wed, 22 May 2013 08:59:57 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.36.147 with SMTP id q19mr15921149wij.26.1369238393213;
Wed, 22 May 2013 08:59:53 -0700 (PDT)
Sender: gavinandresen@gmail.com
Received: by 10.194.83.7 with HTTP; Wed, 22 May 2013 08:59:53 -0700 (PDT)
In-Reply-To: <CA+8xBpf4HLnNrxt+8mMJiiemKcrDyppzgLkmmJNr3o9o5k6sRQ@mail.gmail.com>
References: <519AB8EB.5000103@monetize.io>
<CAKaEYhJ_r7ozQ3v+ggZt35b4GA3+VBkdCy2LVYKoLMGa5bFBfQ@mail.gmail.com>
<CA+8xBpc4deHT7uY+N+yx_qOEvLV3T2G7aXqHtq=nRPGd6=2O=g@mail.gmail.com>
<201305221429.49704.luke@dashjr.org>
<CA+8xBpf4HLnNrxt+8mMJiiemKcrDyppzgLkmmJNr3o9o5k6sRQ@mail.gmail.com>
Date: Wed, 22 May 2013 11:59:53 -0400
X-Google-Sender-Auth: OhHQj1pfUxHVutq5b9SuT5PEjso
Message-ID: <CABsx9T3iS4m_SOvZG0FDkrMojKTjH0WxbieKGNzR49ZBi4d1BA@mail.gmail.com>
From: Gavin Andresen <gavin@bitcoinfoundation.org>
To: Jeff Garzik <jgarzik@exmulti.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.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
(gavinandresen[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
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: 1UfBSN-0005Vb-50
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] UUID to identify chains (payment protocol
and elsewhere)
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Wed, 22 May 2013 16:00:04 -0000
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/
|
