Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YQgzJ-00082o-8W for bitcoin-development@lists.sourceforge.net; Wed, 25 Feb 2015 18:47:13 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.213.171 as permitted sender) client-ip=209.85.213.171; envelope-from=gmaxwell@gmail.com; helo=mail-ig0-f171.google.com; Received: from mail-ig0-f171.google.com ([209.85.213.171]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YQgzI-0000z7-6H for bitcoin-development@lists.sourceforge.net; Wed, 25 Feb 2015 18:47:13 +0000 Received: by mail-ig0-f171.google.com with SMTP id h15so38004609igd.4 for ; Wed, 25 Feb 2015 10:47:07 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.50.66.170 with SMTP id g10mr28921187igt.49.1424890026869; Wed, 25 Feb 2015 10:47:06 -0800 (PST) Received: by 10.107.16.80 with HTTP; Wed, 25 Feb 2015 10:47:06 -0800 (PST) Date: Wed, 25 Feb 2015 18:47:06 +0000 Message-ID: From: Gregory Maxwell To: Bitcoin Development 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 (gmaxwell[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: 1YQgzI-0000z7-6H Subject: [Bitcoin-development] BCF 2012 Miner vote X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Feb 2015 18:47:13 -0000 It would appear that the Bitcoin Foundation has decided that their next two seats would be decided by miners. (More information available at: https://bitcoinfoundation.org/forum/index.php?/topic/1255-blockchain-voting/#entry13453 ) Unfortunately, they seem to have not provided the software needed to participate. I've taken Luke DashJr's somewhat notorious IsNotorious patch, which he's used previously to block things like the Horse Stapler Battery dust-spam attacks and re-purposed it so miners can avoid casting votes in the election that they don't intend to cast. Not really an ideal fit, but the code has the benefit of having been run in production for some time; a necessity for deployment on short notice. A patch (against git master, but should apply to 0.10 cleanly at least and probably other versions) is available at: https://people.xiph.org/~greg/bcf2012.patch Let me know if you have any trouble applying it, I'll be glad to do my civic duty and do what I can to help people participate with the system was clearly intended by the design. [Please note that I am relying on some claims from reddit for some of the candidate addresses ( http://www.reddit.com/r/Bitcoin/comments/2x3ffk/bitcoin_foundation_runoff_voting_live_stats_2015/ ) because the official voting software is more or less completely busted for me and I can only see some of the candidates. If any are wrong, please let me know.] Cheers.