Create account

· 49d
replied · 49d
Are you really implying that BCH needs more throughput to handle the current transaction load? Even BTC has been regularly clearing its mempool recently, no one is using crypto.
replied · 49d
No, I'm implying the network needs a higher soft limit to avoid shitting itself like it did over the weekend.
replied · 49d
Did the network "shit itself"? My transactions never had any problems clearing. I wouldn't have noticed this SV thing unless someone pointed it out.
replied · 49d
Based on my standards yes.

Check the following, this is what I fled from:

An this was BCH over the weekend:
replied · 49d
What do you mean, fled from? Would your transactions not confirm?
replied · 49d
I had a fair number of BTC transactions get stuck in late 2017/early 2018, even a few LTC txs, but I think it's hilarious that he's acting like this is typical in BCH lol
replied · 49d
I'm not acting like that, dicksnorter.
replied · 49d
People didn't call Maxwell "1MegGreg" until the cap caused serious problems

You're whining about Amaury over an adjustable softcap that pools forgot to change lol. You are *drunk*
replied · 49d
Look at #2MegSechet's responses. He flat out declined that the issue exists.

I know a group of devs where Sechet would fit in perfectly.
replied · 49d
If you want to bitch at the pools too, that's fine, I'll even support that effort. But your anger is completely misplaced, it's a fucking soft cap my guy
replied · 49d
The pools do seem to have been ridiculously lazy. We've had 2+ MB blocks for how fucking long now? And they STILL won't support them.
replied · 49d
I mean, seriously we had 8 MB blocks back like what? A few months after the hard fork in 2017? Two fucking years!
replied · 49d
Yeah I was thinking the default should be 8MB since that's what we forked to first, even 2MB shows that BTC needs to upsize blocks though, look how fast BCH chewed through 3 attacks
replied · 49d
Actually, I was underwhelmed by the pace due to the silly 2MB limit and Mr Unknown doing 1MB blocks.
replied · 49d
And I get that nothing should be seen as an attack, everything's just a test for the network, but with even half of pools mining bigger blocks the backlog dies very fast. Plus 0-conf
replied · 49d
Frequent backlogs undermine 0-conf.
replied · 49d
Everyone should send emails ASAP.
replied · 49d
To where?
replied · 49d
To all the BCH pools
replied · 49d
Well i think Roger Ver is here on Memo. I'm surprised he doesn't know or care, since apparently Bitcoin.com pool is doing this too.
replied · 49d
I don't think that Roger checks memo frequently.
replied · 49d
I don't think that Roger checks memo.
replied · 49d
There was a post from his verified account recently.
replied · 49d
"a" post
replied · 49d
sigh. Are you that green? I fled BTC because it was kept crippled artificially which lead to what you see on the pics.
replied · 49d
I'm a bit tired, yeah XD
replied · 49d


This is not organic lol. You're falling for troll talking points again, this is just another lame SV attack.

They try this every update, pay attention twat
replied · 49d
This would be "shitting itself" if this caused any problems, but the only goal was division, and you're the only one buying it. Turning from 1megGreg onto Amaury lol, you're the Judas