MIME-Version: 1.0
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
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Alternative chain support for payment protocol
Precedence: list

--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&#39;d appreciate initial feedback on the idea,=
 and if there&#39;s no major objections I&#39;ll raise this as a BIP.<br></=
blockquote><div><br></div><div>The reason BIP 70 doesn&#39;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 &quot;as is&quot; then IMO we sh=
ould just define a new network string for your alt. network =3D &quot;dogec=
oin-main&quot; or whatever.</div><div><br></div><div>You could also use the=
 genesis hash as the network name. That works too. But it&#39;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&#39;t care much either way.</div></div>=
</div></div>

--047d7b2e0abb184909051ce1b13b--