This is available for anyone. nonce2 is 6 bytes at BitMinter. You can create a subpool that has a 4 byte nonce2 and have up to 65536 active workers in your pool.

In the future the nonce2 size will be configurable by worker account. I just did this as a temporary fix to make subpools possible before the worker configs are available.

Seems there is already a fix for this.


To support sub-pools.


Bad luck - it happens.

No, nothing changed here. It may be a bug that happens rarely.

Hmm, looks like everything is working, except for the hashrate display. Very odd. I've never seen that happen myself. Maybe it only happens with Icarus/ASICminer devices. How often does it get stuck at zero that way? Might be a difficult bug to catch.

Looks like you set up a backup pool which is down. That's not a bitminter server.

The more hashrate the better the chance to get blocks. With a high hashrate pool you get several blocks per day, which means several small payments to you as a miner. Mining solo or in a tiny pool it might take months or even years of nothing before you got a big payment. Most miners prefer the low variance with frequent small payments.


Are there any log messages when this happens? That's the text area at the bottom.

Do accepted proofs of work still go up (the yellow boxes)? Or is everything just stuck, like the erupter hashrate staying at the exact same number instead of going slightly up and down like usual?

Does the device disappear from the client? That happens if the COM port the device is on disappears, for example if you unplug the device. If so, rescanning might help, to get it back again. If the hashrate just drops to zero and stays there, maybe it is because of the device not working properly.

Do you see any error messages in the log when these things happen? That's the text area near the bottom of the window.

If the block erupter is being fed lots of work but not finding any proofs of work for a while then the client will run a test to see whether it is still functional. It sends it work from which the device should return a known proof of work. If this is not happening or the proof of work is wrong it will try again a few times before giving up on the device. If that happens it means the device is consistently giving wrong results or not responding at all and something is wrong.

I'm currently working on idle worker notifications. Will post here when I get a little further and need testers.

Are you saying that if there is a problem fetching work from the server, then you have to reboot the computer to get BitMinter client hashing on your block erupters again? It should just start hashing again after it is able to get new work.

Have you tried setting automatic rescanning of the ports every minute or so? Does that help? I mean, instead of restarting the client to detect more devices.

Even if you have multiple computers you can use the same worker for all of them if you want. Multiple workers is for having separate statistics. So if you need that, set up multiple workers.

Namecoins:

We get namecoins with our bitcoin mining with no additional effort. Only got namecoins so far? You will get bitcoins when we create the next bitcoin block. Read more and get a namecoin wallet from http://dot-bit.org Get a namecoin GUI from http://dot-bit.org/forum/viewtopic.php?f=9&t=341 You can sell namecoins at exchanges: [1] https://btc-e.com/ [2] https://vircurex.com/

Hi,

nice to hear that you like the pool and miner

The really big guys are helping reduce variance for you. You don't need to "keep up" with other miners in the same pool. But you do need to keep up with the global hashrate if you don't want your mining income to drop as the difficulty rises.

I'd see it this way.. massive ASIC production causing the difficulty to skyrocket is bad for your mining income. But having a decent share of the global hashpower in our pool is good as it reduces variance.

If you want a lot of variance (which you would get in a pool with only small miners) then you could try solo mining. I wouldn't recommend it though. You could be waiting a year or two before you get anything at all.

Yeah, nice to see more and more miners are receiving their new ASIC hardware!


I think this is only for keeping tabs on your coins. There was a nice looking website for worker down notifications but I think they are pretty much dead. I'll have something on BitMinter, but no ETA yet.

Thanks! I'll add CryptFolio to the third party app list on the website with the next update

Cool site! Thanks for adding BitMinter support

We need a few more likes on Facebook to reach 1000: http://facebook.com/bitminter

Your expected payout for a block is calculated using your percentage of the work registered in the last 10 completed shifts. As your hashrate changes or the pool hashrate changes there will be some lag because 10 shifts take a while to finish. And after 10 new shifts are over, the hashrates have changed again.

If your hashrate and the pool hashrate did not change much the last day or so then it could be because you had some downtime. Have a look at the shifts page at http://bitminter.com/shifts to see how the 10 last shifts look. You have to be logged in to see your numbers for those shifts, naturally.

Are you overclocking?

Does the meter not show at all, or do you mean it only shows zero?

What about the hashrate on the statusbar at the bottom of the window, does that work?

Hi,

not yet

If cgminer crashing is the problem then have you looked at cgwatcher? https://bitcointalk.org/index.php?topic=159267.0

Yeah, Twitter changed their API. The new stuff is a pain, but I'll get it fixed.

Don't know yet, sorry.