From: Emil Engler <me@emilengler.com>
To: Tim Menapace <tim_jannik@gmx.de>, bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] bitcoin-dev Digest, Vol 49, Issue 8
Date: Sun, 9 Jun 2019 20:56:47 +0200 [thread overview]
Message-ID: <d56dfe90-4977-def6-e35b-81bbbdb5c1da@emilengler.com> (raw)
In-Reply-To: <F1FD5AC3-12F0-4087-8AB6-D7DCF7799FF4@gmx.de>
But using the testnet means that you actually need to deal with resets.
There were 2 resets in the past but the last was in 2011.
Am 09.06.19 um 16:55 schrieb Tim Menapace:
> >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.
>
> Like Bryan said, lot of miners test here. E.g. new firmware versions,
> hardware prototypes and operation services. Difficulty will be on
> current levels in a short period of time.
prev parent reply other threads:[~2019-06-09 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1827.1560068363.7313.bitcoin-dev@lists.linuxfoundation.org>
2019-06-09 14:55 ` [bitcoin-dev] bitcoin-dev Digest, Vol 49, Issue 8 Tim Menapace
2019-06-09 18:56 ` 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=d56dfe90-4977-def6-e35b-81bbbdb5c1da@emilengler.com \
--to=me@emilengler.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=tim_jannik@gmx.de \
/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