The site is showing some odd data  RE: orphaned blocks at the moment due to a rescan happening on the hot wallet server.  Will fix itself once the rescan is complete.

Same users.  Before the full scope of what was happening to BTC Guild was made clear, I informed many other pool operators of the addresses for accounts I was freezing in relation to the block withholding.  We were in discussion about withholding vectors already from the abnormally low luck that Eligius and BTC Guild both had in March and April respectively.

A brief (2 hours or less hopefully) maintenance is happening on the hot wallet due to today's failed payouts.  There is an unconfirmed payout that is "stuck" currently, attempting to be done twice.  The hot wallet is being rebuilt which will correct the issue.  The concern is if another payout is prepared that uses the stuck transaction as one of its inputs, it could cause a chain of transactions which may never confirm.

Another post will be made when the maintenance is complete.  This maintenance has no effects on the pool's block solve rate (the mining servers have zero communication with the wallet server).

A few withdrawals failed this morning because a user kept an obscenely high balance and withdrew it all at once, emptying the hot wallet.  It's being refilled now and the failed withdrawals will be pushed through.

Once they've been notified of the private pool they are able to use it indefinitely.  It's purely a barrier to entry in order to keep it from becoming too public and forcing me to make the "Super Elite Invitation Only" Private Server.

So your suggestion is another pool(s) should spend likely tens of millions building yet another massive private warehouse of mining chips and then RIP OFF CUSTOMERS like GHash does by charging more in BTC than the hash rate will ever produce?


"Cloud miners" are perfectly able to mine on other pools.  GHash.io isn't cloud mining, it's more like putting money into bonds with negative interest rates.

It's a variable speed requirement based on recent hash rate (both user and pool).  The private servers are isolated from public servers for DDoS protection.  Similar to how during the last major attack, users were receiving notifications of alternate DNS that pointed to "semi-private" servers, except these are given out in advance to high hash rate users.

If you have 15 Th/s and put it on the pool, it will notify you for private server information.  I don't respond to private server requests over the forum because of how many times it has been hacked.

6 blocks in 10 minutes has happened a few times before, just like 0 blocks in 60 minutes happens about once a month.  6 in 10 minutes is a bit rarer though.

It will take you ~18,263 days to solve a block with  32 GH/s, assuming difficulty is static.  It can take you 8, 9, 10 times longer than that, or it can take you 1 second.  On average, 18,263 days @ 32 GH/s.  This is based on current network difficulty and assuming (wrongly) that it will not change at all during that time.

Plug your speed into any mining calculator (https://www.alloscomp.com/bitcoin/calculator).  Look at the per day earnings.  Divide 25 by that number.  That's approximately how many days it will take you to solve a block at the current network difficulty assuming it never changes.


You'd be better off selling slow hardware for scrap metal and buying scratch & win tickets than trying to solo mine.

Considering the sound of the concept, that fee is probably right.  No large miners would do this, just small ones.  You'd probably be paying for months worth of servers between each block.  And small miners use just as many resources as large ones, so you can't just throw them on a cheap one.

It would be a lot smarter for miners with obsolete hardware to just sell it for whatever somebody is willing to pay for it and buy lottery tickets.  They're more likely to get something out of it than solo mining.

You've been credited for 13.  You had previously been credited for 7, as pointed out above in the explanation by me and the one by Sir Alan (thank you for that Sir Alan).

6 more were found in the most recent shift (4:01 AM - 5:00:59 AM), which were not credited until that shift completed (8 minutes before your most recent post).

Again...read what you quoted.  I know I edited it to add an even more thorough explanation, but even what you quoted clearly shows where your math is wrong.  You're counting the blocks twice.  They are not separate blocks.  There have only been 7 GLC blocks found in total during the period you're looking at.  Not 10-16.

I'm not dilluting your question.  The problem is you're thinking the pool has found twice as many blocks as it actually has because you're counting the Blocks Paid on each shift as if they are separate blocks when they're actually the exact same blocks split over the 5 previous shifts (though the reward was actually only paid to those two shifts, since there were no shares to award in the 3 prior).

The 5 blocks were found during shift 2907.  The pool takes the shares submitted to 2907, 2906, 2905, 2904, and 2903 for that coin as the total shares to split the reward across.  In this case, that would be the shares you submitted in 2906 & 2907, assuming you were the only user to submit shares to that coin (which seems to be the case since there were 0 shares in 2903-2905 for that coin).

2 more blocks were found during shift 2908.  The reward for these blocks was split for Shifts 2904-2908.  Like before, since there were no shares for that coin in 2903-2905, the actual split only counted shares in 2906-2908, which were all yours.

EDIT: Fixed 2907/2908.

You don't seem to understand how PPLNS works...there were not 10 different blocks originally and 4 more later.  If a block is solved, it's paid to the previous 5 shifts.  So that 1 block will show up under Blocks Paid to all 5 shifts.

This has never happened.  They have made no changes or any efforts to limit their speed.  The made a very poorly made post about their plans, which included such things as letting cloud miners pick a different pool, which is *EVEN WORSE* since that means their share of the network is unknowable.

Uhmm...your entire first bit is completely wrong.  The shares do not come more easily or take any more time to calculate at any point during the round.  Score based payment is purely a way to discourage people from leaving the pool, by making your previous work worthless.  The work done is no harder at any point in a round.

The slush payment method is hoppable, though not as badly as the old proportional systems.  However, the concept of pool hopping to increase profits is basically dead since there are no pools large enough with a hoppable method to make it worth the trouble.

NMC is SHA256...if you want that, go mine on BTC Guild which merged mines it.  FTC isn't supported because I have no interest in implementing proof of stake coins which are not compatible with the current backend.


More coins are coming when the pool is updated this month to force auto conversions and remove the per-coin share recording.

Well, he has a point.  We haven't had any LTC blocks in about 17 hours.  Not that it means much.  We had extremely good luck with LTC blocks the other day.

Of course the comparison of how many blocks per shift changing means *nothing* on a multipool.  A single LTC block is worth probably 1000 LOT or CSC blocks.  The pool has been mostly focused on DOGE and LTC for the last 24 hours, so while the # of blocks paid to each shift will be much lower, they're worth much more than if we tacked on an extra 50-100 LOT/CSC blocks to each shift.

If there was any actual downtime expected, a 24h+ window would have been provided.  For properly working miner configurations/hardware, the restart was virtually transparent.