📅 Original date posted:2015-08-19 📝 Original message:>> I would expect any ...

Danny Thorpe [ARCHIVE] /

npub1q5s…ps87

2023-06-07 17:36:44

in reply to nevent1q…yjsl

📅 Original date posted:2015-08-19
📝 Original message:>>
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 at jtimon.cc> wrote:

> On Tue, Aug 18, 2015 at 11:06 PM, Danny Thorpe via bitcoin-dev
> <bitcoin-dev at 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.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150819/dabc7a84/attachment.html>;

Author Public Key

npub1q5sgcakfxhw3ya93tvnpqeacvf32p6lw70hke53rkjnf9lhw9w8s43ps87

Show more details

Published at

2023-06-07 17:36:44

Kind type

1 Short Text Note

Event JSON

{ "id": "96f3e04f1d12af27711ffcab5a58d65eab2480b5f58b1fab6131c15db5788d2b", "pubkey": "05208c76c935dd1274b15b261067b86262a0ebeef3ef6cd223b4a692feee2b8f", "created_at": 1686159404, "kind": 1, "tags": [ [ "e", "015c5ac0a5b1780b314fc0de46b00e614fb9247d46dfb61637d3d94fa76f544c", "", "root" ], [ "e", "cd49f633f3efbde6023c17a30cc6390c4a2b2d01e49e843eb0642609ef3a077b", "", "reply" ], [ "p", "498a711971f8a0194289aee037a4c481a99e731b5151724064973cc0e0b27c84" ] ], "content": "📅 Original date posted:2015-08-19\n📝 Original message:\u003e\u003e\nI would expect any uncontroversial hardfork to be deployed in testnet3\nbefore it is deployed in bitcoin's main chain.\n\u003c\u003c\n\nOk, glad to hear that.\n\n\u003e\u003e\nIn any case, you can already do these tests using\nhttps://github.com/bitcoin/bitcoin/pull/6382\n\u003c\u003c\n\nI saw your post about that awhile ago, thanks for doing the work! My\nfiddling with that end of the food chain is gated by my needing to block\nout a weekend to set up a bitcoind build environment.\n\nHow do \"big-block\" testnet nodes running this 6382 rev recognize each other\non the peer network? If I set up a 2MB block limit testnet node and\n-addnode another 2MB block testnet node (say, JornC's node) to it, and my\nnode mines a block stuffed with 1.3MB of test txs, the other \"big-block\"\nnode should accept my mined block, but it will be rejected / immediately\norphaned by the rest of the testnet network because it exceeds their notion\nof block size limit, correct?\n\nThanks,\n-Danny\n\nOn Wed, Aug 19, 2015 at 2:29 AM, Jorge Timón \u003cjtimon at jtimon.cc\u003e wrote:\n\n\u003e On Tue, Aug 18, 2015 at 11:06 PM, Danny Thorpe via bitcoin-dev\n\u003e \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e \u003e\n\u003e \u003e Ya, so? All that means is that the experiment might reach the hard fork\n\u003e tipping point faster than mainnet would. Verifying that the network can\n\u003e handle such transitions, and how larger blocks affect the network, is the\n\u003e point of testing.\n\u003e \u003e\n\u003e \u003e And when I refer to testnet, I mean the public global testnet\n\u003e blockchain, not in-house isolated networks like testnet-in-a-box.\n\u003e\n\u003e I would expect any uncontroversial hardfork to be deployed in testnet3\n\u003e before it is deployed in bitcoin's main chain.\n\u003e\n\u003e In any case, you can already do these tests using\n\u003e https://github.com/bitcoin/bitcoin/pull/6382\n\u003e Note that even if the new testchains are regtest-like (ie cheap proof\n\u003e of work) you don't need to test them \"in-a-box\": you can run them from\n\u003e many different places.\n\u003e Rusty's test ( http://rusty.ozlabs.org/?p=509 ) could have been\n\u003e perfectly made using #6382, it just didn't existed at the time.\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150819/dabc7a84/attachment.html\u003e", "sig": "33f49c32c5bbb145ee23823244a40c631eb803933016b6f008c4b334a7dc05d6bdf7f2b84202206ed4cbbbaad3c4f54bc7b21b384fc93fbe821dea53d99fa691" }