mleku on Nostr: i think that the fact it allows users to define new transaction types and have them ...

i think that the fact it allows users to define new transaction types and have them adopted by miners by minting transactions they cannot verify for spends to get them to upgrade is a great idea. but nobody has done it so far, not sure if they haven't tried.

> has there ever been anyone trying to create a new witness program for segwit ever? and how did it go since obviously if there was, they didn't succeed

yes, someone tried and withdrew.

the closest direct analogue to your p2spkh was P2SKH (Pay to Schnorr Key Hash), proposed on the bitcoin-dev mailing list march 2026. it used schnorr key recovery to avoid putting the pubkey in the witness - saving ~12 bytes. essentially the same idea: hash the pubkey, schnorr signature in witness.

it was withdrawn by its author after technical discussion. the killer argument: BIP340's pubkey prefixing (hashing over H(R, P, m) instead of H(R, m)) is deliberate - it enables MuSig and key aggregation. losing scriptability for 12 bytes wasn't worth it.

however, your p2spkh has a different motivation than P2SKH. P2SKH was about efficiency (12 bytes). yours is about quantum resistance (Shor's algorithm on naked pubkeys). that's a stronger argument - but the same counterargument applies: you lose key aggregation and scriptability. the quantum resistance case hasn't been tested on the mailing list the way the efficiency case was.

the other live proposal is BIP360 (P2MR) - claims witness version 2, quantum-resistant using post-quantum signature schemes inside a merkle root structure. has a working testnet implementation from BTQ Technologies, in the formal BIP process. if BIP360 advances, witness version 2 is taken. your option would be version 3 - which BIP-110 currently blocks.

the landscape is: v0 active, v1 active, v2 contested (BIP360 claims it), v3 blocked (BIP-110), and the last attempt at a schnorr-key-hash witness program (P2SKH) failed on technical grounds that partially overlap with yours. nobody has succeeded at adding a new witness version since taproot in 2021.

---

so, yeah, segwit is interesting, but the forum for discussing adopting it is poisoned, if you ask me.

the only way i see it happening is if people create an alternative to *centralised github* discussion forum or outside the bitcoin mailing list. there is nothing stopping anyone from doing it, the biggest challenge is working around the active suppression being done by the core-dominated discussion forums.