public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Alex Mizrahi <alex.mizrahi@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proof-of-Stake branch?
Date: Mon, 28 Apr 2014 15:03:54 +0300	[thread overview]
Message-ID: <CAE28kUQ8C=fCrR5DG08xmJAqEuMwgeT98sM-rrv8RiQdGkp7Mg@mail.gmail.com> (raw)
In-Reply-To: <bf916afe-6617-43c9-9738-486316ce308f@email.android.com>

[-- Attachment #1: Type: text/plain, Size: 665 bytes --]

>
> I can't remember who I saw discussing this idea. Might have been Vitalik
> Buterin?
>

Yes, he described it in an article a couple of months ago:

http://blog.ethereum.org/2014/01/15/slasher-a-punitive-proof-of-stake-algorithm/

but it is an old idea.
For example, I've mentioned punishment of this kind in discussion about
PPCoin when it was released in 2012, and, I think, it was described in
Etlase2's Decrit design.

Also, I and Iddo did some research on pure proof-of-stake, and it seems to
be feasible, in the sense that there are no obvious problems like "nothing
is actually at stake". (Unfortunately I can't refer to it now as it isn't
published yet.)

[-- Attachment #2: Type: text/html, Size: 1245 bytes --]

      parent reply	other threads:[~2014-04-28 12:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24 23:32 [Bitcoin-development] Proof-of-Stake branch? 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
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 [this message]

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='CAE28kUQ8C=fCrR5DG08xmJAqEuMwgeT98sM-rrv8RiQdGkp7Mg@mail.gmail.com' \
    --to=alex.mizrahi@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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