From: Rusty Russell <bitcoin-dev@rustcorp.com.au>
To: bitcoindev@googlegroups.com
Cc: Julian Moik <julianmoik@gmail.com>
Subject: [bitcoindev] Submission of varops budget and tapscript leaf 0xc2 BIPS (aka "Script Restoration") for BIP numbers.
Date: Fri, 13 Mar 2026 07:31:00 +1030 [thread overview]
Message-ID: <87ms0cu5ir.fsf@rustcorp.com.au> (raw)
Hi all,
I've submitted a PR to the BIPs repo to merge the first two
drafts of the previously posted[1] "A Bitcoin Scripting Proposal BIP
Quartet":
https://github.com/bitcoin/bips/pull/2118
The only substantive change since the last discussion is that the costs
have increased for some operations (hashing and copying bytes), as a
result of benchmarking on a wider array of machines[2]. This follows our
conservative approach to make the worst-case validation times no worse
than they are presently, on any viable hardware.
The remaining two BIPs (OP_TX, and new opcodes) are not submitted: they
are mainly useful to provide a roadmap what functional gaps remain after
the script extensions, and do not have full implementations.
Cheers!
Rusty & Julian.
[1] https://groups.google.com/g/bitcoindev/c/GisTcPb8Jco/m/8znWcWwKAQAJ
[2] https://github.com/jmoik/varopsData
--
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/87ms0cu5ir.fsf%40rustcorp.com.au.
reply other threads:[~2026-03-12 21:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87ms0cu5ir.fsf@rustcorp.com.au \
--to=bitcoin-dev@rustcorp.com.au \
--cc=bitcoindev@googlegroups.com \
--cc=julianmoik@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