From: Gregory Maxwell <gmaxwell@gmail•com>
To: Peter Todd <pete@petertodd•org>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] How small blocks make delibrate orphan mining costly
Date: Sat, 23 Feb 2013 16:56:48 -0800 [thread overview]
Message-ID: <CAAS2fgSHi3Ms17JSkxirE5RkH4BEg6GP5SKLuCj6c39k0OQnhg@mail.gmail.com> (raw)
In-Reply-To: <20130224010651.GA22686@savin>
On Sat, Feb 23, 2013 at 5:06 PM, Peter Todd <pete@petertodd•org> wrote:
> In the low-subsidy future fees will be the main source of income for
> miners. Thus in some circumstances large miners may even have a reason
> to delibrately try to mine a block that would orphan the current best
> block. A simple example would be what would happen if a 1000BTC fee tx
> was created, but more realistic examples would be just due to a large
> number of tx's with decent fees.
It's come up a number of times in the past that when there is no
subsidy we might expect slow convergence as miners try to orphan each
other instead in order to fee snipe. What Peter pointed out here
that I had not previously considered and find interesting is was that
if there is a sufficient backlog (or nlocktime immature) of
transactions with fees beyond the maximum block size the incentive to
orphan blocks to take their fees is greatly reduced or eliminated.
prev parent reply other threads:[~2013-02-24 0:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-24 1:06 Peter Todd
2013-02-24 0:56 ` Gregory Maxwell [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=CAAS2fgSHi3Ms17JSkxirE5RkH4BEg6GP5SKLuCj6c39k0OQnhg@mail.gmail.com \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=pete@petertodd$(echo .)org \
/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