Create account

replied 2131d
I'm not acting like that, dicksnorter.
replied 2131d
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 2131d
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 2131d
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 2131d
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 2131d
I mean, seriously we had 8 MB blocks back like what? A few months after the hard fork in 2017? Two fucking years!
replied 2131d
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 2131d
Actually, I was underwhelmed by the pace due to the silly 2MB limit and Mr Unknown doing 1MB blocks.
replied 2131d
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 2131d
Frequent backlogs undermine 0-conf.
replied 2131d
Everyone should send emails ASAP.
replied 2131d
To where?
replied 2131d
To all the BCH pools
replied 2131d
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 2131d
I don't think that Roger checks memo frequently.
replied 2131d
I don't think that Roger checks memo.
replied 2131d
There was a post from his verified account recently.
replied 2130d
"a" post