Tackling Block Size and Mempool Issues

Scalability is still an issue, whether we like it or not. We tend to ignore it when everything runs smoothly, but when fees spike and mempool fills up, we're back to square one. Why do we keep letting those who pay more jump the queue?

Exactly! We need to figure out how to improve transaction batching and get more transactions to join in without the crazy fees.

But those tools won't fix old transactions, right? They're just to help the ones that choose to opt-in. Everyone else is still stuck paying up, typical.

Check this out: Mastercard just launched a new service for P2P crypto transactions using aliases instead of long addresses. Could this be the future?

The whole block size debate has been around for ages, but increasing it could centralize miners. Not really what Bitcoin is about. Layer 2 solutions might ease some pressure.

Why not just admit it? 1TB is outdated. Hard drives are getting huge, let’s catch up.

You could set up DNS entries for aliases, like a domain name that links to a signed transaction. Pretty cool, right?

You’re missing the point. The block size changes based on how transaction size is calculated. SegWit was supposed to fix malleability, not just make things bigger.

So one user might make several transactions instead of just one? But do you really want to run a full node if the size increases?

Fees have been crazy lately, like 6-7 sat/vb, which is way above the expected 1 sat/vb. And let’s not ignore the spam from ordinals boosting those fees.

I think the real issues are storage and propagation time. Bigger blocks mean longer propagation times, which is a killer for the network.

Absolutely, propagation is key. Storage isn’t even the main issue anymore. Miners aren’t just home setups anymore; they’re huge server farms.

So you think full nodes are the real bottleneck, not miners? That’s a different angle.

Yep, it’s all about how Bitcoin was designed. High fees are the goal to keep it secure once block rewards drop.

I’m with you on needing multiple methods to solve this. Mining pools should keep charging for non-standard transactions to keep things in check.

But if we increase block sizes, we risk breaking a lot of software. That’s a huge concern.

Some software will break anyway, and it’ll be a choice for people to upgrade or deal with it. We’ll face problems with timestamps eventually too.

I think the benefits of a hard fork might outweigh the issues in the future. We need to be ready.

Different from the 2038 problem, though. We know that’s coming and have time to fix it. The segwit merge isn't as urgent.

Totally agree, but hard forks need broad support. It's hard to imagine major changes getting that.