From: Stephen Reed <stephenreed@yahoo•com>
To: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Proof-of-Stake branch?
Date: Thu, 24 Apr 2014 16:32:15 -0700 (PDT) [thread overview]
Message-ID: <1398382335.20219.YahooMailNeo@web160503.mail.bf1.yahoo.com> (raw)
Hello all.
I understand that Proof-of-Stake as a replacement for Proof-of-Work is a prohibited yet disputed change to Bitcoin Core. I would like to create a Bitcoin branch that provides a sandboxed testbed for researching the best PoS implementations. In the years to come, perhaps circumstances might arise, such as shifting of user opinion as to whether PoS should be moved from the prohibited list to the hard-fork list.
-----
A poll I conducted today on bitcointalk, https://bitcointalk.org/index.php?topic=581635.0 with an attention-grabbing title suggests some minority support for Bitcoin Proof-of-Stake. I invite any of you to critically comment on that thread.
"Annual 10% bitcoin dividends can be ours if Proof-of-Stake full nodes outnumber existing Proof-of-Work full nodes by three-to-one. What is your choice?"
"I do not care or do not know enough." - 5 (16.1%)
"I would download and run the existing Proof-of-Work program to fight the change." - 14 (45.2%)
"I would download and run the new Proof-of-Stake program to favor the change. " - 12 (38.7%)
Total Voters: 31
-----
Before I branch the source code and learn the proper way of doing things in this community, I ask you simply if creating the branch is harmful? My goal is to develop, test and document PoS, while exploring its vulnerabilities and fixing them in a transparent fashion.
Thanks for taking a bit of your time to read this message.
-Steve
Stephen L. Reed
Austin, Texas, USA
512.791.7860
next reply other threads:[~2014-04-24 23:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 23:32 Stephen Reed [this message]
2014-04-25 7:33 ` Troy Benjegerdes
[not found] ` <D95AE4AB-DC67-4136-901A-D8F712EB7357@acidhou.se>
2014-04-25 10:35 ` Stephen Reed
2014-04-26 18:18 ` Mike Hearn
2014-04-26 20:39 ` Mark Friedenbach
2014-04-26 23:44 ` Gareth Williams
2014-04-27 1:22 ` Mark Friedenbach
2014-04-27 2:01 ` Gareth Williams
2014-04-28 12:03 ` Alex Mizrahi
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=1398382335.20219.YahooMailNeo@web160503.mail.bf1.yahoo.com \
--to=stephenreed@yahoo$(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