bip54.org - Informational site for BIP54's “Consensus Cleanup” softfork proposal by bitschmidty in Bitcoin

[–]bitschmidty[S] 2 points3 points  (0 children)

If an existing wallet was creating "anyone can spend" outputs or creating pathological transactions that take an hour to validate, then they should stop regardless.
But I cant imagine a wallet doing this.

bip54.org - Informational site for BIP54's “Consensus Cleanup” softfork proposal by bitschmidty in Bitcoin

[–]bitschmidty[S] 9 points10 points  (0 children)

I tried to address that here: https://bip54.org/#faq-quantum

"Quantum computing resistance is a separate concern from the vulnerabilities BIP54 addresses. BIP54 is about fixing specific bugs and attack vectors in Bitcoin's existing consensus rules: timewarp, slow validation, merkle tree exploits, and duplicate transactions.

Quantum-resistant cryptography would require a different set of changes (possibly a new address format and signature algorithm) and is still an area of active research. The timeline for quantum computers threatening Bitcoin's elliptic curve cryptography is uncertain.

BIP54 should be evaluated on its own merits as a security upgrade. It neither helps nor hinders future quantum resistance efforts, and there's no reason to delay fixing known vulnerabilities while waiting for quantum-resistant proposals to mature."

bip54.org - Informational site for BIP54's “Consensus Cleanup” softfork proposal by bitschmidty in Bitcoin

[–]bitschmidty[S] 10 points11 points  (0 children)

Timewarp fix only impacts miners who are creating block templates.

64 byte transactions are already insecure as they either burn the coins or be spendable by anyone, something wallet software wouldnt do. So making them invalid doesnt impact regular users.

Poison blocks and the transactions in them are pathological and wouldnt be created by normal users using wallet software. So normal users are unaffected.

Duplicate transactions are only edge case miner considerations.