public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Pieter Wuille <pieter.wuille@gmail.com>
To: xor <xor@freenetproject.org>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] "Subsidy fraud" ?
Date: Wed, 9 Dec 2015 22:43:22 +0100	[thread overview]
Message-ID: <CAPg+sBiLmduEM-r_2T713XC1W-R4-Pj85LHo6n14CGYPjeKirA@mail.gmail.com> (raw)
In-Reply-To: <2770009.yIOdKLpzfC@1337h4x0r>

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

I meant a miner claiming more in the coinbase's output than subsidy + fees
allow.
On Dec 10, 2015 5:26 AM, "xor" <xor@freenetproject.org> wrote:

> Pieter Wuille mentions "subsidy fraud" in his recent talk:
> https://youtu.be/fst1IK_mrng?t=57m2s
>
> I was unable to google what this is, and the Bitcoin Wiki also does not
> seem
> to explain it.
>
> If this is a well-known problem, perhaps it would be a good idea to
> explain it
> somewhere?

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

      reply	other threads:[~2015-12-09 21:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09 21:26 [bitcoin-dev] "Subsidy fraud" ? xor
2015-12-09 21:43 ` Pieter Wuille [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=CAPg+sBiLmduEM-r_2T713XC1W-R4-Pj85LHo6n14CGYPjeKirA@mail.gmail.com \
    --to=pieter.wuille@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=xor@freenetproject.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