Yikes. All the more reason to promote self custody. I'd be sad if I lost my savings because I didn't respond to a Coinbase email.

Reply to this note

Please Login to reply.

Discussion

Self custody will not matter if the mempools and chain get spammed to oblivion and it’s 100k sat v/B to transact.

You don't have to fud so hard. That scenario is so unlikely.

Maybe you are unaware but at one point in time satoshi dice 🎲 made up 96% of the transactions/ blocks.

The dust limit was conceived as a way to filter the spam.

History doesn’t repeat but it rhymes.

This is not fud look at how high fees went during the ordinal craze.

Should I respond with another random link with no context or what?

No

Don’t worry when that happens we’ll get bigger block’s finally

Segwit resulted in 4x the block size and is partially the reason we find ourselves in the situation we are in today. The average block size this epoch so far is about 1.6 MB. Miners are trying to figure out how they can fill up the block space. Shitcoiners are trying to solve this by minting shitcoins on Bitcoin.

Right back on your horse, eh puz?

This is 100% what is going to happen. The miners have to be in on this shit. It’s just too easy to see through this crap. I wonder Who’s getting paid?? I don’t care if it’s consensus or functionality. It’s BS

I’m not sure I get the meme. Would miners not want an unlimited op_return so the data stays in the witness block?

Miners want unlimited data because it makes the block space more limited and hence the fee per Vbyte more and they make more $$. Also if they need to do these out of band. They can charge a premium.

Yeah let’s get 2 mb blocks & Segwit 2x

If segwit never happened you'd be screaming for it meanwhile complaining about fees.

Thank God for LN.

What the fuck are you talking about?

The average block size is slightly over 1MB why would I be screaming for larger blocks?

Blocks would be full and miners wouldn’t be conspiring with Bitcoin core to make mempool policy changes.

Don’t fucking tell me what I would be for or against. You are acting like a shitcoiner trying to put words in my mouth. If you have a question ask.

I'm only adding to the conversation for people who think segwit was a mistake.

Stop being so insecure, sheesh.

I get worked up on this issue because it’s being downplayed by the influencers and rammed down node runners throats

I feel you my g, no hard feelings from me ever 💗🤟

schnorr signatures (as used in taproot) were on offer at the time, and it was my opinion it was the better option for solving the tx malleability problem back in 2017

and now we have them, but they rape it with this other shitcoin "taproot" bullshit you can't just do a schnorr signature, you have to hash your secret key and then use that. efficiency :vomit:

And this is why we choose our nodes carefully, right?

That won't happen, because spam has no value

But it has happened and still does. we saw crazy crap hitting the mempools already.

It never lasts very long though. People get tired of burning money eventually

This is true. I’m still confused by the whole thing and trying to figure it out. I was asking chatGPT to tell me the positive and negatives to both sides yesterday lol

Same here, it's way above my pay grade

The point is that NO CONSENSUS has been reached in favor of the change. Which means it should not be forced in the github. Only when changes are already adopted by the network (like RBF was) after that they should change the default settings. This forcing and "we know better" attitude is a serious departure and I don't think we are making this a big enough deal.

I would agree.

You aren’t thinking from an attacker point of view. If money isn’t a problem and their goal is to throttle the network throughput they would make it expensive and difficult to transact.

They can already do that by sending legitimate transactions back and forth between wallets

Right but they need to construct thousands of tx per block instead of dozens

I don't see that that makes a difference, they're paying per byte right?

Would you rather have to construct billions of transactions or tens of thousands if your goal was to slow things down?

Spammers don't care, their whole deal is sybil attack.

To be clear, I have no idea which side of this whole debate I land on. I strongly resonate with nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg7waehxw309ahx7um5wgkhqatz9emk2mrvdaexgetj9ehx2ap0qy88wumn8ghj7mn0wvhxcmmv9uq3zamnwvaz7tmwdaehgu3wwa5kuef0qqs8fl79rnpsz5x00xmvkvtd8g2u7ve2k2dr3lkfadyy4v24r4k3s4sngrqr5's argument that bitcoin is money and should be treated as such. But I also see the point that accurate mempools help with fee estimation, and we can't stop spam in any way other than by forcing spammers to pay for block space. Getting rid of the segwit discount seems like a clearer win to me, but the cost of putting things in OP_RETURN is much fairer and has obvious uses.

You will never achieve "accurate" mempools. think about it. everyone has different settings, only 5% of nodes today run the latest software.

Core always followed consensus. Now they are forcing it. This is a war.