From: Johnson Lau <jl2012@xbt.hk>
To: Peter Todd <pete@petertodd.org>,
bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Cc: shiva sitamraju <shiva@blockonomics.co>
Subject: Re: [bitcoin-dev] Testnet3 Reest
Date: Fri, 31 Aug 2018 04:44:25 +0800 [thread overview]
Message-ID: <7E247E56-38A5-4B99-941A-A2CC837D2567@xbt.hk> (raw)
In-Reply-To: <20180830200239.ujuzh7pitcuatdt3@petertodd.org>
A public testnet is still useful so in articles people could make references to these transactions.
Maybe we could have 2 testnets at the same time, with one having a smaller block size?
> On 31 Aug 2018, at 4:02 AM, Peter Todd via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
>
> Signed PGP part
> 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
>
>
next prev parent reply other threads:[~2018-08-30 20:44 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
2018-08-30 20:36 ` Jimmy Song
2018-08-30 20:44 ` Johnson Lau [this message]
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=7E247E56-38A5-4B99-941A-A2CC837D2567@xbt.hk \
--to=jl2012@xbt.hk \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=pete@petertodd.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