public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Emil Engler <me@emilengler.com>
To: Peter Todd <pete@petertodd.org>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] testnet4
Date: Mon, 17 Jun 2019 13:41:08 +0200	[thread overview]
Message-ID: <733e1cd5-6511-ebea-fad4-6a5377ef9b25@emilengler.com> (raw)
In-Reply-To: <20190616202506.kjdpul473lutqhfw@petertodd.org>

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

Indeed a large testnet blockchain has advantages too.
But because it is the testnet and the testnet coins have no value, the
blockchain could be 'spammed' after a reset for some days/weeks until it
has a certain size.
Could this be realistic solution ?

Am 16.06.19 um 22:25 schrieb Peter Todd:
> On Sat, Jun 08, 2019 at 05:01:50PM +0200, Emil Engler via bitcoin-dev wrote:
>> I don't get why the testnet shouldn't be resetted just because there is a
>> (probably better) alternative for it. The testnet is still a thing and is
>> also used.
> 
> Remember that the size of testnet itself is an important test; I've argued in
> that past that we should consider making testnet *larger* than mainnet. There's
> good arguments against that too, but I personally think the current size is a
> reasonable compromise.
> 
> Of course, I personally tend to do all my testing on either internal regtest
> nodes, or directly on mainnet. But the fact that works for me is specific to
> the exact type of development I do and may not be applicable to you.
> 

-- 
https://www.emilengler.com

[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 3199 bytes --]

      reply	other threads:[~2019-06-17 11:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-07 23:49 [bitcoin-dev] testnet4 Emil Engler
2019-06-08 14:21 ` Bryan Bishop
2019-06-08 15:01   ` Emil Engler
2019-06-16 20:25     ` Peter Todd
2019-06-17 11:41       ` Emil Engler [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=733e1cd5-6511-ebea-fad4-6a5377ef9b25@emilengler.com \
    --to=me@emilengler.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=pete@petertodd.org \
    /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