public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mark Friedenbach <mark@friedenbach.org>
To: Ross Nicoll <jrn@jrn.me.uk>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Alternative chain support for payment protocol
Date: Sun, 9 Aug 2015 09:02:40 -0700	[thread overview]
Message-ID: <CAOG=w-vG=gTR1Ejfhy0buFUHhZZ72wghagNWq_Z8F5smt-ScMA@mail.gmail.com> (raw)
In-Reply-To: <55C75FC8.6070807@jrn.me.uk>

[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]

A sha256 hash is 32 bytes, but otherwise I agree with this proposal.
Genesis block hash is the logical way to identify chains, moving forward.
On Aug 9, 2015 7:12 AM, "Ross Nicoll via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> BIP 70 currently lists two networks, main and test (inferred as testnet3)
> for payment protocol requests. This means that different testnets cannot be
> supported trivially, and the protocol cannot be used for alternative coins
> (or, lacks context to indicate which coin the request applies to, which is
> particularly dangerous in cases where coins share address prefixes).
>
> I propose adding a new optional "genesis" field as a 16 byte sequence
> containing the SHA-256 hash of the genesis block of the network the request
> belongs to, uniquely identifying chains without any requirement for a
> central registry. For backwards compatibility, the "network" field would
> contain "main" for Bitcoin main net, "test" for Bitcoin testnet3, and
> "other" for other networks apart from those two.
>
> I'd appreciate initial feedback on the idea, and if there's no major
> objections I'll raise this as a BIP.
>
> Ross
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

[-- Attachment #2: Type: text/html, Size: 1880 bytes --]

  parent reply	other threads:[~2015-08-09 16:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-09 14:12 [bitcoin-dev] Alternative chain support for payment protocol Ross Nicoll
2015-08-09 14:29 ` Mike Hearn
2015-08-09 16:23   ` Ross Nicoll
     [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 [this message]
     [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='CAOG=w-vG=gTR1Ejfhy0buFUHhZZ72wghagNWq_Z8F5smt-ScMA@mail.gmail.com' \
    --to=mark@friedenbach.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=jrn@jrn.me.uk \
    /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