Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WdT7v-0004U8-9x for bitcoin-development@lists.sourceforge.net; Thu, 24 Apr 2014 23:32:23 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of yahoo.com designates 216.109.115.141 as permitted sender) client-ip=216.109.115.141; envelope-from=stephenreed@yahoo.com; helo=nm47-vm6.bullet.mail.bf1.yahoo.com; Received: from nm47-vm6.bullet.mail.bf1.yahoo.com ([216.109.115.141]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1WdT7t-0008OZ-HR for bitcoin-development@lists.sourceforge.net; Thu, 24 Apr 2014 23:32:23 +0000 Received: from [98.139.215.140] by nm47.bullet.mail.bf1.yahoo.com with NNFMP; 24 Apr 2014 23:32:16 -0000 Received: from [98.139.212.209] by tm11.bullet.mail.bf1.yahoo.com with NNFMP; 24 Apr 2014 23:32:16 -0000 Received: from [127.0.0.1] by omp1018.mail.bf1.yahoo.com with NNFMP; 24 Apr 2014 23:32:15 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 991789.54486.bm@omp1018.mail.bf1.yahoo.com Received: (qmail 28232 invoked by uid 60001); 24 Apr 2014 23:32:15 -0000 X-YMail-OSG: p0..E9gVM1lc8PPTJlCpiaNjFJIBi2xzR0lTpbtHy3NlCWK 9Me5e1sEmpPrvLAZ0iCZUqQTFMBJOF6N_6npscybCiG5JfJPTlJuRP0eJBU5 yq_QqCi26wwJOwet_ZrGuuIZvKtkTTe2DivZveKxcR8G5Qemd2RXMGgWpjFq HGYmOmsvWOm3i8vljTPN3e0EXCKmgXtVuhRFSpZVah1TL3HV1NHB.rQA9cei NQBf4E6vzEfQYVpJpGTNlrPwFFPz5aGOht3k34DvYfzE2oXoQd0Zei4sianU KLbbIyy8H5rusUt4r_ZxBD0EllktVd3OGLDacavH9vc2.gWZXJMSVuxEhj5L s3XlwUk6EPrfyOuVm6Z7U2ozzAhdm18HwUPOlGU4wd5cgs.Xa_kFXqKAflCu 9e1.lp4._a5f3Er7TUKFUV9XioaqOjwerEIGZz9FDrX7e03GaNmpKyQFNoJP OC9sBQjhKuQbfWht3NUlc30Ni4LChhSPnFLNC0L9lsSgADyCZ.rek8VaoiCl BurlPFs3wu2lo.7g.Br9SGdd0UIvL.nfhwcJrkb4HvHrDqmEVUSTRlAPA0vW Oi8mS0l0_kYVBQDx96m62F0vVhBmJAcMO28T8g8fLS_ciNtJ8jIG6YsSpJgg 8grDeeYt1C8F5Wmd.jeiPZRzq2dWypqcBlhjQQTFx.OI- Received: from [76.250.116.214] by web160503.mail.bf1.yahoo.com via HTTP; Thu, 24 Apr 2014 16:32:15 PDT X-Rocket-MIMEInfo: 002.001, SGVsbG8gYWxsLgoKSSB1bmRlcnN0YW5kIHRoYXQgUHJvb2Ytb2YtU3Rha2UgYXMgYSByZXBsYWNlbWVudCBmb3IgUHJvb2Ytb2YtV29yayBpcyBhIHByb2hpYml0ZWQgeWV0IGRpc3B1dGVkIGNoYW5nZSB0byBCaXRjb2luIENvcmUuIEkgd291bGQgbGlrZSB0byBjcmVhdGUgYSBCaXRjb2luIGJyYW5jaCB0aGF0IHByb3ZpZGVzIGEgc2FuZGJveGVkIHRlc3RiZWQgZm9yIHJlc2VhcmNoaW5nIHRoZSBiZXN0IFBvUyBpbXBsZW1lbnRhdGlvbnMuIEluIHRoZSB5ZWFycyB0byBjb21lLCBwZXJoYXBzIGNpcmN1bXMBMAEBAQE- X-Mailer: YahooMailWebService/0.8.185.657 References: Message-ID: <1398382335.20219.YahooMailNeo@web160503.mail.bf1.yahoo.com> Date: Thu, 24 Apr 2014 16:32:15 -0700 (PDT) From: Stephen Reed To: "bitcoin-development@lists.sourceforge.net" MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -2.3 (--) 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 (stephenreed[at]yahoo.com) -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [216.109.115.141 listed in list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record -0.7 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -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: 1WdT7t-0008OZ-HR Subject: [Bitcoin-development] Proof-of-Stake branch? X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list Reply-To: Stephen Reed List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Apr 2014 23:32:23 -0000 Hello all.=0A=0AI 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 researchin= g 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.=0A-----=0A=0AA poll I= conducted today on bitcointalk,=A0https://bitcointalk.org/index.php?topic= =3D581635.0=A0with an attention-grabbing title suggests some minority suppo= rt for Bitcoin Proof-of-Stake. I invite any of you to critically comment on= that thread.=0A=0A"Annual 10% bitcoin dividends can be ours if Proof-of-S= take full nodes outnumber existing Proof-of-Work full nodes by three-to-one= . What is your choice?"=0A=0A"I do not care or do not know enough." - 5 (16= .1%)=A0=0A"I would download and run the existing Proof-of-Work program to f= ight the change." - 14 (45.2%)=A0=0A"I would download and run the new Proof= -of-Stake program to favor the change. " - 12 (38.7%)=A0=0ATotal Voters: 31= =0A-----=0A=0ABefore 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.=0A=0AThanks for t= aking a bit of your time to read this message.=0A=0A-Steve=0A=0AStephen L. = Reed=0A=0AAustin, Texas, USA=0A512.791.7860=A0