From 7c7e2f10a4ed096b10cd3ea0fd966286057f9c52 Mon Sep 17 00:00:00 2001 From: Antoine Poinsot Date: Tue, 7 Jul 2026 15:32:17 -0400 Subject: [PATCH] bip-0054: an SPV verifier that supports 64-byte txs would have to be modified --- bip-0054.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/bip-0054.md b/bip-0054.md index bbac6c4f..bf5e6527 100644 --- a/bip-0054.md +++ b/bip-0054.md @@ -107,10 +107,10 @@ alternatives to invalidating them were previously proposed. Some believe the imp of Merkle proofs are too marginal to be worth introducing a discontinuity in the set of valid witness-stripped transaction sizes (discussion [here][64 bytes debate]). Others have suggested instead committing to the Merkle tree depth in the header's version field[^8], or even invalidating Merkle tree nodes that correspond -to a valid serialization for a Bitcoin transaction[^14]. These options make some of the available +to a valid serialisation for a Bitcoin transaction[^14]. These options make some of the available workarounds[^13] easier to deploy. The authors believe it is preferable to address the root cause by -invalidating 64-byte transactions, fixing the vulnerability without Merkle proof users having to -rely on any workaround or even know one is necessary in the first place. +invalidating 64-byte transactions. This fixes the vulnerability for users relying on Merkle proofs +of non-64-byte transactions, without requiring a workaround. The `nLockTime` field of transactions is a natural place to store a block height and is currently unused in coinbase transactions. Using it to enforce that new coinbase transactions differ from