public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "'Ava Chow' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] Human meaningful witness versioning
Date: Mon, 21 Jul 2025 02:24:38 +0000	[thread overview]
Message-ID: <69d118b0-e970-4167-9d74-9998e881b247@achow101.com> (raw)
In-Reply-To: <CAEM=y+UJJ9R5ACxNg=B2HcnBZMxf+KoWtkvH1yFgRcU56hms8g@mail.gmail.com>

On 07/20/2025 06:44 PM, Ethan Heilman wrote:
> 3. You could take the Bech32 approach a little further and save an 
> additional 8-bits by not including the OP_PUSH32 and just inferring it 
> from address length. Granted this length inference would present issues 
> if we want to do more complex things in the ScriptPubkey, but we could 
> handle these cases with Witness versions like we do with bech32 and bech32m.
> [...]
> but since that isn't the case and it 
> was just about the number of characters, why not drop the OP_PUSH?

That's what bech32 does, the push is not encoded in the address. The 
length of the witness program is inferred from the length of the address.

-- 
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/69d118b0-e970-4167-9d74-9998e881b247%40achow101.com.


  reply	other threads:[~2025-07-21 17:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-18 21:58 [bitcoindev] Human meaningful witness versioning Ethan Heilman
2025-07-18 22:18 ` Greg Maxwell
2025-07-18 22:46 ` 'Ava Chow' via Bitcoin Development Mailing List
2025-07-20 15:19 ` 'conduition' via Bitcoin Development Mailing List
2025-07-20 21:29   ` Ethan Heilman
2025-07-20 22:38     ` Greg Maxwell
2025-07-21  1:44       ` Ethan Heilman
2025-07-21  2:24         ` 'Ava Chow' via Bitcoin Development Mailing List [this message]
2025-07-21 17:01         ` Ethan Heilman

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=69d118b0-e970-4167-9d74-9998e881b247@achow101.com \
    --to=bitcoindev@googlegroups.com \
    --cc=lists@achow101.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