From: Rhavar <rhavar@protonmail•com>
To: "David A. Harding" <dave@dtrt•org>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Transaction Merging (bip125 relaxation)
Date: Sun, 28 Jan 2018 12:58:11 -0500 [thread overview]
Message-ID: <TRUCAZT1uSDAJVGt0kSdULxKcJXcijO-HosPBaDvib9OVLmMO_2qD4YaEwEf34SCi7xBNr5dPv6IK8dYkja4oZcK0xhZWgju3P2S4SfJ4ZA=@protonmail.com> (raw)
In-Reply-To: <20180128172948.5y32cc6rvf3saolj@fedora-23-dvm>
[-- Attachment #1: Type: text/plain, Size: 2532 bytes --]
I don't think this is a realistic concern. The incentive compatibility _already_ exists (just in reverse: miners are refusing transactions that would increase their total fees in the next block), and as the mempool is already generally competitive enough it's actually worse the way it is.
But I don't think it makes sense to take a zealous approach on "incentive compatibility". Bitcoin is already built on a whole bunch of incentive incompatible behaviors, even things as simple as "change outputs" (you'd be better off privately giving your transaction to trusted miners without change, who deduct the min fee they would've needed and refund the rest OOB). Not to mention, we expect miners to avoid reorgs and stuff even if it's in their short-term interest.
At least personally, I think DoS risks are the real concern.
-Ryan
-------- Original Message --------
On January 28, 2018 12:29 PM, David A. Harding <dave@dtrt•org> wrote:
> On Sun, Jan 28, 2018 at 05:43:34PM +0100, Sjors Provoost via bitcoin-dev wrote:
>
>> Peter Todd wrote:
>>
>>> In fact I considered only requiring an increase in fee rate, based on the
>>> theory that if absolute fee went down, the transaction must be smaller and thus
>>> miners could overall earn more from the additional transactions they could fit
>>> into their block. But to do that properly requires considering whether or not
>>> that's actually true in the particular state the mempool as a whole happens to
>>> be in, so I ditched that idea early on for the much simpler criteria of both a
>>> feerate and absolute fee increase.
>>
>> Why would you need to consider the whole mempool?
>
> Imagine a miner is only concerned with creating the next block and his
> mempool currently only has 750,000 vbytes in it. If two 250-vbyte
> transactions each paying a feerate of 100 nanobitcoins per vbyte (50k
> total) are replaced with one 325-vbyte transaction paying a feerate of
> 120 nBTC (39k total), the miner's potential income from mining the next
> block is reduced by 11k nBTC.
>
> Moving away from this easily worked example, the problem can still exist
> even if a miner has enough transactions to fill the next block. For
> replacement consideration only by increased feerate to be guaranteed
> more profitable, one has to assume the mempool contains an effectively
> continuous distribution of feerates. That may one day be true of the
> mempool (it would be good, because it helps keep block production
> regular sans subsidy) but it's often not the case these days.
>
> -Dave
[-- Attachment #2: Type: text/html, Size: 3377 bytes --]
next prev parent reply other threads:[~2018-01-28 17:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 17:40 Rhavar
2018-01-22 18:16 ` Alan Evans
2018-01-22 18:18 ` Rhavar
2018-01-22 18:50 ` Moral Agent
2018-01-22 18:59 ` Rhavar
2018-01-22 20:00 ` Peter Todd
2018-01-22 20:09 ` Rhavar
2018-01-23 16:31 ` Rhavar
2018-01-23 21:56 ` Moral Agent
2018-01-23 22:19 ` Rhavar
2018-01-23 22:49 ` Gregory Maxwell
2018-01-24 7:44 ` Peter Todd
2018-01-24 13:43 ` Alan Evans
2018-01-24 16:05 ` Rhavar
2018-01-28 16:43 ` Sjors Provoost
2018-01-28 17:29 ` David A. Harding
2018-01-28 17:58 ` Rhavar [this message]
2018-01-28 18:08 ` Moral Agent
2018-01-23 21:31 ` Gregory Maxwell
2018-01-24 7:28 ` Peter Todd
2018-01-23 23:31 Adam Ficsor
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='TRUCAZT1uSDAJVGt0kSdULxKcJXcijO-HosPBaDvib9OVLmMO_2qD4YaEwEf34SCi7xBNr5dPv6IK8dYkja4oZcK0xhZWgju3P2S4SfJ4ZA=@protonmail.com' \
--to=rhavar@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=dave@dtrt$(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