BitMinter arranged a mint race for the weekend. The finest quality minting work (best hash) will win. Start: friday 25.05.2012 at 20:00 UTC Finish: sunday 27.05.2012 at 20:00 UTC Prizes: 1st place: 10 BTC 2nd place: 4 BTC 3rd place: 2 BTC You will also get a gold/silver/bronze medal in the upcoming achievement system, similar to Stack Overflow and various gaming systems. Win conditions: Just like your hash must beat the difficulty to produce a block, it must beat the other miners to win. The best (lowest) 3 hashes during the race will win. As long as your work is accepted by the server it is valid for the race, even if it ends up "stale" or "orphaned" in the block list. Verifiability: Hopefully your mining software will show if you have created a block (the BitMinter miner does). Your block will show with your user name in the block list at http://bitminter.com/blocks. You can click the height number for the block (left most column) to see details. There is a link there to block explorer where you can see the hash value of the block both on the page and in the URL. The lowest hash value wins. Hash values are shown in hexadecimal. 0-9 is lower than A-F. A is lower than B. Pretty simple. If this is popular we will have more mint races later and a page showing current standings in the race. Final results: (updated 27.05.2012 at 20:03 UTC) | Place | Name | Hash (lower is better) | | 1, 10BTC | malavita26 | 000000000000062B2F28D5AA47F9C7EE05DCA83AD9EC16C5D72DA2DCF4D79ACE | | 2, 4BTC | zerogravity | 00000000000007BE233BD1BEA218B02FBBECA9A07EF7C3DF08F5D34C411F3776 | | 3, 2BTC | jeffklause | 00000000000008F37FB201315AD4061ECC1034D5E662C7425A15EE51945B47BB | | 4 | jakob | 0000000000000A9015D5057863097B4E1AB7902B83690A1E35B9FE76161301ED | | 5 | dextryn | 0000000000000C0D835681B6D4B92B12757440A34C40E28F4BC115A2AAC96483 | | 6 | Fefox | 0000000000000CC2560351C6724BF13B4E69AE4750246E61B741C1CC16F72EAB | | 7 | hartmining | 0000000000000E7EE05945C12801A6CC13A897C3575CB33C02E07DD6D4674019 | | 8 | jeffklause | 0000000000000F753C5D5F175C085BBC7762627E9522FA534570DBFB89D246BA | | 9 | dobo79 | 00000000000013B28A0894EF93EF8D28FE8D7461B4B049B1A7D4C40829C815E4 | | 10 | mqpickens | 0000000000001643957EC35EE0115B24F5363CAF12695EA0A442A6DCEDC22DC3 |
|
|
|
|
I'm having some trouble with cgminer telling me that "pool 0 not providing work fast enough" and hanging on that. Is there a way to fix this?
Not sure what the problem is. Are you using the latest version of cgminer? There are many using cgminer in the pool. Yeah, I was using the newest bit minter. I tried everything from putting as many flags as I could, to nothing at all. No core affinity to all core affinity.
Which GPU and which driver version? |
|
|
|
Doc, What is the theoretical limit for your server on hash rate at the moment?
It's been tested to 750 GH/s using GPUmax. It was barely breaking a sweat. So I know it handles 750 easily, but how high it can go I don't know. does anyone know which performs better bitminters miner or diablo for a 7970?
If you test it, I'd like to hear how it goes. I don't have a 7970 myself, but I have been told the miner runs well on them. Hashrate went up again for the fourth week in a row making Bitminter a middle tier pool. Another four weeks? Anyone want to bet on the probability of bitminter being a top tier pool by then?
That would be awesome.  Hopefully new users keep joining, and there are enough FPGAs ordered among users of this pool to double the hash rate we have now. |
|
|
|
Am I the only one that can't get this miner to detect the bitforce singles? I should mention that I did install the FTDI drivers, but I did _not_ reboot yet. Both miners work fine in MPBM though.
You clicked "devices->probe all ports" in the menus? Which OS are you on? |
|
|
|
|
I'd be interested in supporting this.
How similar are the APIs of Deepbit and Slush? Perhaps a standard can be based off of those.
|
|
|
|
Left 4 x 6970's mining and a BFL single mining overnight.
2781 accepted.
9440 rejected.
never has this issue with any other miner before.
I never heard of anyone having such an issue with this miner either. Is there anything in the log (text part of the window) to give a clue as to what went wrong? Perhaps network problems? Currently on my computer I have 317609 accepted and 46 rejected. That's 4 GPUs. BFL units seem to run a bit higher, roughly 0.3% rejected. |
|
|
|
Once I get openID, then I can save this in my documents so that I enter later without being log on google each time?
If you use Google as your OpenID provider to log into BitMinter then logging into the BitMinter website means logging into Google. Regards worker and password, I can choose any one I wish then?
Well, of course, I'll be sure to save this in my document
Yes, for worker name and password you can choose anything you like. You can store this with your miner and it will log in automatically and mine for you. OpenID is only needed for logging into the website. |
|
|
|
This is by far the best pool I have used. Just finished moving the last of my accounts from deepbit. Keep up the great work.
Thank you, good sir. That's good motivation to keep working on BitMinter, as is the hash rate going up so much lately. My singles are finally underway.
Winning!  Are there any plans to add namecoin to bitcoin direct conversion?
There are plans to add something along those lines. I can't promise when, though. |
|
|
|
Do you have an overview, how many singles and mini rigs are/will be there in the BitMinter network?
At least 4 mini rigs and a whole bunch of singles. There are also users mining with other FPGA devices and several people ordered the new Cairnsmore. I intend to add support for more FPGA devices in the future. First I would just like to get v1.2.0 out with BFL support. |
|
|
|
Getting 6x7970 for mining  I want to buy, 5xBFL Singles also, so, does anyone knows what are delivery times now? Nice, 7970s are efficient GPUs I think the delivery time for BFL singles has gone down, but I'm not sure how long it is now. Anyone have any recent info on that? It also appears registering for an OpenID isn't free!
Is there a way to register without an "openID"?
On bitminter doesn seem to make it easier!
There are many free OpenID providers. Actually, I haven't seen one that costs money, which one is that? I'd suggest using a Google account and activating 2-factor authentication on it. Then your account will be secured by a code in addition to password. The code can be generated by an app on your phone, or sent to you from Google by SMS or voice message at the time you are logging in. You don't have to pay anything for this. In case you lose your phone they have one-time codes you can print out and keep someplace safe. Now your account is protected by something you know (password) and something you have (your phone). This is much more secure than a simple username + password solution. The first time you log into BitMinter with Google there's a checkbox to allow automatic authentication. If you enable this and are logged into Google already then logging into BitMinter is just one click on the Google logo on the BitMinter login page. Your browser gets bounced over to Google then back to BitMinter. You are logged in after just a split second with only one mouse click. In case you don't like Google there is Yahoo and many others. For the future I may add username + password, Facebook login and possibly other solutions. However OpenID is secure, convenient and free, so new login solutions is not at the top of the priority list. Btw, for the mining itself you use worker accounts with passwords, just like any other pool. Miners send this password unencrypted across the internet, so don't use a password you use anywhere else (which is never a good idea anyway). |
|
|
|
So since it is showing expected average from the past months wouldnt the line not be straight, and be adjusted for when the difficulty changed? Right now the line seems to show "if the difficulty was always what it was today, then here is the expected average." But since in the past the difficulty was less the slope should be greater at those times. Or am i missing something?
The second chart is just the numbers from the first one added up. The yellow line in the second graph is actually slightly curved, but you can't see it with the naked eye. If you hit "view source" in the browser you can see the javascript function accumulate() that is used to add up numbers from the first chart to create data for the second. |
|
|
|
I ordered a mini rig today, let's see how fast they will get it to me.
Is Bitminter ready for such a device? shure hope so, otherwise I think we will make it work somehow.
Ready for testing...
There's one issue I'm still working on with the beta. It seems to not grab new work from the server fast enough. This will surely be a problem with a mini rig. But it will be fixed long before your mini rig arrives. Currently observed: Windows 7 with 8 singles shows slow work queue buildup but runs ok. Mac OS X with 10 singles ends up with an utterly depleted work queue and devices idling. A fix for this should be coming soon. Congrats on getting a mini rig! I think it's awesome that so many in the pool are getting singles and mini rigs. I aim to make the miner run as smoothly on them as possible. |
|
|
|
BTW, why don't the little "I" icons next to the worker settings do anything? I expected some popup help tips or something, but nothing. Maybe it's a bug, and they should be doing something? This was in the latest beta you posted.
You just mouse over them and get a tooltip. Hmm, perhaps I can also make it work to click them. EDIT: Also, I'm getting 380 MH/s on my 5870 through Bitminter (on the 5 ms interval), instead of 345 MH/s on guiminer, so that's a plus! Hopefully it'll work well enough for gaming, but can't try it right now.
Good times Overclocked? |
|
|
|
I adjusted the work interval UP. Will have to try adjusting it downward. So lower = slower then?
Between every work interval other programs get a chance to use the graphics card. So if the work interval is only 5 ms long, other programs don't have to wait too long to update the screen. This makes mining a little slower, but in my experience it's not that bad. |
|
|
|
Does anyone know if there is a way to change the time zone on the bitminter website from the default?
Sorry, you can't. Maybe I'll do something about that when I have time. For now all the dates are UTC. Why does the yellow "expected average" line keep going down on the rewards page. I've kept thinking it has gone down, but I distinctly remember the peak at the third graph line still being under the expected average line quite a few months ago.
Expected average reward for one proof of work is determined by difficulty. Rewards drop as difficulty go up. Hopefully the next time difficulty will go down and rewards will go up. Those charts only show the last 500 shifts. I should make it possible to move around in time on those charts when I have time. I tried adjusting the work intervals, but it didn't make any appreciable change.
I have work intervals set to 5 ms, and games mostly run ok without the need to stop mining. Have you tried values as low as that? |
|
|
|
I'll have 10 of them come Monday... with how much space each one takes up on the screen, a more condensed overview option would be nice!
Here's v1.2.0 beta 9. You can click the green arrows to switch between full and compact display for each device. New since beta 8: - Scan devices one by one to circumvent concurrency bugs in serial port library
- Raise priority of serial port I/O threads to improve performance during high CPU load. This should fix "command timed out" and "extranous data" errors. If the program is starved of CPU time you can still run out of work, see hash rate drop due to slow work dispatch and stales rise due to slow reaction time. Note if you are CPU-mining: run the CPU miner at low priority and/or not on all CPU cores.
- The start button of the "total" device display now starts only the visible devices instead of all devices the first time you click it. The next time you use it to start devices it will resume those you stopped with it, like it always did. The start button on the status bar is the same.
- Added minimize/maximize buttons on each device. The compact display is handy if you have a long list of devices. Remembered across restarts.
- Adjusted expected hash rate (green zone) for AMD Juniper GPU
- Fixed miner GUI bugs
 |
|
|
|
|
Thanks for testing it, SgtSpike. Glad you like it! The experience you are talking about is exactly the reason I made this.
Like you, many are now getting quite a few BFL singles. Also, I'm not sure whether the rig box will show up as a whole heap of devices. I will look into making an alternative display mode so it is easier to manage that many units. Coming in the next beta, hopefully the last before 1.2.0 goes out.
|
|
|
|
Awesome site! Very easy to use, got mining in no time!
Thanks!
Thank you - welcome to the team! |
|
|
|
v1.2.0 beta 8 is ready. Finishing up the BFL features. Added an identify button which will cause the BFL unit to blink its light. Will not work on the earliest BFL units. Someone let me know if the light actually blinks - I'm programming this remotely.  Added an awesome looking temperature display. If you'd rather have Fahrenheit than Celsius you can toggle that in the menu: View -> Use Fahrenheit. It will change the next time it checks the temp. There's a new setting in tune & tweak that lets you select at which point the temperature bar should go red and the little light (in the GUI) start to blink. Defaults: blink at 62 C, shutdown at 75 C. Not sure how good those settings are, but I read somewhere that the BFL singles throttle at 65 C, so they should be ok. This should make BFL support feature complete and take care of all known bugs.  |
|
|
|
Is this the first time the pool's had an orphaned block? I don't recall seeing one before.
There's one more orphaned block in the block history. But that was really a stale. There was a bug that caused it to still pay out to users. Also there has been a couple namecoin orphans I think. 18 BTC paid out to users who have the prepay perk on, 32 BTC lost for those who didn't. And 18 BTC lost for me. Please don't make any more orphans. |
|
|
|
|
Show Posts
