From: Stephen Reed <stephenreed@yahoo•com>
To: Jeffrey Paul <sneak@acidhou•se>, Troy Benjegerdes <hozer@hozed•org>
Cc: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Proof-of-Stake branch?
Date: Fri, 25 Apr 2014 03:35:00 -0700 (PDT) [thread overview]
Message-ID: <1398422100.68438.YahooMailNeo@web160505.mail.bf1.yahoo.com> (raw)
In-Reply-To: <D95AE4AB-DC67-4136-901A-D8F712EB7357@acidhou.se>
My understanding is that sidechains require merged mining support and that sidechains create no coinbase transactions themselves. When Bitcoin Core supports the two-way peg then I would update my source code branch to incorporate that or any other change that is released. Ideally, when sidechains can work with PoW Bitcoin, then those same sidechains should work without any changes with PoS Bitcoin running in my testnet.
I will be examining PPC, NXT and whitepapers for ideas that I can implement in such a way as the result can be called Bitcoin. The only difference would be the absence of wasteful Proof-of-Work, and the presence of mining rewards distributed to full nodes in proportion to the amount of bitcoin each is willing to expose to the network. Coin age is a good starting point. A reference peer-to-peer pool developed by me would be responsible for fairly distributing the mining rewards as daily dividend payments to PoS full node pool members.
In a few days, I plan to establish a Proof-of-Stake Bitcoin project thread in the Project Development sub-forum of Bitcointalk. We can continue the technical discussion there, starting with a list of principles.
Stephen L. Reed
Austin, Texas, USA
512.791.7860
On Friday, April 25, 2014 4:42 AM, Jeffrey Paul <sneak@acidhou•se> wrote:
Are proof of stake blockchains compatible with the sidechain/two-way peg system invented by Greg (and maybe others - reports unclear)?
>
>http://letstalkbitcoin.com/blockchain-2-0-let-a-thousand-chains-blossom/
>
>It's my limited understanding that any sidechains in such a model are somewhat cryptographically tied to the PoW system that bitcoin's chain uses. I am seriously curious if alternate decentralized consensus algorithms (proof of execution, proof of stake, et c) are compatible with the sidechain universe as envisioned.
>
>Perhaps someone with a deeper technical understanding could explain how, if so, or if my incomplete hunch (that alternate consensus algorithms cannot retain compatibility with Bitcoin in a two way peg model) is correct.
>
>These sorts of "alternate universe" altcoin experiments with different proof models take on a different cost/benefit ratio if they can't ever interoperate as sidechains, which is why I'm curious.
>
>Best,
>-jp
>
>--
>Jeffrey Paul +1 (312) 361-0355
>5539 AD00 DE4C 42F3 AFE1 1575 0524 43F4 DF2A 55C2
>
>
>> On 25.04.2014, at 00:33, Troy Benjegerdes <hozer@hozed•org> wrote:
>>
>> This also might be an interesting application of the side
>> chains concept Peter Todd has discussed.
>
>
next prev parent reply other threads:[~2014-04-25 10:35 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
[not found] ` <D95AE4AB-DC67-4136-901A-D8F712EB7357@acidhou.se>
2014-04-25 10:35 ` Stephen Reed [this message]
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=1398422100.68438.YahooMailNeo@web160505.mail.bf1.yahoo.com \
--to=stephenreed@yahoo$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=hozer@hozed$(echo .)org \
--cc=sneak@acidhou$(echo .)se \
/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