From: Peter Todd <pete@petertodd•org>
To: grarpamp <grarpamp@gmail•com>
Cc: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Ok to use 0.8.x?
Date: Sat, 16 Mar 2013 18:17:09 -0400 [thread overview]
Message-ID: <403A5D3D-9CB1-4E35-A017-A5E0F42BFF39@petertodd.org> (raw)
In-Reply-To: <CAD2Ti28baaYbbYvNxUgb2PNz0UjURkE5ROtmdSJ8nxvp4+fFKA@mail.gmail.com>
Hardware mining rigs do not need updating - they all are designed to connect directly to a pool and it is the pool that makes all block related decisions. All the miner, or as I prefer to call them hasher, sees is an 80 byte block header and possibly with stratum and getblocktemplate enough other information like a partial merkle tree to roll the extranonce.
On 2013-03-16, at 18:04, grarpamp <grarpamp@gmail•com> wrote:
>>> Bitcoin version 0.8.0 is safe to use for everything EXCEPT creating blocks.
>>>
>>> So: safe for everybody except solo miners / pool operators.
>>
>> And even solo miners / pool operators can use it if connected to the network only through a 0.7 node.
>
> I'll go ahead and use 0.8.x since it will be just transactions and queries.
>
> I'm guessing this will all be fixed in a couple weeks and that ASIC and FPGA
> miners will have their softcode updated, as will the pure softminers (GPU).
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_mar
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
prev parent reply other threads:[~2013-03-16 22:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 2:49 grarpamp
2013-03-14 4:01 ` Gavin Andresen
2013-03-14 8:33 ` Michael Gronager
2013-03-16 22:04 ` grarpamp
2013-03-16 22:17 ` Peter Todd [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=403A5D3D-9CB1-4E35-A017-A5E0F42BFF39@petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=grarpamp@gmail$(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