From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org, Peter Todd <pete@petertodd•org>
Subject: Re: [bitcoin-dev] Playing with full-rbf peers for fun and L2s security
Date: Wed, 15 Jun 2022 02:53:58 +0000 [thread overview]
Message-ID: <202206150253.59722.luke@dashjr.org> (raw)
In-Reply-To: <YqlDiCEMQ/1tCJ0Z@petertodd.org>
Bitcoin Knots still uses this service bit, FWIW (though due to a bug in some
older versions, it wasn't signalled by default). There are probably at least
100 nodes with full RBF already.
On Wednesday 15 June 2022 02:27:20 Peter Todd via bitcoin-dev wrote:
> On Mon, Jun 13, 2022 at 08:25:11PM -0400, Antoine Riard via bitcoin-dev
wrote:
> > If you're a node operator curious to play with full-rbf, feel free to
> > connect to this node or spawn up a toy, public node yourself. There is a
> > ##uafrbf libera chat if you would like information on the settings or
> > looking for full-rbf friends (though that step could be automated in the
> > future by setting up a dedicated network bit and reserving a few outbound
> > slots for them).
>
> I previously maintained a Bitcoin Core fork that did just that, using
> nServices bit 26:
>
> https://github.com/petertodd/bitcoin/commit/1cc1a46a633535c42394380b656d681
>258a111ac
>
> IIRC I was using the code written to prefer segwit peers; I have no idea if
> a similar approach is still easy to implement as I haven't worked on the
> Bitcoin Core codebase for years.
next prev parent reply other threads:[~2022-06-15 2:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 0:25 Antoine Riard
2022-06-15 2:27 ` Peter Todd
2022-06-15 2:53 ` Luke Dashjr [this message]
2022-06-15 3:18 ` Peter Todd
2022-06-16 0:16 ` alicexbt
2022-06-16 1:02 ` Greg Sanders
2022-06-16 1:45 ` alicexbt
2022-06-16 5:43 ` linuxfoundation.cndm1
2022-06-16 12:47 ` alicexbt
2022-06-16 13:24 ` Greg Sanders
[not found] ` <gmDNbfrrvaZL4akV2DFwCuKrls9SScQjqxeRoEorEiYlv24dPt1j583iOtcB2lFrxZc59N3kp7T9KIM4ycl4QOmGBfDOUmO-BVHsttvtvDc=@protonmail.com>
2022-06-17 1:34 ` Antoine Riard
2022-06-17 4:54 ` alicexbt
2022-06-19 10:42 ` Peter Todd
2022-06-21 23:43 ` Antoine Riard
2022-06-26 16:40 ` alicexbt
2022-06-27 0:43 ` Peter Todd
2022-06-27 12:03 ` Greg Sanders
2022-06-27 13:46 ` Peter Todd
2022-07-05 20:46 ` alicexbt
2022-07-08 14:53 ` Peter Todd
2022-07-08 15:09 ` Greg Sanders
2022-07-08 19:44 ` alicexbt
2022-07-09 15:06 ` Antoine Riard
2022-06-20 23:49 ` Peter Todd
2022-06-21 23:45 ` Antoine Riard
2022-06-23 19:13 ` Peter Todd
2022-08-24 1:56 ` Antoine Riard
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=202206150253.59722.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--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