From: Troy Benjegerdes <hozer@hozed•org>
To: Stephen Reed <stephenreed@yahoo•com>
Cc: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Proof-of-Stake branch?
Date: Fri, 25 Apr 2014 02:33:34 -0500 [thread overview]
Message-ID: <20140425073334.GV3180@nl.grid.coop> (raw)
In-Reply-To: <1398382335.20219.YahooMailNeo@web160503.mail.bf1.yahoo.com>
Do it. Someone will scream harm. The loudest voices screaming how it would
be harmful are doing the most harm.
The only way to know is build it, and test it. If the network breaks, then
it is better we find out sooner rather than later.
My only suggestion is call it 'bitstake' or something to clearly differentiate
it from Bitcoin. This also might be an interesting application of the side
chains concept Peter Todd has discussed.
On Thu, Apr 24, 2014 at 04:32:15PM -0700, Stephen Reed wrote:
> 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.
--
----------------------------------------------------------------------------
Troy Benjegerdes 'da hozer' hozer@hozed•org
7 elements earth::water::air::fire::mind::spirit::soul grid.coop
Never pick a fight with someone who buys ink by the barrel,
nor try buy a hacker who makes money by the megahash
next prev parent reply other threads:[~2014-04-25 7:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 23:32 Stephen Reed
2014-04-25 7:33 ` Troy Benjegerdes [this message]
[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=20140425073334.GV3180@nl.grid.coop \
--to=hozer@hozed$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=stephenreed@yahoo$(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