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
98
99
100
101
102
103
104
105
106
107
108
109
|
Return-Path: <hearn@vinumeris.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 12C2CFF
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 9 Aug 2015 14:29:09 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ig0-f176.google.com (mail-ig0-f176.google.com
[209.85.213.176])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 9F0EA1A4
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 9 Aug 2015 14:29:08 +0000 (UTC)
Received: by igr7 with SMTP id 7so55940166igr.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 09 Aug 2015 07:29:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=vinumeris.com; s=google;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type;
bh=QR1DWhsQvbNUjG597yhRdVONHoa6PjJrVGKN9Sp+XQ0=;
b=m/nKmZwBkucuXiRxSC4u3G2Wr03ZJM8t4J+sKLEnj7N/juA6Gvrtgbk+ncIu5UY/V1
7AZ04+A4fppOS+D/Uwt0e47uTO88IdJCiRBq99mkCg3AOCjII/rmv51jCZXkh2IlmNkY
9fe6mL3lRObrgoGAgQP+ck2by2AMGoW/paP3E=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=QR1DWhsQvbNUjG597yhRdVONHoa6PjJrVGKN9Sp+XQ0=;
b=Uc2NUYQL4pxCkJ2H3WvyEYTr/DjC4n9cRd1N1PPtYAwQNJ4CEniQdbR2FKZQ0vRwQx
m4irCueX+W76LRbkXZXuNVcNiY/wZ++josUKlR+26c4LrbbRtAgHqVswc1fvrbqNL0jI
RyeQccwlWa2pS3AvjMnNG/ShPWQp0eJy27CRtjRAa9n5xt2SIMYtMXz74gtWBg3pgvtk
opPDgZRWuCyga3uh8QEKd1/r0FhklX85wvyjDxVeO/FZSsol1qVugt6uX7cajDBJaX28
p9nk4n7lKGSD9Patvik7Ap2mA3PsbRsmZfHIzVg/RiLrKdvjKsqcqpnWMAsIJy4j5N2K
jZ0Q==
X-Gm-Message-State: ALoCoQmgDrLYcmhOyubG6OV6PsALwQ6kx4N2oE0Ytds/8ApBJriYPuU/U4TknDUaxCkq0u7Ws8AX
MIME-Version: 1.0
X-Received: by 10.50.103.6 with SMTP id fs6mr727900igb.83.1439130547922; Sun,
09 Aug 2015 07:29:07 -0700 (PDT)
Received: by 10.50.108.111 with HTTP; Sun, 9 Aug 2015 07:29:07 -0700 (PDT)
In-Reply-To: <55C75FC8.6070807@jrn.me.uk>
References: <55C75FC8.6070807@jrn.me.uk>
Date: Sun, 9 Aug 2015 16:29:07 +0200
Message-ID: <CA+w+GKS4O176C4-oGw913xvNSXzaBPO-UpU3SrzWR2yE-gcTwQ@mail.gmail.com>
From: Mike Hearn <hearn@vinumeris.com>
To: Ross Nicoll <jrn@jrn.me.uk>
Content-Type: multipart/alternative; boundary=047d7b2e0abb184909051ce1b13b
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham
version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Alternative chain support for payment protocol
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Aug 2015 14:29:09 -0000
--047d7b2e0abb184909051ce1b13b
Content-Type: text/plain; charset=UTF-8
>
> I'd appreciate initial feedback on the idea, and if there's no major
> objections I'll raise this as a BIP.
>
The reason BIP 70 doesn't do this is the assumption that alt coins are ...
well .... alt. They can vary in arbitrary ways from Bitcoin, and so things
in BIP70 that work for Bitcoin may or may not work for other coins.
If your alt coin is close enough to BIP 70 that you can reuse it "as is"
then IMO we should just define a new network string for your alt. network =
"dogecoin-main" or whatever.
You could also use the genesis hash as the network name. That works too.
But it's less clear and would involve lookups to figure out what the
request is for, if you find such a request in the wild. I don't care much
either way.
--047d7b2e0abb184909051ce1b13b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">I'd appreciate initial feedback on the idea,=
and if there's no major objections I'll raise this as a BIP.<br></=
blockquote><div><br></div><div>The reason BIP 70 doesn't do this is the=
assumption that alt coins are ... well .... alt. They can vary in arbitrar=
y ways from Bitcoin, and so things in BIP70 that work for Bitcoin may or ma=
y not work for other coins.</div><div><br></div><div>If your alt coin is cl=
ose enough to BIP 70 that you can reuse it "as is" then IMO we sh=
ould just define a new network string for your alt. network =3D "dogec=
oin-main" or whatever.</div><div><br></div><div>You could also use the=
genesis hash as the network name. That works too. But it's less clear =
and would involve lookups to figure out what the request is for, if you fin=
d such a request in the wild. I don't care much either way.</div></div>=
</div></div>
--047d7b2e0abb184909051ce1b13b--
|
