public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd.org>
To: alicexbt <alicexbt@protonmail.com>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>,
	alicexbt via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>,
	Aaradhya Chauhan <chauhanansh.me@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Regarding setting a lower minrelaytxfee
Date: Tue, 26 Jul 2022 16:27:56 +0200	[thread overview]
Message-ID: <8CD1F5D4-9260-4BE7-B710-993955AB58C8@petertodd.org> (raw)
In-Reply-To: <Ue6CCWgdkGc1VPF4yAP252kg3h-6U6xCZZ7hs9w6vDM7LBWsAaksRkLIpkrE39HLmI35Fu3cHC3-WA8Q9Ij3Z7YhAqzJbkytBqU9ZbfruB0=@protonmail.com>



On July 26, 2022 2:19:32 PM GMT+02:00, alicexbt via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
>Hi Aaradhya,
>
>> As it's not a consensus rule, I think it can be done easily, just needing support from full node operators
>
>A few miners will need to use a lower minrelaytxfee for this to work. I don't think miners would want to lower their profits.

Whether or not this lowers profits for a particular miner is complex:

https://petertodd.org/2016/block-publication-incentives-for-miners

But to a first approximation, at any fee above zero failing to mine a tx you know about is leaving money on the table.

Anyway even if miners don't actually mine these txs by themselves, with Child-Pays-For-Parent, allowing near-zero txs into your mempool potentially allows you to mine more fees.


  reply	other threads:[~2022-07-26 14:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26  8:26 [bitcoin-dev] Regarding setting a lower minrelaytxfee Aaradhya Chauhan
2022-07-26 12:19 ` alicexbt
2022-07-26 14:27   ` Peter Todd [this message]
2022-07-26 19:14     ` alicexbt
2022-07-26 12:45 ` Peter Todd
2022-07-27  4:10   ` vjudeu
2022-07-27 11:50     ` Peter Todd
2022-07-27 12:18       ` vjudeu
2022-07-29  3:38   ` David A. Harding
2022-07-29 18:59     ` Aaradhya Chauhan
2022-07-30  7:55     ` Aaradhya Chauhan
2022-07-30 17:24       ` alicexbt
2022-08-01 10:30         ` Peter Todd
2022-08-01 13:19           ` aliashraf.btc At protonmail
2022-08-01 13:37             ` Peter Todd
2022-08-03 15:40               ` Aaradhya Chauhan
2022-08-03 17:07                 ` vjudeu
2022-08-03 18:22                   ` Aaradhya Chauhan
2022-08-04  1:21                     ` Billy Tetrud
2022-07-30 10:20     ` Peter Todd

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=8CD1F5D4-9260-4BE7-B710-993955AB58C8@petertodd.org \
    --to=pete@petertodd.org \
    --cc=alicexbt@protonmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=chauhanansh.me@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