From: Peter Todd <pete@petertodd•org>
To: 0xB10C <b10c@b10c•me>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Cc: Anthony Towns <aj@erisian•com.au>
Subject: Re: [bitcoin-dev] Announcement: Full-RBF Miner Bounty
Date: Fri, 9 Dec 2022 16:16:20 -0500 [thread overview]
Message-ID: <Y5OlpAi3wHPKxxkx@petertodd.org> (raw)
In-Reply-To: <f146ca66-a611-f129-ae11-6907a7333d10@b10c.me>
[-- Attachment #1: Type: text/plain, Size: 1835 bytes --]
On Fri, Dec 09, 2022 at 05:04:05PM +0100, 0xB10C via bitcoin-dev wrote:
> Hi AJ and list,
>
> > This seems to be pretty good evidence that we currently don't have any
> > significant hashrate mining with fullrbf policies (<0.5% if there was a
> > high fee replacement available prior to every block having been mined),
> > despite the bounty having been collected.
>
> For further monitoring, I've set-up a mempoolfullrbf=1 node and are
> logging replacement events with [0]. I filter the full-RBF replacements
> and list the replaced and replacement transactions here:
Question: are you taking any special steps to peer that node with other
full-rbf nodes? I see you are in fact getting all the replacements I'd expect
you to get, so you must have good peering. I'm curious what it took (if
anything) to achieve that. Also, is that node accepting incoming connections?
> Over the last few days, I has mostly seen OP_RETURN transactions
> (presumably mostly by OpenTimestamps; but I haven't checked closely) and
> a few other non-OP_RETURN transactions. None of the replacement
> transactions have been mined yet.
They are mostly OpenTimestamps transactions; I checked against the records from
my calendars and didn't find any OP_Return tx that wasn't one of mine.
The two calendars making full-rbf replacements are:
https://alice.btc.calendar.opentimestamps.org/
https://bob.btc.calendar.opentimestamps.org/
The status pages currently link to https://mempool.nixbitcoin.org, which is
also running mempoolfullrbf=1 As you can see, I've started the full-rbf bounty
again on Alice.
https://blockstream.info also enabled full-rbf a few days ago. But currently
propagation to their nodes is spotty, so replacements don't always show up.
--
https://petertodd.org 'peter'[:-1]@petertodd.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-12-09 21: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
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 [this message]
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=Y5OlpAi3wHPKxxkx@petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=aj@erisian$(echo .)com.au \
--cc=b10c@b10c$(echo .)me \
--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