What sections you think need the chop chop, the virtual block, segwit data or both?

Reply to this note

Please Login to reply.

Discussion

There are no sections...๐Ÿคจ

I'm afraid I'm not familiar with the precise wording.

What I meant to ask is if you think the block size should be reduced maintaining the same proportion of segwit to virtual block data (e.g. 0.5MB virtual, 1.5MB segwit) or just clip the segwit data (e.g. 1MB virtual, 1MB segwit).

Ideally something like 600kWU limit with non-segwit signatures given the same discount.

Sounds rough, if I'm not mistaken that'd be just 150kb of virtual data per block ๐Ÿ’€ How do you get to that number?

There's no such thing as virtual data...

Blocks would be about 300k

Well, there is segwit data that weights 1WU, and non-segwit data that weights 4WU, no? ๐Ÿค”

For 600kWU max block sizes would range from 150kb (block with only legacy txs) to 600kb (almost no txs and huge taproot script/monke pic)

Again, I would give the same 1 WU/B discount to non-segwit ("legacy"๐Ÿ˜ฎโ€๐Ÿ’จ) signatures.

Blocking spam is a different issue, to be resolved in a different way (maybe).

Aight, now I gotchu. Thanks for the patience ๐Ÿ˜ฌ