From: /dev /fd0 <alicexbtong@gmail•com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] A Taproot-native (re-)bindable transaction bundle proposal
Date: Fri, 11 Jul 2025 20:44:09 -0700 (PDT) [thread overview]
Message-ID: <2c16b2d0-ac82-4c10-8404-02001bda2658n@googlegroups.com> (raw)
In-Reply-To: <a40c2b1a-1164-4794-a6d5-79d0b97296aa@murch.one>
[-- Attachment #1.1: Type: text/plain, Size: 2114 bytes --]
> P2TR UTXO count¹: 57,956,440 (34.7% of UTXO count)
The fact that 86% of these UTXOs are under 1000 sats suggests that the use
cases envisioned by protocol developers before taproot activation are still
struggling to gain adoption.
/dev/fd0
floppy disk guy
On Saturday, July 12, 2025 at 6:03:59 AM UTC+5:30 Murch wrote:
> 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/2c16b2d0-ac82-4c10-8404-02001bda2658n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 3948 bytes --]
prev parent reply other threads:[~2025-07-13 0:46 UTC|newest]
Thread overview: 10+ 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
2025-07-12 3:44 ` /dev /fd0 [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=2c16b2d0-ac82-4c10-8404-02001bda2658n@googlegroups.com \
--to=alicexbtong@gmail$(echo .)com \
--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