Actually it goes beyond being futile because mining with cpu and gpu shares nothing in common with modern mining of bitcoin and doesn't even teach you anything about mining. The CPU/GPU mining section of bitcoin is in the archived area of the forum. If you wish to mine altcoins and get help you can try in the altcoins section. If you continue to post about this in bitcoin your thread remains irrelevant in the bitcoin mining section and a moderator will eventually consider it offtopic enough to move to the archive area.

We seem to not be communicating here. You asked "Is this not something developers should sort out" and I'm telling you they can't.

The developers cannot dictate.

No. You cannot dictate what transactions are included at all, only what rules they must abide by. To do so would require a hard fork and mandating what transactions will be going in would be an extremely unpopular move and suicide for a cryptocurrency that is trying to be open.

Default rules in bitcoin core with segwit enabled bias towards segwit transactions by counting the amount of block space they use and since their signature verification is no longer in the block they are substantially smaller than traditional transactions (up to 4x) so if they use the default bitcoin core implementation they will bias towards segwit transactions by default. However there is absolutely nothing that says what any pool must include or how they must bias their transaction choices, so long as the transactions are valid by current rules - most pools run custom bitcoin daemons already and they probably have their own custom rules.

I know, right? But it gave me an excuse to call all the people I have on ignore morons.

Then all you've really done is create yet another thread like all the other ones I'm afraid. They all end up looking the same.

Why on earth did you start a thread trying to dispel the nonsense of the march of the full time anti-core propaganda trolls and not make the thread self-moderated, hence inciting the very same morons back to post here?

The pool has now registered over 150 unique users, 131 of which have contributed hashes. Hopefully people are only using the one username as I've recommended which would imply quite a few people have tried mining here.  Only a much smaller proportion have been mining consistently and continue to mine now and obviously we need more hashrate more than we need more users but it's reassuring to see more people trying it out. Let's bring down that first block so I can stop labelling the pool beta and that will hopefully bring more miners too.

It's just peoples' familiarity with banks "taking care" of their money for them, which is ironic considering bitcoin is meant to abolish the need for banks...

All mining pools use stratum for communicating these days. The stratum spec indicates that an update must be sent out within 2 minutes. Most pools send out updates every 60 seconds (ckpool based ones every 30 seconds).  With each stratum update the block time is updated to the local clock time. Some mining hardware still rolls this time forward to increase the range of data it can hash without creating more base work to hash off, thus the time is artificially moved forwards - though this is less common these days. The bitcoin protocol allows time to be up to 10 minutes before and 2 hours after the current time which is why the rolling forwards is done. Thus the time in the block is only weakly correlated with the true time at best, and can be sometimes a long way off. Some blocks even have a time in the past compared to blocks that are mined before them.

Are you checking workers? The workers page has been removed. Everything has been moved into the users pages.

Sorry about that, they should repopulate. I still need to debug what went wrong in the first place to prevent it happening again on the next restart as well.

The DE server is currently having issues and I've lodged a technical support request. Please aim miners directly at the main pool in the interim which is unaffected.
DE is back online.

Which was the point of my post... likely the bulk of them out there are still vulnerable.

Additionally I happen to know that certain functionality only existed on the first S9 firmware and many users are reluctant to change from it.

Intermediate sized miner that hasn't been mining long!


https://www.blocktrail.com/BTC/block/0000000000000000019c420cbea0a5cd1c9008ab45b9e887d6c3ce1fb3c9cafc

No problem. Never fear, your shares and HERP will be here for when you get back.

There's ~200TH from one user that comes and goes according to rentals etc. of his equipment which will not always be there which you're probably counting.

I had counted on a larger miner who had said he would bring about 2PH when this pool was in the planning stages by the end of this month and was one of the reasons I was more interested in starting the pool up. However that appears to have fallen through since he's gone silent (which doesn't surprise me; most promises I've seen like this don't last ) so we have to get the hashrate up the slow and steady way.

It's not a matter of "come back" since they never were here in the first place. The higher hashrate was nothing but early rentals from a very small number of people. If anything, the number of users on here is more than ever. Establishing a new pool from scratch and getting enough hashrate in this day and age is freaking hard, especially since most mining operations have fixed pools they mine at (mostly the Chinese consortium) leaving hardly any to select a pool the old fashioned way themselves.

Pool's up to 50% diff this block. Hang in there and let's crack this thing to consider the pool stable instead of beta and move onto the next stage.

Except for mining the opening and closing transactions which is still done by miners and broadcast as regular transactions by nodes.

I think you found the 2 blocks before I implemented the best ever statistic so there's no record of it

Yes diff is pool percent of current network diff as OSM said.