public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Sriram Karra <karra.etc@gmail.com>
To: bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Data / Evidence regd "penalties" for not validating blocks (Was: Why Satoshi's temporary anti-spam measure isn't temporary)
Date: Thu, 30 Jul 2015 11:58:22 +0530	[thread overview]
Message-ID: <CAFkt3UN9iEMnBhTP3J=wM2cu5M0-4hxyOG72GANJpGO9hJS-yA@mail.gmail.com> (raw)

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

On Wed, Jul 29, 2015 at 10:23 PM, Gregory Maxwell via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

On Wed, Jul 29, 2015 at 9:59 AM, Mike Hearn via bitcoin-dev
>
>
> > Miners who don't validate have a habit of bleeding money:   that's the
> > system working as designed.
>
> The information I have currently is that the parties engaging in that
> activity found it to be tremendously profitable, even including losses
> from issues.


This got buried in another thread. Putting it out in case anyone has any
insight.

Does anyone have any data on which of the above two viewpoints is actually
correct? Measuring / publishing these effects will go a long way in either
(a) establishing credibility of the 'system design' or (b) trigger a
conversation on what needs fixing.

If there is no such known data, and someone new to Bitcoin would like to do
that, where would be a good place to start, if it is at all possible.

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

                 reply	other threads:[~2015-07-30  6:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAFkt3UN9iEMnBhTP3J=wM2cu5M0-4hxyOG72GANJpGO9hJS-yA@mail.gmail.com' \
    --to=karra.etc@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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