- All-OP_RETURN blocks: If miners fill complete 4 MB blocks with nothing however massive OP_RETURN outputs, what are the validation and propagation penalties?
They can not. OP_RETURNs exist in transaction outputs, which aren’t topic to the witness low cost. The most important consensus-valid quantity of OP_RETURN knowledge in a block is just below 1 million bytes, considerably smaller than what is feasible with utterly extraordinary segwit transactions. They’re are additionally far less complicated to validate; it is transaction inputs which can be costly by way of computation and I/O phrases.
Even ignoring that, relay coverage continues to be restricted to 100 kvB transactions. A miner can after all exceed that, however that was already the case, and their skill to take action is unaffected by the (default) coverage modifications in Bitcoin Core v30.
- Mempool flooding: What occurs if the community is flooded with hundreds of very massive OP_RETURN transactions that linger unconfirmed? How does eviction carry out towards “fewer however heavier” junk txs?
Fewer bigger transactions is way preferable on this regard than many small transactions.
- Propagation asymmetry: Might sustained megabyte-heavy blocks widen propagation gaps between high-bandwidth and low-bandwidth miners, rising orphan danger and centralization stress?
That’s the reason the block weight restrict exists. Blocks might be crammed to 1 MvB (and as much as 4 MB serialized measurement) no matter coverage, and ceaselessly have been. If something, together with massive OP_RETURNs reduces the influence right here, as they don’t seem to be topic to the witness low cost 4x issue, so their inclusion displaces extra witness bytes than their very own serialized measurement.
- Storage development: Sustained 4 MB junk blocks would develop the chain by ~576 MB/day (~210 GB/12 months). How effectively does Core’s blockfile and database design deal with such development, particularly for pruned nodes?
Sustained 4 MB junk blocks are already doable. OP_RETURN outputs cut back the disk development area, by not being topic to low cost.
- Charge market influence: If OP_RETURN demand competes instantly with financial transactions, has charge estimation been stress-tested for non-financial blockspace utilization?
I do not see how charge estimation could be affected by, or is in any means associated to, the person’s intent for transactions.
