From: Ross Nicoll <jrn@jrn•me.uk>
To: Mike Hearn <hearn@vinumeris•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Alternative chain support for payment protocol
Date: Sun, 9 Aug 2015 17:23:28 +0100 [thread overview]
Message-ID: <55C77E80.3060203@jrn.me.uk> (raw)
In-Reply-To: <CA+w+GKS4O176C4-oGw913xvNSXzaBPO-UpU3SrzWR2yE-gcTwQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1401 bytes --]
I'm cautious of using human-meaningful identifiers, especially any that
might require a central repository, due to name collisions. Examples
that could be complicated include BitcoinDark, Litedoge, and other names
that base on existing coins. I think the ability to differentiate
between test networks is also useful.
Could certainly just use the genesis hash as network ID, that would
work. Bit long, but suspect 64 bytes isn't the end of the world! I'll
see if any more responses come in then raise a BIP for using genesis
hash as an alternative to short names.
Ross
On 09/08/2015 15:29, Mike Hearn wrote:
>
> 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.
[-- Attachment #2: Type: text/html, Size: 2418 bytes --]
next prev parent reply other threads:[~2015-08-09 16:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-09 14:12 Ross Nicoll
2015-08-09 14:29 ` Mike Hearn
2015-08-09 16:23 ` Ross Nicoll [this message]
[not found] ` <CADv+LCxF5MoSFcCiqXnXXsfE5KvJmL0RQ4pOhmM-5eb2TH-ncg@mail.gmail.com>
2015-08-09 18:42 ` John L. Jegutanis
2015-08-10 12:45 ` Jorge Timón
2015-08-10 12:53 ` Mike Hearn
2015-08-10 13:06 ` Jorge Timón
2015-08-10 15:38 ` odinn
2015-08-09 16:02 ` Mark Friedenbach
[not found] ` <201508092346.20301.luke@dashjr.org>
[not found] ` <55C8EE2A.3030309@jrn.me.uk>
2015-08-10 18:40 ` Luke Dashjr
2015-08-10 19:19 ` Ross Nicoll
2015-08-10 19:49 ` Jorge Timón
2015-08-10 19:44 ` Jorge Timón
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=55C77E80.3060203@jrn.me.uk \
--to=jrn@jrn$(echo .)me.uk \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=hearn@vinumeris$(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