public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Emil Engler <me@emilengler.com>
To: Bryan Bishop <kanzure@gmail.com>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] testnet4
Date: Sat, 8 Jun 2019 17:01:50 +0200	[thread overview]
Message-ID: <cbe4190d-ee49-b6f0-de99-c526fabff6ab@emilengler.com> (raw)
In-Reply-To: <CABaSBawPvOoTwQYQ0ZQc20b3g9GMp_fdz7cogHW25o40iF2UeA@mail.gmail.com>

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.

Am 08.06.19 um 16:21 schrieb Bryan Bishop:
> Be greeted Emil,
> 
> On Sat, Jun 8, 2019 at 9:21 AM Emil Engler via bitcoin-dev 
> <bitcoin-dev@lists.linuxfoundation.org 
> <mailto:bitcoin-dev@lists.linuxfoundation.org>> wrote:
> 
>     Hello, I tried myself with some Bitcoin development. For this I used of
>     course the Bitcoin testnet. However it took me one hour to sync the
>     blockchain with around 1538358 blocks. In my opinion that is too much
>     for a testnet. Especially the blockchain size with around 26GB is so
>     much. Would it be possible to reset the testnet with a new genesis
>     block
>     ? And if so, can we setup a fixed cycle for resetting the testnet (For
>     example every second 1st of January) ?
> 
> 
> At the moment, I somewhat doubt this is likely to happen. Signet 
> provides an alternative for configuring multiple separate private and 
> public testing networks. If you would like to get involved, check out 
> the recent discussion on the topic recorded here:
> http://diyhpl.us/wiki/transcripts/bitcoin-core-dev-tech/2019-06-07-signet/
> 
> - Bryan
> http://heybryan.org/


  reply	other threads:[~2019-06-08 15:01 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 [this message]
2019-06-16 20:25     ` Peter Todd
2019-06-17 11:41       ` Emil Engler

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=cbe4190d-ee49-b6f0-de99-c526fabff6ab@emilengler.com \
    --to=me@emilengler.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=kanzure@gmail.com \
    /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