public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd.org>
To: James O'Beirne <james.obeirne@gmail.com>
Cc: Antoine Poinsot <darosior@protonmail.com>,
	Greg Sanders <gsanders87@gmail.com>,
	Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] A Taproot-native (re-)bindable transaction bundle proposal
Date: Thu, 17 Jul 2025 09:05:20 +0000	[thread overview]
Message-ID: <aHi80KYQB7ZnUiVl@petertodd.org> (raw)
In-Reply-To: <CAPfvXfL59wF-sfrnwkK0NUeGCphsJ1VJzGmbTUDHgNFncx2VSw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1698 bytes --]

On Fri, Jul 11, 2025 at 06:59:18PM -0400, James O'Beirne wrote:
> Hi Antoine,
> 
> > You state that between 0.1% and 0.75% of all bitcoins in existence are
> > held in P2TR outputs, and use this figure to conclude the
> > "overwhelming majority of **value transfer** in bitcoin is still
> > happening in a pre-Taproot script context".
> 
> I think you might have misparsed my email; I wasn't using one
> observation to justify the other.
> 
> I ran a script[0] to tally the value of newly created outputs by address
> type, and the node tells me that 93.5% of all output-value created over
> the last three months is non-P2TR.

The total output value created that is non-P2TR is irrelevant here: all those
outputs are being created by existing production systems. Obviously, they have
no reason to rush to implementing taproot. Heck, as I just mentioned elsewhere,
even P2PKH addresses are *still* fairly commonly used even though there are
significant fee savings to upgrading. People just don't like upgrading existing
- working - code unless there is a really good reason.

What we're discussing here is a new scripting feature, that inevitably are only
useful for brand new code. There are no sigificant obstacles to new code making
use of taproot.

ACK new opcodes being taproot only.

-- 
https://petertodd.org 'peter'[:-1]@petertodd.org

-- 
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/aHi80KYQB7ZnUiVl%40petertodd.org.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2025-07-17 10:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-09 18:19 [bitcoindev] A Taproot-native (re-)bindable transaction bundle proposal 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-14 14:23       ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-07-17  9:05       ` Peter Todd [this message]
2025-07-12  0:27   ` Murch
2025-07-12  3:44     ` /dev /fd0
2025-07-14 13:58       ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-07-17  9:00       ` Peter Todd

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=aHi80KYQB7ZnUiVl@petertodd.org \
    --to=pete@petertodd.org \
    --cc=bitcoindev@googlegroups.com \
    --cc=darosior@protonmail.com \
    --cc=gsanders87@gmail.com \
    --cc=james.obeirne@gmail.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