From: Gregory Maxwell <gmaxwell@gmail•com>
To: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] BCF 2012 Miner vote
Date: Wed, 25 Feb 2015 18:47:06 +0000 [thread overview]
Message-ID: <CAAS2fgQOvaOT=CZD-=9Rc-A2WbPygV=Jf9jCwjgZ1oB4oqavhA@mail.gmail.com> (raw)
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.
reply other threads:[~2015-02-25 18:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAAS2fgQOvaOT=CZD-=9Rc-A2WbPygV=Jf9jCwjgZ1oB4oqavhA@mail.gmail.com' \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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