From: Peter Todd <pete@petertodd.org>
To: shiva sitamraju <shiva@blockonomics.co>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Testnet3 Reest
Date: Thu, 30 Aug 2018 16:02:39 -0400 [thread overview]
Message-ID: <20180830200239.ujuzh7pitcuatdt3@petertodd.org> (raw)
In-Reply-To: <CABuOfuh7M6siJW1FzXajsBSeYSu=TBEgx9SAmCbwnP=yb7rJOQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
On Thu, Aug 30, 2018 at 12:58:42PM +0530, shiva sitamraju via bitcoin-dev wrote:
> Hi,
>
> Testnet is now 1411795 blocks and a full sync is taking atleast 48 hours.
>
> Is a testnet reset scheduled in the next release or any reason not to do a
> reset ?
>
> Fast onboarding/lower disk overheads would be very much appreicated for
> testing purposes
Actually I'd advocate the opposite: I'd want testnet to be a *larger*
blockchain than mainnet to find size-related issues first.
Note that for testing regtest is often a better alternative, and you can setup
private regtest blockchains fairly easily and with good control over exactly
when and how blocks are created.
--
https://petertodd.org 'peter'[:-1]@petertodd.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-08-30 20:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 7:28 [bitcoin-dev] Testnet3 Reest shiva sitamraju
2018-08-30 20:02 ` Peter Todd [this message]
2018-08-30 20:36 ` Jimmy Song
2018-08-30 20:44 ` Johnson Lau
2018-08-31 0:06 ` Gregory Maxwell
2018-09-01 14:47 ` rhavar
2018-09-05 3:00 ` Karl-Johan Alm
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=20180830200239.ujuzh7pitcuatdt3@petertodd.org \
--to=pete@petertodd.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=shiva@blockonomics.co \
/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