From: Anthony Towns <aj@erisian.com.au>
To: Sergej Kotliar <sergej@bitrefill.com>,
Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Re: [bitcoin-dev] [Opt-in full-RBF] Zero-conf apps in immediate danger
Date: Tue, 6 May 2025 15:39:31 +1000 [thread overview]
Message-ID: <aBmgk4nqULp2_5GA@erisian.com.au> (raw)
In-Reply-To: <aBSZGqZ50K-WVnAf@erisian.com.au>
On Fri, May 02, 2025 at 08:06:18PM +1000, Anthony Towns wrote:
> So the mempoolfullrbf default changed from false to true in 28.0 released
> in October last year, which is advertised as being run by maybe 30%-40%
> of the network now, and fullrbf transactions have been reportedly been mined
> reliably since well before that.
>
> Any chance of an update on how that change has affected bitcoin/lightning
> payment volume for you guys, or customer satisfaction (if payment
> acceptance is delayed more often), or how much engineering/support time
> was needed to adapt, or any other impact?
There was a related thread on X late last year that offers some relevant
information for these questions:
https://x.com/MattAhlborg/status/1828436316930912364
Some key points from that thread, IMO:
* The "relative volume" metric shows a drop in bitcoin/lightning volume
from 30%-40% in 2022 to 25%-30% in late 2024
* The "monthly active users" metric shows a drop in bitcoin/lightning
volume from about 50% to about 40% in a similar timeframe, as well as
a large switch from on-chain to lightning
* The "average payment size" metric shows distinctly different behaviours
between on-chain bitcoin users and lightning users -- individual
on-chain payments are about 4x greater in value than individual
lightning payments
* Bitrefill stopped accepting zeroconf transactions in Aug/Sep 2023; they
didn't indicate if this was due to seeing a rise in (attempted?) fraud,
or a purely preventative measure.
* The charts show definite correlations between the decrease in on-chain
activity with fee spikes
* The charts don't show obvious correlations between on-chain activity
and when bitrefill stopped accepting zeroconf transactions. At best
you could argue this shows up as volume not returning to on-chain
bitcoin after the fee spikes eased.
* This may also be due to a rise in use of bitrefill accounts -- ie,
you send a bunch of money to top up your bitrefill account, and
then later spend small amounts from that. Doing that provides some
insulation from the impact of both on-chain fees and confirmation
delays. The thread doesn't give details on how that has changed over
time, so there's no indication if there's any correlation with either
dropping support for zeroconf or with fee spikes.
* Much of the lightning monthly active users (>50%) is due to a business
partnership, where the users don't end up using lightning directly. The
author speculates that as little as 12.5% (or as much as 25%) of the
lightning payments they see are from users who control their own keys.
That's not super positive for bitcoin (as a payments system) overall --
lightning growth seems to be almost entirely in the B2B zone, rather
than the P2P zone, in particular.
It doesn't seem to indicate huge problems resulting from how
mempoolfullrbf was handled; though if "just custody funds with bitrefill"
was a significant mitigating factor, perhaps that's not terribly positive
either from a P2P, be-your-own-bank perspective.
IMO, anyway. Thanks to John Carvalho for the pointer to the thread.
Cheers,
aj
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/aBmgk4nqULp2_5GA%40erisian.com.au.
next prev parent reply other threads:[~2025-05-06 6:03 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABZBVTC5kh7ca3KhVkFPdQjnsPhP4Kun1k3K6cPkarrjUiTJpA@mail.gmail.com>
2022-10-19 14:29 ` [bitcoin-dev] [Opt-in full-RBF] Zero-conf apps in immediate danger Sergej Kotliar
2022-10-19 14:45 ` Erik Aronesty
2022-10-19 15:43 ` Jeremy Rubin
2022-10-19 15:51 ` Greg Sanders
2022-10-19 16:04 ` Sergej Kotliar
2022-10-19 16:08 ` Greg Sanders
2022-10-20 1:37 ` Antoine Riard
2022-10-20 14:11 ` Sergej Kotliar
2022-10-21 1:04 ` Antoine Riard
2022-10-20 4:05 ` Peter Todd
2022-10-21 19:35 ` Peter Todd
2022-10-20 7:22 ` Anthony Towns
2022-10-20 12:37 ` Sergej Kotliar
2022-10-20 14:14 ` Ruben Somsen
2022-10-20 14:17 ` Sergej Kotliar
2022-10-20 19:58 ` Anthony Towns
2022-10-20 21:05 ` David A. Harding
2022-10-20 21:07 ` Greg Sanders
2022-10-20 22:02 ` Eloy
2022-10-21 12:02 ` Sergej Kotliar
2022-10-21 14:01 ` Greg Sanders
2022-10-21 14:19 ` Sergej Kotliar
2022-10-21 14:47 ` Greg Sanders
2022-10-21 19:43 ` Peter Todd
2022-10-24 7:55 ` Sergej Kotliar
2022-10-20 22:13 ` Peter Todd
2022-10-21 9:34 ` Sergej Kotliar
2022-10-21 19:33 ` Peter Todd
2022-10-24 7:45 ` Sergej Kotliar
2022-10-21 11:56 ` Sergej Kotliar
2025-05-02 10:06 ` [bitcoindev] " Anthony Towns
2025-05-06 5:39 ` Anthony Towns [this message]
2022-10-23 19:20 ` David A. Harding
2022-10-23 20:51 ` alicexbt
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=aBmgk4nqULp2_5GA@erisian.com.au \
--to=aj@erisian.com.au \
--cc=bitcoindev@googlegroups.com \
--cc=sergej@bitrefill.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