From: Murch <murch@murch•one>
To: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] A Taproot-native (re-)bindable transaction bundle proposal
Date: Fri, 11 Jul 2025 17:27:14 -0700 [thread overview]
Message-ID: <a40c2b1a-1164-4794-a6d5-79d0b97296aa@murch.one> (raw)
In-Reply-To: <CAPfvXf+E0YDzqY_jsGVoc4KKh_Kgsp-p20wNAD05tv_rMNG2sA@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1696 bytes --]
Hello list,
On 2025-07-10 05:24, James O'Beirne wrote:
> Right now two separate estimates put Taproot usage (by value) at
> 0.1% or 0.75% as of May 2025[3][4]. This is nearly four years after its
> activation. We can't say exactly why users aren't upgrading, but the
> reality is that the overwhelming majority of value transfer in bitcoin
> is still happening in a pre-Taproot script context.
I thought there might be interest in a few more metrics regarding P2TR
usage.
Stats on the current UTXO set, from today:
• Bitcoins held in P2TR outputs¹: ~156,309 (0.79% of supply)
• P2TR UTXO count¹: 57,956,440 (34.7% of UTXO count)
30-day averages as of 2025-07-10:
• P2TR outputs by value²: 8.3%
• P2TR output count³: 20.0%
• P2TR input count⁴: KP 16.0%, SP: 7.0%
"P2TR outputs by value" has been trending up steadily since February,
being 1.4% on February 1st, possibly due to more people taking on UTXO
management tasks and wallet updates since the mempool cleared end of
January.
Cheers,
Murch
———
¹ via https://dune.com/murchandamus/bitcoins-utxo-set
² via https://mainnet.observer/charts/output-type-distribution-amount/
³ https://mainnet.observer/charts/output-type-distribution-count/
⁴ https://mainnet.observer/charts/inputs-types-by-count/
--
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/a40c2b1a-1164-4794-a6d5-79d0b97296aa%40murch.one.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 61209 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2025-07-12 0:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 18:19 Greg Sanders
2025-07-09 19:59 ` Rijndael
2025-07-09 20:05 ` Rijndael
2025-07-09 20:14 ` Ademan
2025-07-10 4:44 ` Brandon Black
2025-07-10 12:24 ` James O'Beirne
2025-07-11 18:37 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-07-11 22:59 ` James O'Beirne
2025-07-12 0:27 ` Murch [this message]
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=a40c2b1a-1164-4794-a6d5-79d0b97296aa@murch.one \
--to=murch@murch$(echo .)one \
--cc=bitcoindev@googlegroups.com \
/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