public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <mike@plan99.net>
To: Chris Page <pagecr@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Request for comments on hybrid PoW/PoS enhancement for Bitcoin
Date: Wed, 25 Feb 2015 13:30:28 +0100	[thread overview]
Message-ID: <CANEZrP11Ru2E8TgKZsPzWwSqK+ffUbWr2XtVptW+NRR6GAYKqg@mail.gmail.com> (raw)
In-Reply-To: <CAEG8yzmS61H7uqWQuqx09T1NjiHrpK=3MYT+63AXb=_xkz831g@mail.gmail.com>

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

Hi Chris,

Just FYI you may not have received much feedback on this because Gmail put
it into the spam folder for some reason. So I'm guessing a lot of people
didn't see it.

My main feedback is - I do not really see how this is different from actual
mining. Mining also incentives the running of full nodes, miners are
rewarded via coinbases, etc. I'm missing a crisp description of why your
scheme is better than this, in particular, taking into account the
difficulty of distinguishing full node sybils of each other.

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

  parent reply	other threads:[~2015-02-25 12:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-23 19:27 [Bitcoin-development] Request for comments on hybrid PoW/PoS enhancement for Bitcoin Chris Page
2015-02-24 14:54 ` Jameson Lopp
2015-02-24 17:13   ` Chris Page
2015-02-25 12:30 ` Mike Hearn [this message]
2015-02-25 13:43   ` Chris Page
2015-02-25 21:58 [Bitcoin-development] Request for comments on hybrid, " Andrew Lapp
2015-02-26  1:21 ` Chris Page

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=CANEZrP11Ru2E8TgKZsPzWwSqK+ffUbWr2XtVptW+NRR6GAYKqg@mail.gmail.com \
    --to=mike@plan99.net \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=pagecr@gmail.com \
    /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