Hi,
i would like to have an 3h and 12h avg hashrate table for each worker how eligius. this would be very usefull for the miner controll.
Topic: [CLOSED] Semi-private mining pool - page 7. (Read 53242 times)
Very good improvements, now I can finally get some rest 
Development Update
By popular request, we have added more notifications to let you know what is going on with your workers. There are now 4 possible notifications:
The new low hashrate notification works off of your 5 minute hashrate average. If you are submitted 20 shares per minute (hashrate of worker / 1.4) this should an acceptable time range. If you have set your diff higher, please be aware that your 5 minute average will swing back and forth more than if you submit 20 shares per minute.
Big thanks to jddebug for kicking my ass into gear on this one.
Best,
James
Thank you, very nice. By popular request, we have added more notifications to let you know what is going on with your workers. There are now 4 possible notifications:
- Idle worker notification - same setting on each worker as before - email title has changed in case you forward these emails somewhere.
- Worker recovery notification - if you are subscribed to Idle notifications, the system will now tell you when your worker has recovered.
- Low hashrate notification - this is a new setting for each worker. Once checked, a text field will appear for you to enter the threshold in Mh/s.
- Hashrate recovery notification - if you are subscribed to low hashrate notifications, you will be alerted when the workers hashrate exceeds the threshold.
The new low hashrate notification works off of your 5 minute hashrate average. If you are submitted 20 shares per minute (hashrate of worker / 1.4) this should an acceptable time range. If you have set your diff higher, please be aware that your 5 minute average will swing back and forth more than if you submit 20 shares per minute.
Big thanks to jddebug for kicking my ass into gear on this one.
Best,
James
Add to wish list:
User defined auto-logout time or something that could be done with a cookie if you want to stay logged in, like on a tablet.
Development Update
By popular request, we have added more notifications to let you know what is going on with your workers. There are now 4 possible notifications:
The new low hashrate notification works off of your 5 minute hashrate average. If you are submitted 20 shares per minute (hashrate of worker / 1.4) this should an acceptable time range. If you have set your diff higher, please be aware that your 5 minute average will swing back and forth more than if you submit 20 shares per minute.
Big thanks to jddebug for kicking my ass into gear on this one.
Best,
James
By popular request, we have added more notifications to let you know what is going on with your workers. There are now 4 possible notifications:
- Idle worker notification - same setting on each worker as before - email title has changed in case you forward these emails somewhere.
- Worker recovery notification - if you are subscribed to Idle notifications, the system will now tell you when your worker has recovered.
- Low hashrate notification - this is a new setting for each worker. Once checked, a text field will appear for you to enter the threshold in Mh/s.
- Hashrate recovery notification - if you are subscribed to low hashrate notifications, you will be alerted when the workers hashrate exceeds the threshold.
The new low hashrate notification works off of your 5 minute hashrate average. If you are submitted 20 shares per minute (hashrate of worker / 1.4) this should an acceptable time range. If you have set your diff higher, please be aware that your 5 minute average will swing back and forth more than if you submit 20 shares per minute.
Big thanks to jddebug for kicking my ass into gear on this one.
Best,
James
Problem is still there. Possibly related to the initial lowest diff of 25?
The previous diff is only good for the current work template id. If your diff is adjusted AND new work is sent, the pool expects higher diff shares.
Is this not correct?
EDIT: To clarify, I've only seen that once since your fixes.
Problem is still there. Possibly related to the initial lowest diff of 25?
The previous diff is only good for the current work template id. If your diff is adjusted AND new work is sent, the pool expects higher diff shares.
Is this not correct?
Problem is still there. Possibly related to the initial lowest diff of 25?
Code:
[2013-11-06 23:33:17] Accepted 09748d54 Diff 27/25 BAS 0 pool 0
[2013-11-06 23:33:19] Accepted 04beb37b Diff 54/25 BAS 0 pool 0
[2013-11-06 23:33:19] Accepted 078ad6aa Diff 34/25 BAS 0 pool 0
[2013-11-06 23:33:19] Accepted 063eb1e5 Diff 41/25 BAS 1 pool 0
[2013-11-06 23:33:19] Accepted 09695c59 Diff 27/25 AVA 0 pool 0
[2013-11-06 23:33:20] Accepted 05cec45a Diff 44/25 AVA 0 pool 0
[2013-11-06 23:33:20] Accepted 027e8729 Diff 103/25 BAS 1 pool 0
[2013-11-06 23:33:20] Accepted 01152354 Diff 236/25 BAS 1 pool 0
[2013-11-06 23:33:20] Accepted 01b52dc9 Diff 150/25 AVA 0 pool 0
[2013-11-06 23:33:21] Pool 0 difficulty changed to 75
[2013-11-06 23:33:21] Accepted 027b1e38 Diff 103/25 BAS 0 pool 0
[2013-11-06 23:33:21] Rejected 0a23a6b7 Diff 25/25 BAS 1 pool 0 (Share is above target)
[2013-11-06 23:33:22] Rejected 03dc2e8a Diff 66/25 AVA 0 pool 0 (Share is above target)
[2013-11-06 23:33:22] Rejected 046d7b1a Diff 58/25 BAS 0 pool 0 (Share is above target)
[2013-11-06 23:33:23] Rejected 05767d65 Diff 47/25 AVA 0 pool 0 (Share is above target)
[2013-11-06 23:33:23] Rejected 088ee26b Diff 30/25 AVA 0 pool 0 (Share is above target)
[2013-11-06 23:33:24] Rejected 0832a7f6 Diff 31/25 BAS 0 pool 0 (Share is above target)
[2013-11-06 23:33:26] Accepted 01240438 Diff 224/75 BAS 0 pool 0
[2013-11-06 23:33:26] Accepted 02cd067a Diff 91/75 BAS 0 pool 0
Hi, you're not associating diff properly in stratum and after diff rises you are rejecting valid work as hash being above target.
I have updated the pool servers to make sure all diff change notifications allow for the previous diff to still be accepted.
Code:
[2013-11-05 15:30:42] Accepted 02382ffe Diff 115/75 BAS 6 pool 1
[2013-11-05 15:30:42] Accepted 02ad696d Diff 95/75 BAS 7 pool 1
[2013-11-05 15:30:42] Accepted 02a84b41 Diff 96/75 BAS 2 pool 1
[2013-11-05 15:30:44] Pool 1 difficulty changed to 225
[2013-11-05 15:30:44] Accepted 02353e00 Diff 115/75 BAS 1 pool 1
[2013-11-05 15:30:45] Accepted 031dfab3 Diff 82/75 BAS 1 pool 1
[2013-11-05 15:30:47] Accepted 014dc656 Diff 196/75 BAS 2 pool 1
[2013-11-05 15:30:51] Accepted 00f4e8f4 Diff 267/225 BAS 6 pool 1
[2013-11-05 15:30:54] Accepted 003f2be8 Diff 1.04K/225 BAS 4 pool 1
As we can see from the cgminer output above, diff 75 shares were still accepted even after the pool suggested raising the diff to 225.
Hi, you're not associating diff properly in stratum and after diff rises you are rejecting valid work as hash being above target.
I have updated the pool servers to make sure all diff change notifications allow for the previous diff to still be accepted.
Code:
[2013-11-05 15:30:42] Accepted 02382ffe Diff 115/75 BAS 6 pool 1
[2013-11-05 15:30:42] Accepted 02ad696d Diff 95/75 BAS 7 pool 1
[2013-11-05 15:30:42] Accepted 02a84b41 Diff 96/75 BAS 2 pool 1
[2013-11-05 15:30:44] Pool 1 difficulty changed to 225
[2013-11-05 15:30:44] Accepted 02353e00 Diff 115/75 BAS 1 pool 1
[2013-11-05 15:30:45] Accepted 031dfab3 Diff 82/75 BAS 1 pool 1
[2013-11-05 15:30:47] Accepted 014dc656 Diff 196/75 BAS 2 pool 1
[2013-11-05 15:30:51] Accepted 00f4e8f4 Diff 267/225 BAS 6 pool 1
[2013-11-05 15:30:54] Accepted 003f2be8 Diff 1.04K/225 BAS 4 pool 1
As we can see from the cgminer output above, diff 75 shares were still accepted even after the pool suggested raising the diff to 225.
still problem
with payment
with payment
Hi, you're not associating diff properly in stratum and after diff rises you are rejecting valid work as hash being above target.
EDIT: Relevant link:
https://bitcointalksearch.org/topic/m.1344456
Also resume support would be nice.
EDIT2: Relevant link:
https://bitcointalksearch.org/topic/m.1557099
Code:
[2013-11-05 13:06:01] Accepted 0203f2e6 Diff 127/113 AVA 0 pool 0
[2013-11-05 13:06:06] Pool 0 difficulty changed to 339
[2013-11-05 13:06:08] Rejected f5d0ee6e Diff 267/113 BAS 0 pool 0 (Share is above target)
[2013-11-05 13:06:11] Accepted 96897334 Diff 435/339 BAS 1 pool 0
https://bitcointalksearch.org/topic/m.1344456
Also resume support would be nice.
EDIT2: Relevant link:
https://bitcointalksearch.org/topic/m.1557099
Yes. 5% for all members. PPS is very dangerous to a pool - big risk - which is why high fees.
My pool will be the first to keep coins at a specific address, sign a message stating we own the coins AND show the calculations for our risk of ruin to PROVE we can run a legitimate PPS operation. Users can be rest assured that any bad luck the pool experiences is backed 100%.
Pplns is free of fees???
PPLNS runs at 0% fees.
PPS runs at 5% fees.
This is all stated on the OP in this thread.
Pplns is free of fees???
So better paid per pplns?
Better than pps??
Better than pps??
Yes. 5% for all members. PPS is very dangerous to a pool - big risk - which is why high fees.
Pps have 5% fees or not?
For old members?
For old members?
Perhaps a nice feature to add with the next site upgrade
- A timer which counts down to the estimated end of a shift.
- timestamp instead of create date in hours
Cheers
- A timer which counts down to the estimated end of a shift.
- timestamp instead of create date in hours
Cheers
The shift / PPS process got stuck yesterday. I have resolved the issue and shifts are catching up.
I will re-reward all of the found blocks that have not confirmed when shifts have caught up.
I will re-reward all of the found blocks that have not confirmed when shifts have caught up.
Shifts are working as expected now and things have caught up. All PPS rewards have been calculated and paid and shifts have been properly applied to the three unconfirmed blocks.
Smooth troubleshooting again, thanks!
The shift / PPS process got stuck yesterday. I have resolved the issue and shifts are catching up.
I will re-reward all of the found blocks that have not confirmed when shifts have caught up.
I will re-reward all of the found blocks that have not confirmed when shifts have caught up.
Shifts are working as expected now and things have caught up. All PPS rewards have been calculated and paid and shifts have been properly applied to the three unconfirmed blocks.
Jump to: