Nostr Web Client

I kind of understand what you are saying, but it’s alittle bit above my head in terms of verifying myself.

You’re saying: how nodes store the data of UTXOs locally has a different footprint than the virtual blockspace we bid for?

Out if the 4 vMB possible in a block (post segwit) what is the smallest block footprint (vbyte) allowed to have a single valid and spendable UTXO. I understand this minimum will vary depending on the script used, but I’m just looking for the actual smallest structure of memory for a valid utxo (as a % of the 4vMB available for each block).

waxwing 5mo ago 💬 2

OK, then you can ignore the other part.

For utxos (outputs), vbytes == bytes, because there is no witness discount.

You'd want to look up utxo sizes for each type: p2pk, p2pkh, p2sh, p2wpkh, p2wsh, p2tr. As above i think p2tr is 43? Maybe p2wpkh is 1 byte less? I forget.

Reply to this note

Please Login to reply.

Discussion

Jack K 5mo ago

I see, it gets more complex without having the witness discount; so witness basically increases our potential by 3MB (4MB total) and without witness we still bound by original 1MB?

The total available blocksize varies depending on the outputs selected by miners; selecting more segwit addresses increases the possible max size from 1MB to some amount X <4MB?

waxwing 5mo ago 💬 1

Yeah that's basically it. No witness at all, 1MB size. Arranging to have a huge amount of witness data in the block can get it close to 4MB. But that's extremely artificial.

Jack K 5mo ago

Thank you for the clarification. This makes sense. I was trying to understand why the real world outcome is ~2.5MB vs the theoretical 4MB.

The speed of information (MB/Block) written to the chain depends on the outputs, and the maximum allowable blocksize varies between1MB-4MB depending if segwit transactions are selected and how much witness data is included.

Lots of complexity to take into account!