From: "'Russell O'Connor' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: Greg Maxwell <gmaxwell@gmail.com>,
Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Policy restrictions Was: [BIP Proposal] Limit ScriptPubkey Size >= 520 Bytes Consensus.
Date: Thu, 30 Oct 2025 16:27:34 -0400 [thread overview]
Message-ID: <CAMZUoKnyYpfJ1fZRan7BzyGvMitxznoSyCXkjxc2Qy5Z9pNvMA@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgSNtO6kpfm0XaBCufyExjJnxg87ttLGUgpUU9pkemZTig@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1423 bytes --]
On Thu, Oct 30, 2025 at 2:40 AM Greg Maxwell <gmaxwell@gmail.com> wrote:
> I don't even think bitcoin has ever policy restricted something that was
> in active use, much less softforked out something like that.
>
I invite the Bitcore lore experts to correct me here, but I recall someone
many years ago finding that their bare multisig funds (likely related to
the Counterparty nonsense) were stuck by policy due to some new policy
being enacted to mandate that pubkeys in bare multisigs must now all be
on-curve points ... or something like that. I do hope that they managed to
get their funds recovered by now with direct miner intervention.
I really ought to vet my claim above by going through my IRC logs and
Bitcoin development history ... but a quicker way is to post a claim
publicly on the internet and wait for someone else to call it out as being
wrong.
Also, I think this type of policy change quite harmful and shouldn't be
replicated, and ideally reverted, assuming my story is correct.
--
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/CAMZUoKnyYpfJ1fZRan7BzyGvMitxznoSyCXkjxc2Qy5Z9pNvMA%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 2077 bytes --]
next prev parent reply other threads:[~2025-10-30 20:40 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 20:42 [bitcoindev] " PortlandHODL
2025-10-02 22:19 ` Andrew Poelstra
2025-10-02 22:46 ` Andrew Poelstra
2025-10-02 22:47 ` 'moonsettler' via Bitcoin Development Mailing List
2025-10-03 7:11 ` Garlo Nicon
2025-10-02 22:27 ` Brandon Black
2025-10-03 1:21 ` [bitcoindev] " /dev /fd0
2025-10-03 10:46 ` 'moonsettler' via Bitcoin Development Mailing List
2025-10-03 11:26 ` /dev /fd0
2025-10-03 13:35 ` jeremy
2025-10-03 13:59 ` Andrew Poelstra
2025-10-03 14:18 ` /dev /fd0
2025-10-03 14:59 ` Andrew Poelstra
2025-10-03 16:15 ` Anthony Towns
2025-10-05 9:59 ` Guus Ellenkamp
2025-10-03 13:21 ` [bitcoindev] " Peter Todd
2025-10-03 16:52 ` 'moonsettler' via Bitcoin Development Mailing List
2025-10-03 15:42 ` Anthony Towns
2025-10-03 20:02 ` Luke Dashjr
2025-10-03 20:52 ` /dev /fd0
2025-10-04 23:12 ` jeremy
2025-10-05 10:59 ` Luke Dashjr
2025-10-08 15:03 ` Greg Tonoski
2025-10-08 18:15 ` Keagan McClelland
2025-10-15 20:04 ` [bitcoindev] " Casey Rodarmor
2025-10-16 0:06 ` Greg Maxwell
2025-10-17 17:07 ` Brandon Black
2025-10-17 18:05 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-10-18 1:01 ` Antoine Riard
2025-10-18 4:03 ` Greg Maxwell
2025-10-18 12:06 ` PortlandHODL
2025-10-18 16:44 ` Greg Tonoski
2025-10-18 16:54 ` /dev /fd0
2025-10-22 8:07 ` 'moonsettler' via Bitcoin Development Mailing List
2025-10-27 23:44 ` Michael Tidwell
2025-10-30 2:26 ` Greg Maxwell
2025-10-30 3:36 ` Michael Tidwell
2025-10-30 6:15 ` Greg Maxwell
2025-10-30 8:55 ` Bitcoin Error Log
2025-10-30 17:40 ` Greg Maxwell
2025-10-30 20:27 ` 'Russell O'Connor' via Bitcoin Development Mailing List [this message]
2025-10-30 22:23 ` [bitcoindev] Re: Policy restrictions Was: " 'Russell O'Connor' via Bitcoin Development Mailing List
2025-10-30 16:10 ` [bitcoindev] " Tom Harding
2025-10-30 22:15 ` Doctor Buzz
2025-10-20 15:22 ` Greg Maxwell
2025-10-21 19:05 ` Garlo Nicon
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=CAMZUoKnyYpfJ1fZRan7BzyGvMitxznoSyCXkjxc2Qy5Z9pNvMA@mail.gmail.com \
--to=bitcoindev@googlegroups.com \
--cc=gmaxwell@gmail.com \
--cc=roconnor@blockstream.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