public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed

From: Danny Thorpe <danny.thorpe@gmail•com>
To: "Jorge Timón" <jtimon@jtimon•cc>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin is an experiment. Why don't we have an experimental hardfork?
Date: Wed, 19 Aug 2015 10:30:35 -0700	[thread overview]
Message-ID: <CAJN5wHWCst=SmRA-Pu7fmJwxtL9aneCx_hkdDV0Nt7-fAjr5QA@mail.gmail.com> (raw)
In-Reply-To: <CABm2gDp69g8H4Was2qzixPq3qwQ_smzzeFpE+y2GYEK6F4kUrw@mail.gmail.com>

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

>>
I would expect any uncontroversial hardfork to be deployed in testnet3
before it is deployed in bitcoin's main chain.
<<

Ok, glad to hear that.

>>
In any case, you can already do these tests using
https://github.com/bitcoin/bitcoin/pull/6382
<<

I saw your post about that awhile ago, thanks for doing the work!  My
fiddling with that end of the food chain is gated by my needing to block
out a weekend to set up a bitcoind build environment.

How do "big-block" testnet nodes running this 6382 rev recognize each other
on the peer network? If I set up a 2MB block limit testnet node and
-addnode another 2MB block testnet node (say, JornC's node) to it, and my
node mines a block stuffed with 1.3MB of test txs, the other "big-block"
node should accept my mined block, but it will be rejected / immediately
orphaned by the rest of the testnet network because it exceeds their notion
of block size limit, correct?

Thanks,
-Danny

On Wed, Aug 19, 2015 at 2:29 AM, Jorge Timón <jtimon@jtimon•cc> wrote:

> On Tue, Aug 18, 2015 at 11:06 PM, Danny Thorpe via bitcoin-dev
> <bitcoin-dev@lists•linuxfoundation.org> wrote:
> >
> > Ya, so?  All that means is that the experiment might reach the hard fork
> tipping point faster than mainnet would. Verifying that the network can
> handle such transitions, and how larger blocks affect the network, is the
> point of testing.
> >
> > And when I refer to testnet, I mean the public global testnet
> blockchain, not in-house isolated networks like testnet-in-a-box.
>
> I would expect any uncontroversial hardfork to be deployed in testnet3
> before it is deployed in bitcoin's main chain.
>
> In any case, you can already do these tests using
> https://github.com/bitcoin/bitcoin/pull/6382
> Note that even if the new testchains are regtest-like (ie cheap proof
> of work) you don't need to test them "in-a-box": you can run them from
> many different places.
> Rusty's test ( http://rusty.ozlabs.org/?p=509 ) could have been
> perfectly made using #6382, it just didn't existed at the time.
>

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

next prev parent reply	other threads:[~2015-08-19 17:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18  9:54 jl2012
2015-08-18 11:57 ` Micha Bailey
2015-08-18 18:52 ` Eric Lombrozo
2015-08-18 20:48 ` Danny Thorpe
2015-08-18 20:51   ` Eric Lombrozo
2015-08-18 21:06     ` Danny Thorpe
2015-08-18 21:17       ` Eric Lombrozo
2015-08-18 21:39         ` Danny Thorpe
2015-08-19  9:29       ` Jorge Timón
2015-08-19 10:14         ` odinn
2015-08-19 11:06           ` Jorge Timón
2015-08-19 11:25             ` odinn
2015-08-19 15:22               ` jl2012
2015-08-19 15:48                 ` Tier Nolan
2015-08-19 15:25               ` Jorge Timón
2015-08-19 17:30         ` Danny Thorpe [this message]
2015-08-19 18:33           ` Jorge Timón
2015-08-18 22:51 ` Ahmed Zsales
2015-08-19  2:53   ` Eric Lombrozo
2015-08-19  9:24 ` Jorge Timón
2015-08-19 10:34   ` jl2012
2015-08-19 10:53     ` 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='CAJN5wHWCst=SmRA-Pu7fmJwxtL9aneCx_hkdDV0Nt7-fAjr5QA@mail.gmail.com' \
    --to=danny.thorpe@gmail$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=jtimon@jtimon$(echo .)cc \
    /path/to/YOUR_REPLY

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox