From: "Jorge Timón" <jtimon@jtimon•cc>
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: Mon, 10 Aug 2015 15:06:51 +0200 [thread overview]
Message-ID: <CABm2gDr1=ezS_BdCe8YZVwhC6U31aVP7nTHrieD3ELnD+=h5WA@mail.gmail.com> (raw)
In-Reply-To: <CA+w+GKTMAi7xXo9r6PZ=N2UQ5A8zPRUw4=FsYwOV3wFn+ND3Fg@mail.gmail.com>
On Mon, Aug 10, 2015 at 2:53 PM, Mike Hearn <hearn@vinumeris•com> wrote:
> We're not modifying BIP 70, it's now immutable and can only be extended.
Well, yes, I guess it's modifying that in the extension BIP.
> There's really not much point in having a dedicated chain ID for regtest
> mode. You shouldn't be finding BIP70 requests for regtest outside of your
> own developer machine, where the id doesn't matter.
The point is not having exceptions and treating all supported chains
in the same way in the code.
Having a special case for regtest makes the code more complex, not simpler.
next prev parent reply other threads:[~2015-08-10 13:07 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
[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 [this message]
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='CABm2gDr1=ezS_BdCe8YZVwhC6U31aVP7nTHrieD3ELnD+=h5WA@mail.gmail.com' \
--to=jtimon@jtimon$(echo .)cc \
--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