From: Tim Menapace <tim_jannik@gmx•de>
To: bitcoin-dev@lists.linuxfoundation.org,me@emilengler•com
Subject: Re: [bitcoin-dev] bitcoin-dev Digest, Vol 49, Issue 8
Date: Sun, 09 Jun 2019 16:55:25 +0200 [thread overview]
Message-ID: <F1FD5AC3-12F0-4087-8AB6-D7DCF7799FF4@gmx.de> (raw)
In-Reply-To: <mailman.1827.1560068363.7313.bitcoin-dev@lists.linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 348 bytes --]
>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.
[-- Attachment #2: Type: text/html, Size: 371 bytes --]
next parent reply other threads:[~2019-06-09 14:55 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 ` Tim Menapace [this message]
2019-06-09 18:56 ` 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=F1FD5AC3-12F0-4087-8AB6-D7DCF7799FF4@gmx.de \
--to=tim_jannik@gmx$(echo .)de \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=me@emilengler$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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