Hi Sjors,
On 2026-01-08 00:30, Sjors Provoost wrote:
The approach suggested by Towns [4] of appending a 0-sat OP_RETURN output with
padding so a 4-byte nonce lands in the final 64-byte SHA256 chunk is probably
better, but not because like nLockTime it has a small hashing midstate
benefit. It's easier to implement.
I can’t access Delving right now to read AJ’s comment, but a small nit
on the idea of using an additional output: BIP 141 requires coinbase
transaction inputs to have a 32-byte witness. Since the witness section
follows the outputs in the serialization, the bytes before the
`nLocktime` in a coinbase transaction are the witness of the coinbase
input, not the last output script.
-Murch
--
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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/bitcoindev/492f9bba-8a1f-4fa2-8618-98bd564a6178%40murch.one.
