Replying to Avatar ESE

Today’s quiet mempool isn’t a danger—the subsidy still secures the chain—but the new unlimited-blob rule is permanent and will let the subsequent spam wave stuff blocks, driving up disk, RAM, and bandwidth costs until only datacentres can afford to run nodes. Meanwhile fast off-chain payment networks are on track to reach global scale within a couple of years, so real payment traffic—not chain-bloating uploads—will feed the fee market once the subsidy is gone; if we don’t keep block weight in check now, we’ll end up with Ethereum-style centralised validation just as those fees finally arrive.
Avatar
rieger_san 7mo ago

That’s simply not true because a block can not be larger than 4mb and we have a block time of ten minutes. This rule is written in stone!

Reply to this note

Please Login to reply.

Discussion

Avatar
ESE 7mo ago

When we say “the cap is X,” we’re talking about the consensus block-size limit—nothing else. Un-capping OP_RETURN makes it normal for every block to slam into that limit with random data, and once that feels routine, the most “logical” follow-up from Core is to raise the block size again. Meanwhile, the most “logical” move from alternative node software will be to clap back by filtering off-curve fake pub-key blobs—because if we’re playing Whac-A-Mole, we might as well bring a bigger mallet.

Avatar
rieger_san 7mo ago

You cannot raise the block size because it would require a hard fork.