public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd•org>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Announcement: Full-RBF Miner Bounty
Date: Tue, 8 Nov 2022 13:16:13 -0500	[thread overview]
Message-ID: <Y2qc7Ubc5xtJhxGw@petertodd.org> (raw)
In-Reply-To: <Y2I3w8O5X55sD/3C@petertodd.org>

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

On Wed, Nov 02, 2022 at 05:26:27AM -0400, Peter Todd via bitcoin-dev wrote:
> I'm now running a full-RBf bounty program for miners.
> 
> tl;dr: I'm broadcasting full-RBF replacements paying extremely high fees to
> reward miners that turn on full-RBF. I'm starting small, just ~$100/block in
> times of congestion.

FYI I've gotten a few hundred dollars worth of donations to this effort, and
have raised the reward to about 0.02 BTC, or $400 USD at current prices.

To be clear, this doesn't mean there will always be a $400 fee tx in the
full-rbf mempool. I have to take a number of precautions to avoid the
double-spend tx being mined by accident, such as only spending txouts with >2
confirmations, and waiting significant amounts of time before the 1st
transaction is sent to allow for maximal propagation.

> If you'd like to donate to this effort, send BTC to
> bc1qagmufdn6rf80kj3faw4d0pnhxyr47sevp3nj9m

-- 
https://petertodd.org 'peter'[:-1]@petertodd.org

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2022-11-08 18:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02  9:26 Peter Todd
2022-11-02 19:02 ` alicexbt
2022-11-03 13:32   ` Erik Aronesty
2022-11-09 12:14     ` email
2022-11-08 18:16 ` Peter Todd [this message]
2022-11-15  5:36   ` Anthony Towns
2022-11-15 14:43     ` Peter Todd
2022-12-05 12:20       ` El_Hoy
2022-12-05 13:38         ` Greg Sanders
2022-12-05 14:12         ` Rijndael
2022-12-05 15:33           ` Michael Folkson
2022-12-05 17:00           ` Erik Aronesty
2022-12-06  4:48             ` El_Hoy
2022-12-05 17:25           ` El_Hoy
2022-12-06  5:39         ` Peter Todd
2022-12-06  7:37           ` Peter Todd
2022-12-09 16:04     ` 0xB10C
2022-12-09 21:16       ` Peter Todd
2022-12-10 11:59         ` 0xB10C
2022-12-10 18:07           ` Peter Todd
2022-12-13  4:01       ` Anthony Towns

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=Y2qc7Ubc5xtJhxGw@petertodd.org \
    --to=pete@petertodd$(echo .)org \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.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