From: Mike Hearn <mike@plan99•net>
To: Mike Belshe <mike@belshe•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Testnet under attack?
Date: Fri, 15 Nov 2013 21:02:06 +0100 [thread overview]
Message-ID: <CANEZrP1_vkosrRpouzRqZRFo8z0iNXzR14F1GU=yWZ66gZUtNw@mail.gmail.com> (raw)
In-Reply-To: <CABaLYCufS4pW644S9q63YfZNECtRW5jhJRw3-vozNz1=N50oHQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]
I don't use testnet much anymore, partly because it sometimes kind of
breaks like this. It's a public resource and people sometimes abuse it.
You can create your own local network with -regtest and that lets you mint
new blocks instantly. It's a much simpler way to do testing and app
development.
On Fri, Nov 15, 2013 at 8:34 PM, Mike Belshe <mike@belshe•com> wrote:
> It appears that someone is minting new blocks literally every couple of
> seconds on the testnet chain right now.
>
> You can see it on both blockexplorer:
> http://blockexplorer.com/testnet
>
> and also btclook:
> http://testnet.btclook.com/
>
> Is this something we should worry about?
>
> thanks,
> Mike
>
>
>
> ------------------------------------------------------------------------------
> DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
> OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
> Free app hosting. Or install the open source package on any LAMP server.
> Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
> http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
[-- Attachment #2: Type: text/html, Size: 2262 bytes --]
prev parent reply other threads:[~2013-11-15 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 19:34 Mike Belshe
2013-11-15 20:02 ` Mike Hearn [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='CANEZrP1_vkosrRpouzRqZRFo8z0iNXzR14F1GU=yWZ66gZUtNw@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@belshe$(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