₿ Isaiah ⚡️

@rodpalmerhodl Plebs:

“nodes! how do they work??”

@grok @SpectrGen @sodiumbtc21 @btcballistics Hopefully @SpectrGen reads through this and learns why 4MB average blocks will never happen.. But unfortunately it seems like he’s not here to learn and would rather spread slop instead.

@BitcoinIsaiah @SpectrGen @sodiumbtc21 @btcballistics Precisely. The video captures it perfectly – theoretical 4MB peaks from witness data are possible but far from the sustained reality. Averages hovering 1.6-1.7MB (with ~2MB as a practical ceiling) keep Bitcoin's design efficient and predictable without constant extreme demand.

You need 2TB SSD and 16GB of ram to sync a bitcoin node now, let that sink in, with the current growth pace, running nodes will be unattainable for a large portion of the world.

@grok @SpectrGen @sodiumbtc21 @btcballistics

Yes, exactly. A ~4MB serialized block is theoretically possible by maxing out the 4M weight limit with witness-heavy data (like certain inscriptions), but sustaining that in *every* block is extremely unlikely without perpetual extreme demand for that specific tx type. Recent near-full blocks average ~1.7MB serialized, with overall averages around 1.6MB. A realistic sustained ceiling for average block size is indeed closer to ~2MB.

@grok @SpectrGen @sodiumbtc21 @btcballistics So you would agree that every block being 4MB is technically “possible” but extremely unlikely? The realistic maximum average block size is more like 2MB.

Very few. Only a small handful of specially constructed blocks (mostly large witness-heavy inscriptions since early 2023, like Luxor’s ~3.96 MB one) have approached the theoretical ~4 MB max. The vast majority of Bitcoin’s ~950k+ blocks are well under that—even recent near-full-weight blocks average ~1.7 MB serialized size. True 4 MB every block remains theoretical, not historical reality.

@SpectrGen @sodiumbtc21 @btcballistics @grok how many blocks in Bitcoin’s history have been 4MB?

@BitcoinIsaiah @sodiumbtc21 @btcballistics > 210GB/yr is practically impossible Citation needed

@SpectrGen @sodiumbtc21 @btcballistics Blocks can only be 4MB if they are 100% using witness data. Which is extremely rare, even for “spam.” Blocks are currently full and only around 1.6-2MB on average. 210GB/yr is practically impossible.

@BitcoinIsaiah @sodiumbtc21 @btcballistics 🙄 You said “The chain is growing around 80GB-90GB/yr” — that is not full. If you account for witness data, a full block can weigh around 4MB, or ~210GB/yr Learn the basics of how Bitcoin works

@bathtoob30 @masterminedusa

@masterminedusa The use case was peer 2 peer electronic cash with a middleman. Which isn't possible. Now you want it to be SOV, which it has also failed at. The use case was speculation, you probably failed in the taking profit part.

Bitcoin's main use-case is Store of Value There are only 21 million bitcoin, but unlimited bitcoin IOUs Enough people have to care about having real bitcoin (UTXOs) for this thing to work This a much bigger issue than spam

@SpectrGen @sodiumbtc21 @btcballistics Blocks are already full. None of this increases the block size. Learn the basics of how Bitcoin works.

@BitcoinIsaiah @sodiumbtc21 @btcballistics You’re not accounting for the amount of shit Core devs, shitcoiners, and suitcoiners want to dump on L1 in the next few years. Blowing out OP_RETURN was just Core laying the foundation for what comes next

@rodpalmerhodl No wonder their nodes are having a hard time syncing.

pleb nodes

@volpeLP @omgbruce @sodiumbtc21 @btcballistics The chain is currently growing around 80GB-90GB/yr. It’s not going to magically grow faster than this without a hard fork. This quite literally means 2TB will be fine until 2038-2040. Extremely basic math here.

@BitcoinIsaiah @omgbruce @sodiumbtc21 @btcballistics You cannot include the growth curve and conclude that you'll need 2TB only by 2040. That's matematically impossible.

@volpeLP @omgbruce @sodiumbtc21 @btcballistics That’s not at all what I did but keep talking out your ass.

@BitcoinIsaiah @omgbruce @sodiumbtc21 @btcballistics You just took the first 17 years of Bitcoin's requirements and multiplied by two. That's not how this works. The network growth curve is the key metric to be included when calculating anything related to Bitcoin's size projection. That's your problem, you're too basic.

@volpeLP @omgbruce @sodiumbtc21 @btcballistics Bro doesn’t know how to do basic math.

@BitcoinIsaiah @omgbruce @sodiumbtc21 @btcballistics "We won’t need an SSD larger than 2TB until around 2040." You're literally taking these statements out of your ass. The broad consensus about current recommended specs is 2TB, as it's expected to the sufficient for the short to mid term. The long term recommendation is 4+TB.

@omgbruce @sodiumbtc21 @btcballistics Anyone that’s been paying attention knew 1TB would be obsolete around this time.

@BitcoinIsaiah @sodiumbtc21 @btcballistics That’s what they said about my 1TB then I had to upgrade it again in less than 2 years! 🐸😭

@rodpalmerhodl I see what you’re trying to do Rod

don't gamble your reputation virtue signaling and calling everyone a pedo bet on bitcoin. beta.predyx.com/market/will-bi…

@sodiumbtc21 @btcballistics The chain is growing around 80GB-90GB/yr, so yes.

@BitcoinIsaiah @btcballistics 2040? are you sure?

@bigjeff1430726 @BTCBreadMan “Spam makes bigger blocks” The block size limit remains the same whether there’s spam in it or not. Stop spreading lies.

@BTCBreadMan Spam makes bigger blocks and forces out the nodes. Core changed consensus.

Most BIP-110 proponents are well intentioned and have strong conviction. Most big blockers back in 2017 were also well intentioned and had strong conviction. The road to hell is paved with good intentions and strong conviction.

@BTCBreadMan @KasGobbler Pruned nodes are not as useful as full-nodes though. You need full nodes with the entire transaction history in order for new nodes to download the entire chain. If everyone ran pruned nodes, the network would die.

@KasGobbler Full nodes are not forced to hold the entire tx history. They are required to initially download it to validate the chain, and then they can optionally prune it down dramatically. To 10gb, 2gb, etc. At which point they remain a fully validating node.

When I post about $KAS I get a bunch of engagement from folks with arguments that would be compelling if I didn’t already understand what happens to shitcoins. When I post about BIP-110 I get less engagement, and even less compelling arguments. It’s frankly embarrassing.

@TheKaspianSea @BTCBreadMan @realvijayk @saylor By Saylor? 😆 That dude showed up long after Bitcoin maximalism became a thing.

@BTCBreadMan @realvijayk That’s the issue. You guys have been brainwashed by @saylor to think nothing else is worth your time. Just a mindless, close-minded army ignorant of how technology evolves.