wizkid057
Legendary
Offline
Activity: 1223
Merit: 1006
|
|
March 22, 2013, 11:52:58 PM |
|
Greetings Eligius Miners!
So, after some discussion, I've dropped the minimum payout/enter-queue amount to 100 TBC (0.16777216 BTC).
This is implemented, as per suggestion from Luke-Jr, as a two pass approach.
The payout queue setup now does a first pass using the old minimum payout amount (400 TBC or ~0.67 BTC) and miners that timed out from inactivity (> 7 days). Then, it does a second pass with the remaining miners for any that meet the new minimum payout amount of 100 TBC.
This should make it a smooth transition, and once the payout queue gets cleaned up a bit (either on its own through generated payouts or sometime soon from a manual payout), I'll put everything back to a single pass using the new lower minimum payout amount.
Also, keep in mind, that customization of settings such as your own desired minimum payout amount are coming soon!
-wk
|
|
|
|
Feldspar
Newbie
Offline
Activity: 27
Merit: 0
|
|
March 23, 2013, 09:11:39 PM |
|
Greetings Eligius Miners!
So, after some discussion, I've dropped the minimum payout/enter-queue amount to 100 TBC (0.16777216 BTC).
This is implemented, as per suggestion from Luke-Jr, as a two pass approach.
The payout queue setup now does a first pass using the old minimum payout amount (400 TBC or ~0.67 BTC) and miners that timed out from inactivity (> 7 days). Then, it does a second pass with the remaining miners for any that meet the new minimum payout amount of 100 TBC.
This should make it a smooth transition, and once the payout queue gets cleaned up a bit (either on its own through generated payouts or sometime soon from a manual payout), I'll put everything back to a single pass using the new lower minimum payout amount.
Also, keep in mind, that customization of settings such as your own desired minimum payout amount are coming soon!
-wk
This is great! As a wee little GPU miner, I greatly appreciate the chance to, in the future, get smaller payments more regularly. Now we just need a bunch of high-luck blocks to come our way to catch up the queue . Thank you for all the work you do!
|
|
|
|
bitcoindaddy
|
|
March 25, 2013, 11:41:22 PM |
|
I noticed TOR is offered on port 8337, Base on the port, I assume this is a getwork server. Is Stratum also available on TOR?
|
|
|
|
wizkid057
Legendary
Offline
Activity: 1223
Merit: 1006
|
|
March 26, 2013, 04:01:12 AM |
|
I noticed TOR is offered on port 8337, Base on the port, I assume this is a getwork server. Is Stratum also available on TOR?
Actually, it wasn't, but, I've gone ahead and added port 3334. -wk
|
|
|
|
bitcoindaddy
|
|
March 26, 2013, 07:48:18 AM |
|
I noticed TOR is offered on port 8337, Base on the port, I assume this is a getwork server. Is Stratum also available on TOR?
Actually, it wasn't, but, I've gone ahead and added port 3334. -wk Thanks!
|
|
|
|
stevegee58
Legendary
Offline
Activity: 916
Merit: 1003
|
|
March 26, 2013, 10:57:18 AM |
|
I don't completely understand the payout queue. My address has been moving up and down in the queue so much I was thinking there was something wrong. Wouldn't I just steadily move up the queue over time as addresses above me are paid out? It doesn't appear to be like this.
|
You are in a maze of twisty little passages, all alike.
|
|
|
Parazyd
|
|
March 26, 2013, 11:06:57 AM |
|
I don't completely understand the payout queue. My address has been moving up and down in the queue so much I was thinking there was something wrong. Wouldn't I just steadily move up the queue over time as addresses above me are paid out? It doesn't appear to be like this.
The minimum payout is changed to ~0.17 or something. When you get to that, you end up on the bottom of the queue. But! If you hit the old limit (~0.67) then you are moved to the top.
|
|
|
|
stevegee58
Legendary
Offline
Activity: 916
Merit: 1003
|
|
March 26, 2013, 11:25:01 AM |
|
I'm just below the old payout limit. I guess what I'm seeing is others moving above 0.67 and above me in the queue?
|
You are in a maze of twisty little passages, all alike.
|
|
|
wizkid057
Legendary
Offline
Activity: 1223
Merit: 1006
|
|
March 26, 2013, 11:55:43 AM |
|
I'm just below the old payout limit. I guess what I'm seeing is others moving above 0.67 and above me in the queue?
That, plus there are funds owed to miners added to the queue with every block we find. No worries, it will be caught up soon enough even if I have to manually clear it up. -wk
|
|
|
|
|
wizkid057
Legendary
Offline
Activity: 1223
Merit: 1006
|
|
March 30, 2013, 05:32:18 AM |
|
Greetings miners!
With the payout queue all caught up, I've officially made the 100 TBC minimum payout the only minimum payout. (No more two pass setup).
Happy mining!
-wk
|
|
|
|
bitcoindaddy
|
|
April 04, 2013, 07:24:30 PM |
|
Longest block ever? 25 hours so far as of this post.
|
|
|
|
somedood
Newbie
Offline
Activity: 14
Merit: 0
|
|
April 05, 2013, 08:14:59 PM Last edit: April 05, 2013, 08:40:31 PM by somedood |
|
Is there trouble with the pool? I can ping but I cannot get work at the moment...
EDIT: seems to work again.
|
|
|
|
wizkid057
Legendary
Offline
Activity: 1223
Merit: 1006
|
|
April 05, 2013, 11:40:30 PM |
|
Is there trouble with the pool? I can ping but I cannot get work at the moment...
EDIT: seems to work again.
Server was having some problems. We've been getting a lot of high-connection count miners in bursts lately (maybe someone's botnet's failover...), and the server was having some issues handling the load. I've changed a few things, updating some settings, and some other tweaks. For now, I've added the X-Stratum redirect header to getwork requests. This seems to have limited the connections of some users using mining software that does not yet support GBT mining. Overall, there is just one more change that will need to be made to the pool server code (eloipool) to make everything perfect, but, nothing that is hindering the pool. This should solve pretty much all of the stability issues people have been experiencing with Eligius. Happy mining! -wk
|
|
|
|
wizkid057
Legendary
Offline
Activity: 1223
Merit: 1006
|
|
April 06, 2013, 11:03:35 AM |
|
Is there trouble with the pool? I can ping but I cannot get work at the moment...
EDIT: seems to work again.
Server was having some problems. We've been getting a lot of high-connection count miners in bursts lately (maybe someone's botnet's failover...), and the server was having some issues handling the load. I've changed a few things, updating some settings, and some other tweaks. For now, I've added the X-Stratum redirect header to getwork requests. This seems to have limited the connections of some users using mining software that does not yet support GBT mining. Overall, there is just one more change that will need to be made to the pool server code (eloipool) to make everything perfect, but, nothing that is hindering the pool. This should solve pretty much all of the stability issues people have been experiencing with Eligius. Happy mining! -wk It seems some people have taken this post as an excuse to load some huge botnets onto Eligius! So, currently dealing with some connection count load management issues. Please bear with me... -wk
|
|
|
|
purelithium
|
|
April 06, 2013, 06:17:31 PM |
|
I can't get GBT to connect (8337 port) but stratum works fine. I'm using BFGMiner.
|
Like my post? 1H7bfRYh7F89mfmFgsRCdn4awDaUHQmYqY
|
|
|
wizkid057
Legendary
Offline
Activity: 1223
Merit: 1006
|
|
April 07, 2013, 12:36:36 PM Last edit: April 07, 2013, 03:33:39 PM by wizkid057 |
|
Greetings Eligius miners! So, I was up yesterday morning at 5:30AM local time (Saturday!) because of one of my "pool is broken" alarms. Turns out some insanely huge botnet has decided to call Eligius home, and is adding bots at a rate of about 2-3 unique IPs per second. And of course, these bots are connecting on port 8337 (getwork/GBT). So, of course, after building up for a while, the server got bogged down and tripped my alarm. I've since been trying to figure out a solution to the problem, and it is now just about 27 hours later (I had about a 90 minute nap somewhere in there). Anyway, after many many attempts at different methods for fixing this, I ended up coming up with a solution which basically amounts to load balancing port 8337. I've also moved stratum (port 3334) to it's own independent process. Now, eloipool wasn't really designed to do this, so, I don't know if there are any unforeseen issues with the way I've attempted this. One side effect comes to mind, and it involves variable difficulty calculation for miners who mine from multiple IPs. Most likely their vardiff number will be lower than it normally would be because of this if they use GBT/getwork because they wont be getting/submitting work to the same server on the backend. Not a huge problem. One which I will solve soon. Edit: I also just realized that this setup affects vardiff for anyone with hashpower on both GBT/getwork and stratum. So, conclusion, the pool is up, its handling the new traffic now, and all should be well for miners. -wk P.S. - I need a raise.
|
|
|
|
Parazyd
|
|
April 07, 2013, 04:38:33 PM |
|
So the pool is handling that?
What kind of connection does the server have? Seems like a powerful server.
|
|
|
|
bitcoindaddy
|
|
April 07, 2013, 08:10:22 PM |
|
Have you considered getting rid of getwork (and the botnets) and just do Stratum and GBT?
|
|
|
|
WynX
Member
Offline
Activity: 77
Merit: 10
|
|
April 07, 2013, 10:12:30 PM |
|
So, conclusion, the pool is up, its handling the new traffic now, and all should be well for miners. -wk P.S. - I need a raise. Nice work . Can only give you a small bit of your raise ghehe...
|
|
|
|
|