Any word on when/if you'll implement merged mining support?
Topic: [CLOSED] Semi-private mining pool - page 26. (Read 53242 times)
Also, the annoying bug that only happened in Safari when setting up your OTP has been squashed.
Feel free to use Safari to your hearts content.
Feel free to use Safari to your hearts content.
Pool is back to normal. Sorry for any heart palpitations. 
Post mortem is basically shift creation stopped sometime this morning and needed more memory to do it's job. New server is in place and working has expected.
Post mortem is basically shift creation stopped sometime this morning and needed more memory to do it's job. New server is in place and working has expected.
Is something wrong with the graphs? It shows everything at 0.
Apologies. Background tasks are down right now while I fix an issue with shift creation.
Please also note we do not have any orphans for today and that those blocks are on hold for payout until I am completed.
Things should be back to normal soon.
Whew. 2 orphans in a row, on a lean day was looking mighty sad.
Is something wrong with the graphs? It shows everything at 0.
Apologies. Background tasks are down right now while I fix an issue with shift creation.
Please also note we do not have any orphans for today and that those blocks are on hold for payout until I am completed.
Things should be back to normal soon.
Is something wrong with the graphs? It shows everything at 0.
1229 258,409 1 minute smracer 25.28430317 112,628,548 530,582,880 11h 43m 18s 54.00Th/s 1 99.10%
LOL!
LOL!
Thanks for taking care of that one...
1229 258,409 1 minute smracer 25.28430317 112,628,548 530,582,880 11h 43m 18s 54.00Th/s 1 99.10%
LOL!
LOL!
Someone needs to bitch slap this round.
3 solid hours and 0% reject rate *knock on wood*
Great job Giga!!!
old vs new:
Great job Giga!!!
old vs new:
Over what period of time is the worker 'speed' determined on the worker page? My BF rig is showing 370-400 GH/s after 1.5 hrs. Was showing 490-500 on EMC.
Thanks.
Thanks.
All of the displayed speeds are over a 30 minute window. Your worker is currently showing a speed of 491.12Gh/s.
Please also remember that we target 12 shares a minute unlike most pools that target 20-24 shares per minute. This increases share variance a bit so you will see bigger swings around your actual hash rate.
I'm running at 12.96Th/s and can swing from 13.2Th/s down to 12.6Th/s pretty easily. Over a 2 hour period though, this noice is mostly gone.
It's happy now. I reset the miner and stratum proxies and set the min diff to 512. The stratum jobs still show 256 diff, but the pool is showing ~500GH/s so, I'm happy!
Thanks again for fixing things for the BF crowd.
Over what period of time is the worker 'speed' determined on the worker page? My BF rig is showing 370-400 GH/s after 1.5 hrs. Was showing 490-500 on EMC.
Thanks.
Thanks.
All of the displayed speeds are over a 30 minute window. Your worker is currently showing a speed of 491.12Gh/s.
Please also remember that we target 12 shares a minute unlike most pools that target 20-24 shares per minute. This increases share variance a bit so you will see bigger swings around your actual hash rate.
I'm running at 12.96Th/s and can swing from 13.2Th/s down to 12.6Th/s pretty easily. Over a 2 hour period though, this noice is mostly gone.
Final Pool Update
I have reduced the minimum difficulty to 25 for the time being and have cleaned up the worker creation page to put the right default values.
As before, old workers are grandfathered in until they are updated.
I have reduced the minimum difficulty to 25 for the time being and have cleaned up the worker creation page to put the right default values.
As before, old workers are grandfathered in until they are updated.
Over what period of time is the worker 'speed' determined on the worker page? My BF rig is showing 370-400 GH/s after 1.5 hrs. Was showing 490-500 on EMC.
Thanks.
Final Pool Update
I have reduced the minimum difficulty to 25 for the time being and have cleaned up the worker creation page to put the right default values.
As before, old workers are grandfathered in until they are updated.
I have reduced the minimum difficulty to 25 for the time being and have cleaned up the worker creation page to put the right default values.
As before, old workers are grandfathered in until they are updated.
With some help from Morblias we have verified that the pool is now ready for Bitfury miners.
Use the invite feature to bring over some friends with miners of the Eastern European persuasion!
Use the invite feature to bring over some friends with miners of the Eastern European persuasion!
Not on IRC but initial impression positive. Very low rejected shares, similar to other ASIC devices.
Yeah!
Yeah!
Thanks for the quick reply and feedback!
Pool UPdate
I believe that the bitfury / stratum proxy issue is resolved. What has happening is that when you would authorize, your diff would get set to something higher than the pool default of 4. Then, a subscribe would happen setting your miner to a diff of 4, which is obviously not correct. I now check to see if authorized was called first, and if so, we do not broadcast the pool default minimum difficulty.
I've also stopped checking for passwords for workers so any password willl work.
If someone is watching this thread, has a Bitfury miner and is on IRC, hit me up for some final testing.
I believe that the bitfury / stratum proxy issue is resolved. What has happening is that when you would authorize, your diff would get set to something higher than the pool default of 4. Then, a subscribe would happen setting your miner to a diff of 4, which is obviously not correct. I now check to see if authorized was called first, and if so, we do not broadcast the pool default minimum difficulty.
I've also stopped checking for passwords for workers so any password willl work.
If someone is watching this thread, has a Bitfury miner and is on IRC, hit me up for some final testing.
Not on IRC but initial impression positive. Very low rejected shares, similar to other ASIC devices.
Yeah!
Pool Update
I believe that the bitfury / stratum proxy issue is resolved. What has happening is that when you would authorize, your diff would get set to something higher than the pool default of 4. Then, a subscribe would happen setting your miner to a diff of 4, which is obviously not correct. I now check to see if authorized was called first, and if so, we do not broadcast the pool default minimum difficulty.
I've also stopped checking for passwords for workers so any password willl work.
If someone is watching this thread, has a Bitfury miner and is on IRC, hit me up for some final testing.
I believe that the bitfury / stratum proxy issue is resolved. What has happening is that when you would authorize, your diff would get set to something higher than the pool default of 4. Then, a subscribe would happen setting your miner to a diff of 4, which is obviously not correct. I now check to see if authorized was called first, and if so, we do not broadcast the pool default minimum difficulty.
I've also stopped checking for passwords for workers so any password willl work.
If someone is watching this thread, has a Bitfury miner and is on IRC, hit me up for some final testing.
Awesome. Thanks for all the work on the pool.
Did you get the stratum server issue fixed? My 500GH bitfury is itching to move over.
Did you get the stratum server issue fixed? My 500GH bitfury is itching to move over.
* gigavps reboots into ubuntu to work on the stratum proxy issue....
Pool Updates
I've made some updates to the pool today.
Using the invite a friend feature at the top right of any page and you will be shown a registration link that you can send to your friends. We've lost some ground in keep up with the overall hash rate of the network and it is time that we changed that.
If you want less variance, then send some invites out and lets get the pool to 100Th!
I've made some updates to the pool today.
- Upgraded bitcoinds to 0.8.5
- There are new API calls for all payments and all rewards
- There was a bug introduced in the security area for resetting your password that jimbit pointed out. It has been fixed.
- Little hiccup with a block this morning was corrected.
- Added the ability for current pool members to invite up to 10 of your fastest hashing friends.
Using the invite a friend feature at the top right of any page and you will be shown a registration link that you can send to your friends. We've lost some ground in keep up with the overall hash rate of the network and it is time that we changed that.
If you want less variance, then send some invites out and lets get the pool to 100Th!
Awesome. Thanks for all the work on the pool.
Did you get the stratum server issue fixed? My 500GH bitfury is itching to move over.
Jump to: