Setting a higher minimum difficulty or using the easy mining perk to reduce difficulty is only useful at very high hashrates. At 1 GH/s you can just leave it at the default.

That's a net split (IRC lingo). The bot and everyone else were still there, but they couldn't see you 3, and you 3 couldn't see them. Happens on IRC sometimes. People are talking in the same channel, but they are separated into different islands that cannot communicate.


It's not really about 3 days. It's about the amount of work and the difficulty. You can sum that up with CDF. The CDF is currently 99.77% which is very bad luck - but we have seen worse in the past.

It is statistically possible that the biggest pool never finds another block ever again. But it's extremely unlikely.

Someone who has 10 times more hashpower will get 10 times more. Someone who has lower electricity usage (better efficiency) or cheaper electricity will have lower expenses.

Three lucky days in a row. I hope you got some of that.

Yeah, that was just some general info. These devices are starting to appear (but sold by other companies than bitmine.ch?) and the software looks a bit broken.

If you have a Coincraft device, be careful what you set its difficulty to (in its own web interface). It will ignore the difficulty sent from the server and not send in work below the diff you set. You will only get credited for a fraction of your work. Whoever programmed this: this was NOT a good idea.

I don't actually have one of these myself. Anyone know anything more, let's hear it.

Bitminter client v1.6.0 is out.

New:

• Switch to Stratum mining protocol
• Show worker difficulty changes in the log
• Show the block's hash in the log when a block is found
• Remove display of queued work from status line (work now generated locally)

Try it now:


Note: if you were using the "port 80" option to bypass a firewall then this release will probably not work for you. v1.5.0 will still be available in the "tools" menu at bitminter.com for some time. If you have firewall issues, let me know what your needs are, or better yet, fix the firewall.

If you have a problem with 1.6.0 you can still load 1.5.0 from here: https://bitminter.com/client/1.5.0/bitminter.jnlp

If you restart the client and still see 1.5.0, try clearing your java cache. See http://www.java.com/en/download/help/plugin_cache.xml

You can do this today. Each has their own setting. Only problem is if they trade places, U1 on COM1 and U2 on COM2 originally. You set different speeds. Later for some reason the U1 is on COM2 and U2 on COM1, and the client will attempt to run them with wrong speeds. I think this will normally not happen if you keep them plugged into the same USB ports.

As far as I know the only difference is the larger heatsink on U2. I don't think there is a way for software to detect a difference.

That's because the "total" display that shows all the totals is the only one showing full information. The device displays are minimized. Press the green arrows to expand them and the wrench and other stuff will appear.

There are over 100 ASICMiner blades and cubes communicating directly with the Bitminter pool using the getwork protocol. This is not recommended as they will run at reduced speed. To get the most out of your blades/cubes you need to connect through a stratum proxy.

There are instructions on how to set up blades/cubes with a proxy here:
https://bitcointalk.org/index.php?topic=27062.msg3046129#msg3046129

Ask if you have problems setting this up. Get your blades and cubes running at full speed.

Good stuff. No network issues? Devices running out of work or connection issues?

It gives 1.5 until 1.6 is out of beta testing.

Bitminter client v1.6.0 beta1 is ready for testing.

New:

• Switch to Stratum mining protocol
• Show worker difficulty changes in the log
• Show the block's hash in the log when a block is found

Note: if you were using the "port 80" option to bypass a firewall then this release will probably not work for you. v1.5.0 will still be available in the "tools" menu at bitminter.com for some time. If you have firewall issues, let me know what your needs are, or better yet, fix the firewall.

Please check it out:

The carrot is the same with all pools. It's just a little further ahead of you with small pools.

Any documentation for these Stratum protocol extensions?

client.reconnect
client.add_peers
client.show_message
mining.get_hashrate
mining.get_temperature

Are there any other interesting extensions in use?

I don't understand what you mean. We are always mining for BTC. We never stop mining.

1.4.2 should connect fine.

Two reasons not to CPU mine:

1. It uses much more in electricity than what you earn. The more you mine, the more money you lose.

2. Like PCMiner just said, it is so slow that what you earn will probably never be more than "dust" which is not enough to withdraw.

And if you still want to CPU mine, don't use Bitminter client. The best CPU miners are 10 times faster. I never had time to implement fast CPU mining, and it doesn't make any sense now.

What happens when you try?

Does it help to clear the Java cache?

http://www.java.com/en/download/help/plugin_cache.xml


Yes, 1.5.0 is the latest version so that's the version you get unless you have been using a version-specific link.

Some work has 3 valid diff-1 nonces, and some has none at all. I haven't found a way to predict this without checking all possible nonce values though.