From: "Jorge Timón" <jtimon@jtimon•cc>
To: Luke Dashjr <luke@dashjr•org>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Alternative chain support for payment protocol
Date: Mon, 10 Aug 2015 21:44:43 +0200 [thread overview]
Message-ID: <CABm2gDpaYLM0rUZ8QDw_cFnmogsu-FZz5Z5fZOJ_ek4cQti6iw@mail.gmail.com> (raw)
In-Reply-To: <201508101841.00173.luke@dashjr.org>
On Mon, Aug 10, 2015 at 8:40 PM, Luke Dashjr via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
>> > Genesis blocks are not necessarily unique. For example, Litecoin and
>> > Feathercoin share the same one.
That's a fatal design in Feathercoin, not a mistake all altchains have
done and certainly irrelevant to Bitcoin.
> Regtest isn't really a network at all, just a testing mode of Bitcoin Core...
Regtest is a testchain just like testnet2 and testnet3. Testchains are
the only reason why Bitcoin Core supports multiple chains using
CChainParams.
> Sorry, I meant to stress that BIPs are for *Bitcoin* improvements
> specifically. Things which only improve altcoins, while a perfectly fine thing
> to standardise, are outside the scope of what belongs in a BIP.
>
> Perhaps, however, this could be made to kill 2 birds with one stone, by
> ensuring it addresses the need for payments made of bitcoins on a sidechain?
> For this, a merchant who wants a sidechain payment would presumably be able to
> provide a script from the main chain already, but an extension allowing
> payment directly on the sidechain (at the customer's choice) avoids the need
> to round-trip it...
For the payment protocol testchains, sidechains and altcoins are all
quite similar.
But it is fine to just focus on testchains if sidechains and altcoins
are out of scope.
prev parent reply other threads:[~2015-08-10 19:44 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
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 [this message]
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=CABm2gDpaYLM0rUZ8QDw_cFnmogsu-FZz5Z5fZOJ_ek4cQti6iw@mail.gmail.com \
--to=jtimon@jtimon$(echo .)cc \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=luke@dashjr$(echo .)org \
/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