From: grarpamp <grarpamp@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Ok to use 0.8.x?
Date: Sat, 16 Mar 2013 18:04:18 -0400 [thread overview]
Message-ID: <CAD2Ti28baaYbbYvNxUgb2PNz0UjURkE5ROtmdSJ8nxvp4+fFKA@mail.gmail.com> (raw)
In-Reply-To: <17182C57-07C5-4E35-9F04-DC2B8C96A8EB@ceptacle.com>
>> 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).
next prev parent reply other threads:[~2013-03-16 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 2:49 [Bitcoin-development] Ok to use 0.8.x? grarpamp
2013-03-14 4:01 ` Gavin Andresen
2013-03-14 8:33 ` Michael Gronager
2013-03-16 22:04 ` grarpamp [this message]
2013-03-16 22:17 ` Peter Todd
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=CAD2Ti28baaYbbYvNxUgb2PNz0UjURkE5ROtmdSJ8nxvp4+fFKA@mail.gmail.com \
--to=grarpamp@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
/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