From: "Luke-Jr" <luke@dashjr•org>
To: Jeff Garzik <jgarzik@exmulti•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Upcoming network event: block v2 lock-in
Date: Sat, 23 Mar 2013 17:43:57 +0000 [thread overview]
Message-ID: <201303231743.59510.luke@dashjr.org> (raw)
In-Reply-To: <CA+8xBpc9n4_CDYTq80+u3V=sD+F-tTnc1NMVnK1Z_UnNix75dg@mail.gmail.com>
On Saturday, March 23, 2013 5:28:55 PM Jeff Garzik wrote:
> On Sat, Mar 23, 2013 at 1:09 PM, Luke-Jr <luke@dashjr•org> wrote:
> > I don't think anyone is mining using bitcoind 0.7 or later?
>
> slush, BTC Guild, ozcoin too I think, several others.
Not for producing coinbases (where BIP 34 is implemented).
next prev parent reply other threads:[~2013-03-23 17:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-23 16:16 Jeff Garzik
2013-03-23 17:09 ` Luke-Jr
2013-03-23 17:28 ` Jeff Garzik
2013-03-23 17:43 ` Luke-Jr [this message]
2013-03-23 17:47 ` Jeff Garzik
2013-03-23 17:51 ` Luke-Jr
2013-03-23 18:21 ` Jeff Garzik
2013-03-23 18:27 ` Luke-Jr
2013-03-23 19:18 ` Gregory Maxwell
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=201303231743.59510.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jgarzik@exmulti$(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