Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <grarpamp@gmail.com>) id 1UGzDF-0003sg-28 for bitcoin-development@lists.sourceforge.net; Sat, 16 Mar 2013 22:04:25 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.220.174 as permitted sender) client-ip=209.85.220.174; envelope-from=grarpamp@gmail.com; helo=mail-vc0-f174.google.com; Received: from mail-vc0-f174.google.com ([209.85.220.174]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1UGzDE-0000Kd-CJ for bitcoin-development@lists.sourceforge.net; Sat, 16 Mar 2013 22:04:25 +0000 Received: by mail-vc0-f174.google.com with SMTP id hx10so2065497vcb.19 for <bitcoin-development@lists.sourceforge.net>; Sat, 16 Mar 2013 15:04:18 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.220.153.143 with SMTP id k15mr12953286vcw.33.1363471458843; Sat, 16 Mar 2013 15:04:18 -0700 (PDT) Received: by 10.220.115.7 with HTTP; Sat, 16 Mar 2013 15:04:18 -0700 (PDT) In-Reply-To: <17182C57-07C5-4E35-9F04-DC2B8C96A8EB@ceptacle.com> References: <CAD2Ti28XnZFDLMm+B1cxb5b+adjwk5M-DrFRs7C+VE=SLZ0hNQ@mail.gmail.com> <CABsx9T0VMuCwtw=LR_N4PyVPKGzAJfE3K7NzzLK719w87aqQ5g@mail.gmail.com> <17182C57-07C5-4E35-9F04-DC2B8C96A8EB@ceptacle.com> Date: Sat, 16 Mar 2013 18:04:18 -0400 Message-ID: <CAD2Ti28baaYbbYvNxUgb2PNz0UjURkE5ROtmdSJ8nxvp4+fFKA@mail.gmail.com> From: grarpamp <grarpamp@gmail.com> To: bitcoin-development@lists.sourceforge.net Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (grarpamp[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1UGzDE-0000Kd-CJ Subject: Re: [Bitcoin-development] Ok to use 0.8.x? X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: <bitcoin-development.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> List-Post: <mailto:bitcoin-development@lists.sourceforge.net> List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Sat, 16 Mar 2013 22:04:25 -0000 >> 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).