For those who had problems getting the miner to run on Mac OS X; this was fixed in an update yesterday. This update also takes care of the errors that occurred when stopping and restarting GPUs on recent Catalyst versions.

Just quit and restart the miner to get the latest version.

If you don't mind mining at the BitMinter pool (and get 5% extra pay while promotion lasts), you could try the BitMinter miner. It's the fastest miner on 6990 right now.

If you try this miner and do a speed comparison, especially on multi-GPU systems, hit the little button in the lower right for performance mode. Otherwise all the screen updates can cause a noticable performance hit.

Update to website:
Member area "account details" now shows number of proofs of work for each worker for the current round, in addition to the total. Also, everything is summed up in the bottom row.

I also added a tooltip explanation for Mhps - just put the mouse pointer over the "Mhps" text in the column header to see it. Fluctuations in your hash rate should be less confusing when you know it's just an estimate.


That's great! We need to increase the hashrate to make payouts more frequent.

Always glad to hear reports of good performance.

To be honest, on a 5770 you can maybe get 1 MH/s higher with DiabloMiner or modified-Phoenix with modified-phatk kernel. I will be closing that gap later, to make this the fastest miner on any GPU. But for now, it's close enough to the best, while I work on some other things.

Yes, try 10 ms intervals - should be smooth.

No, it's an estimate (guesstimate, really), based on the number of proofs-of-work you are sending in. When you are lucky, it shows higher than actual speed. When you are unlucky, it shows lower.

I will add an explanation for this on the page - it's rather confusing.

Congratulations on the third block, everyone.

After the block was confirmed this morning, 79 members were credited for their work and also 5% bonuses added to their accounts. Shortly after that payments went out to 14 members whose accounts were now over their chosen minimum payout threshold.

Quick bugfix update on the BitMinter mining application today:
- Fixes errors that occurred when stopping and restarting a device
- Fixes "compilation error" on Mac OS X

Edit: To get the new version, just restart the miner.

Of course you are welcome. Fire up that GPU!

Norway right now: $0.09/kWh 

Hi Steamy - welcome to the team!

I have a lot planned for statistics and transparency, both very soon (today, I hope) and more in a couple of weeks. Stay tuned!

If you or anyone else have any questions, feel free to ask. Apart from myself we also have many members who can help, who are experts at all sorts of things.

Mhps added. No total yet, but that and more will come.

Great

Well, it wouldn't prevent DDOS attacks. It might make it a little more difficult for DDOS attackers to overload the server with getwork-requests. But it would also shut out honest miners who just prefer different software.

Yep. I noticed all the pools are almost the same, and that the miners could be improved. So I created a pool+miner combo that is different (better in my opinion) from the others out there. The pool works with other miners too, though.


It's just intended as a benefit for pool members. I don't plan to make it work with other pools, instead I plan to add extra pool-specific features when I get the time. Since I also wrote the pool backend myself it's easy to add new communication between pool and miner.

Bitminter shutdown notice

The Bitminter mining pool will shut down mining activities on 2020-07-01. The website will stay up until 2021-06-01 so you can cash out any crypto currency on your account.

It is unfortunate to have to shut down after 9 years of mining. However, to keep going would not be fair to the few miners we have left in the pool. The efforts of miners who have tried to keep the pool going is greatly appreciated. But the pool has shrunk so much that we might never find another block. Attempts to bring big miners onboard did not work out.

A big thank you to everyone who mined with Bitminter over the years. This has been a grand adventure.

The original purpose of Bitminter was to make mining accessible to those who found other mining software difficult to operate. For many of our users mining in this pool was their first experience with bitcoin. I hope you enjoyed it and that you are still part of the bitcoin community.

Hopefully Bitminter was a useful service for you.

Best of luck for the future.

Below is the original message that was posted here:



Bitminter mining pool has it's own custom miner.

Features of Bitminter client:

• Easy to use good-looking GUI
• Zero installation(!)
• Supported ASICs: Butterfly Labs (except Monarch), Block Erupter USB (and other Icarus-compatible), Chili, Red/Blue Fury, Antminer U1/U2
• Works on Windows, Linux and Mac OS X

No need to manually install it, and certainly no need to build/compile it yourself.

Try it now:

• 1. Fill in the pool sign-up form at https://bitminter.com/signup
• 2. Start the miner with "engine start" here or on our website (Java required)
• 3. Experience mining the way it should be

If two people owe you 10 BTC each, and you give them separate addresses to use when paying, it's easy to tell who it was if only one of them payed.

If you only ever use the same address you just see 10 BTC arrived.

Yep, this and more is coming soon. It will feel less "blind" with some more stats.

If you are mining in a pool with 8 GH/s, I think you'd be requesting about 2 new "getworks" per second, and sending in on average 2 new proofs-of-work per second. In addition is long polling. I guess this is several computers, so you'd have several long polling connections.

Let's say roughly that getting new work is about 800 bytes, sending 100 bytes to request it. Sending in proof-of-work means roughly sending 400 bytes and receiving roughly 100 bytes. Including both directions, about 2800 bytes, or 22400 bits per second. In addition there would be a spike at every block change, from the long polling connections. Sounds totally doable.

Some reasons a share (proof-of-work) may be rejected by a pool:

- it's built on stale data
- you already submitted the same share before
- it's invalid (GPU calculated wrong)
- it's built on data from a different pool

Only the first is really stale. But I think most miners and pool backends treat them all the same.

Are you talking about surviving botnets doing normal mining in your pool?  Or are you saying you can out-scale actual DDOS attacks?

Obviously it can help to scale up to mitigate the effects of a DDOS attack, but aren't many of the botnets so large that you can't out-scale them?

Should be easy enough to set up an SSH tunnel to your home computer and forward the miner connections through that.

But don't use the computer for mining if your employer does not condone with it. If you get fired it's not worth mining 5 BTC a month.