Voskuil explains how an SPV client would validate tx inclusion without 64 byte soft fork.
Looking forward to how future versions of Fountain will handle clip sharing. It's a bit too tedious still. Ideally timestamps in the shownotes are some RSS annotation could automate the process.
https://fountain.fm/clip/6e6xMkP1ilq0JcoohJTI
#bitcoin #consensus
One thing that wasn't spelled out, IIUC, is that in order to know the depth of the transaction merkle tree in a block, you just need to know the depth of *any* one transaction. This is because the tree is flat. So the coinbase transaction is used for this, plus the requirement that it starts with 36 zeros.
Though this could be annoying if the coinbase is 4MB? (I should keep listening)
nostr:nprofile1qqsvvk9qy7qx2gzed6wazxtureunuxljam66za6yr3p02zc0qhz57jqpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgcwaehxw309ahx7um5wghxvmt59emkj73wvf5h5tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhs0dsl3l noted in discussion on Delving that you only need a proof of transaction contents (e.g. the coinbase outpoint) if the tx is exactly 64 bytes. Otherwise, a proof of tx size is sufficient, which is compatible with SHA midstate verification (i.e., ~100 bytes max data).
