Quote from: Synchronice on May 27, 2024, 12:16:05 PM

By the way, do you know what does this mean? (Click on image for high resolution). What does BAVO mean? BAVO MINT 1,000? And why are they so much on this image? It's from the address that you posted.

1. BAVO refer to name of the token created using BRC-20 protocol.
2. MINT 1000 means someone mint/create 1000 BAVO token.
3. Someone probably mint/create bunch of BAVO at once.

Quote from: larry_vw_1955 on Today at 12:06:01 AM

Quote from: gmaxwell on May 27, 2024, 04:47:05 AM

They don't take up the "same space". In order to validate blocks utxo data needs to be quickly accessible as the access speed bottlenecks validation speed, witness data doesn't need to be stored *at all*, since once you've validated it once you can forget it, so the long term cost of witness data is orders of magnitude lower.

i'm not sure what you mean by "utxo data" but utxos don't have signatures attached to them. they have to be signed to be spent. a utxo is just a transaction id with a particular output index number. nothing more than that. in practice though i think the output index number is looked up and replaced with the value and scriptpubkey. but still. we aren't needing to store any signatures in the utxo set.

for non-segwit transactions the signature is stored in the scriptsig field of transaction inputs. but they are not needed. so once you have validated a particular transaction you could just throw it away. and just store any of its outputs you needed to in the utxo set.

I think you missed the point. I think his point is that adding arbitrary data to "fake" address/public key leads to longer time to verify transaction, while using witness doesn't have such impact.