public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Btc Drak <btcdrak@gmail.com>
To: Danny Thorpe <danny.thorpe@gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] RFC - BIP: URI scheme for Blockchain exploration
Date: Tue, 1 Sep 2015 23:59:36 +0100	[thread overview]
Message-ID: <CADJgMzuK6YpLyFQ1BnHuWi4GyoqOgnuaA7T3odukpB=Hh3pTgQ@mail.gmail.com> (raw)
In-Reply-To: <CAJN5wHVdneuRv6Vpf4q3d=mqwu2HkNeJwFhoqPHFiQcatt4RSg@mail.gmail.com>

On Tue, Sep 1, 2015 at 5:12 PM, Danny Thorpe via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> Rather than using an inhumanly long hex string from the genesis hash to
> distinguish between mainnet and testnet, why not use the network magic bytes
> instead? Much shorter, just as distinct.

There's nothing stopping two coins having the same magic bytes, but
communicating on separate ports.

> I'd still prefer a common network name mapping for the sake of humanity. Few
> bitcoin library implementations use the same string names for mainnet and
> testnet. This BIP could simply define one string name alias for each
> supported network and leave mapping to local lingo to the implementors.

The only sane way to me see to have cointype like BIP44.
See https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki#coin-type


  reply	other threads:[~2015-09-01 22:59 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-29 11:48 [bitcoin-dev] RFC - BIP: URI scheme for Blockchain exploration Marco Pontello
2015-08-29 16:31 ` Richard Moore
2015-08-29 17:19   ` Matt Whitlock
2015-08-29 19:24     ` Richard Moore
2015-08-29 18:07   ` Andreas Schildbach
2015-09-01 14:33     ` Marco Pontello
2015-08-29 18:58   ` Btc Drak
2015-08-29 19:01     ` Matt Whitlock
2015-08-29 20:10       ` Jorge Timón
2015-08-30  2:02         ` Chun Wang
2015-08-30  2:20           ` Jorge Timón
2015-09-01 22:56             ` Btc Drak
2015-09-01 14:49         ` Marco Pontello
2015-09-01 21:16           ` Matt Whitlock
2015-09-01 21:25             ` Esteban Ordano
2015-09-01 21:38             ` Marco Pontello
2015-09-01 21:42               ` Matt Whitlock
2015-09-01 21:43                 ` Marco Pontello
2015-09-01 22:46             ` Jorge Timón
2015-09-01 23:25               ` Matt Whitlock
2015-09-01 16:12         ` Danny Thorpe
2015-09-01 22:59           ` Btc Drak [this message]
2015-09-01 23:57             ` Jorge Timón
2015-08-29 19:28     ` Richard Moore
2015-09-01 14:51       ` Marco Pontello
2015-11-15  2:14 ` Marco Pontello
2015-11-15 11:42   ` Jorge Timón
2015-11-16  0:59     ` Marco Pontello
2015-11-16 14:43       ` Jorge Timón
2015-11-16 22:10         ` Marco Pontello
2015-11-18 11:29           ` Jorge Timón
2015-11-18 12:31             ` Marco Pontello

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='CADJgMzuK6YpLyFQ1BnHuWi4GyoqOgnuaA7T3odukpB=Hh3pTgQ@mail.gmail.com' \
    --to=btcdrak@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=danny.thorpe@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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