|
purelithium
|
 |
October 07, 2012, 03:56:28 AM |
|
getting a few errors on the payment the Current round rewards just dropped down a bit for BTC
Is this normal ?
Thanks
It is DGM at work. Probably because difficulty has risen during round or because current round lasts so long. Anyway DGM will add those "missing" coins to your balance in next 1-3 rounds. DGM? I thought this was a PPS pool? |
Like my post? 1H7bfRYh7F89mfmFgsRCdn4awDaUHQmYqY
|
|
|
|
|
|
|
|
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
coinotron (OP)
Legendary
 Offline
Activity: 1182
Merit: 1000
|
|
October 07, 2012, 09:56:10 AM |
|
Previously there was proportional BTC pool. In March 2012 I changed reward system to DGM.
|
|
|
|
|
purelithium
|
|
October 07, 2012, 03:15:35 PM |
|
Ahh I misunderstood, thanks.
|
Like my post? 1H7bfRYh7F89mfmFgsRCdn4awDaUHQmYqY
|
|
|
coinotron (OP)
Legendary
Offline
Activity: 1182
Merit: 1000
|
|
October 07, 2012, 04:14:00 PM
Last edit: January 22, 2014, 09:36:16 PM by coinotron |
|
We are introducing pure PPS worker - no more waiting for block confirmation! Coins mined with this worker are immediately added to your balance and ready to withdraw. Worker will be available in LTC and PPC pools. Existing PPS worker has been renamed to Round Based PPS (RBPPS) worker. PPC network needs 520 confirmations until real coins are in our wallet (other blockchains need only 120 conf.). Therefore pool operator must maintain much bigger buffer of coins. Also PPCoin price is currently very volatile. And last but not least: spreads at doublec's exchange are very high (20-30% between ask and bid prices). Detailed Coinotron Reward System can be found here: www.coinotron.com/coinotron/AccountServlet?action=home |
|
|
|
coinotron (OP)
Legendary
Offline
Activity: 1182
Merit: 1000
|
|
October 08, 2012, 01:07:29 PM |
|
FYI Usage of PPS and RBPPS workers 1 day after their introduction: | worker | | LTC | | PPC | | PPS | | 28% | | 25% | | RBPPS | | 72% | | 75% |
|
|
|
|
Tomatocage
Legendary
Offline
Activity: 1554
Merit: 1222
brb keeping up with the Kardashians
|
|
October 08, 2012, 04:14:25 PM |
|
Ok so I have some PPC sitting in the Confirmed Rewards column. I set the "Send Threshold" to 1.00 about 2 hours ago. How long does it normally take to send out my coins?
|
|
|
|
coinotron (OP)
Legendary
Offline
Activity: 1182
Merit: 1000
|
|
October 08, 2012, 09:04:56 PM |
|
Ok so I have some PPC sitting in the Confirmed Rewards column. I set the "Send Threshold" to 1.00 about 2 hours ago. How long does it normally take to send out my coins?
Minimum "Send Threshold " is currently 10 PPC. All values below mean not payout. Purpose of this is obvious: to limit number of frequent tiny payouts. I'm trying to avoid LTC like situation. For a few last months minimum "Send Threshold" was 0.1 LTC. There was 0.1 LTC fee for each small transaction added by client. And all of those thousands of little 0.1 LTC transaction fees were being paid by pool. |
|
|
|
|
meebs
|
|
October 08, 2012, 10:18:54 PM |
|
Will the "pure pps" system pay for stales? (LTC)
|
|
|
|
coinotron (OP)
Legendary
Offline
Activity: 1182
Merit: 1000
|
|
October 09, 2012, 10:36:24 AM |
|
Will the "pure pps" system pay for stales? (LTC)
Currently we don't pay for stalesand we pay for invalid blocks. |
|
|
|
coinotron (OP)
Legendary
Offline
Activity: 1182
Merit: 1000
|
|
October 09, 2012, 10:38:47 AM |
|
There was few hours of outage in PPC pool. Last night pool's ppcoind.exe died. Probably due to memory leak bug.
Now PPC pool is up and running.
|
|
|
|
|
Liquid
|
|
October 09, 2012, 10:47:32 AM |
|
why is my Current round rewards dropping it started at 0.77 a few days ago now its at 0.29 BTC  |
Bitcoin will show the world what hard money really is.
|
|
|
coinotron (OP)
Legendary
Offline
Activity: 1182
Merit: 1000
|
|
October 09, 2012, 06:54:53 PM |
|
why is my Current round rewards dropping it started at 0.77 a few days ago now its at 0.29 BTC It is because pool uses DGM. It is a hybrid between PPLNS and the geometric method. That geometric part is responsible for behavior you are observing. It is hard to explain more accurately without going into technical details. DGM algorithm is described here: https://bitcointalk.org/index.php?topic=39497.0 I probably should name this column "estimated current round reward". It will be less confusing. |
|
|
|
|
Liquid
|
|
October 10, 2012, 04:41:18 AM |
|
Yer that would be better thanks
|
Bitcoin will show the world what hard money really is.
|
|
|
coinotron (OP)
Legendary
Offline
Activity: 1182
Merit: 1000
|
|
October 10, 2012, 09:15:41 PM |
|
Pool has been restarted today 2-3 times. I was installing new versions of pool software.
Sorry for any inconvenience.
|
|
|
|
coinotron (OP)
Legendary
Offline
Activity: 1182
Merit: 1000
|
|
October 11, 2012, 06:44:59 PM |
|
FYI Usage of PPS and RBPPS workers after 4 days: | worker | | LTC | | PPC | | PPS | | 39% | | 2% | | RBPPS | | 61% | | 98% |
|
|
|
|
coinotron (OP)
Legendary
Offline
Activity: 1182
Merit: 1000
|
|
October 12, 2012, 05:44:31 PM |
|
Today our LTC pool for the very first time hit 100 MH/s.  |
|
|
|
|
stoppots
|
|
October 12, 2012, 10:49:33 PM |
|
I am seem to be unable to connect with one of my workers. Any idea how to fix this? [2012-10-12 14:42:34] 4 miner threads started, using 'scrypt' algorithm.
[2012-10-12 14:42:35] HTTP request failed: The requested URL returned error: 401
[2012-10-12 14:42:35] json_rpc_call failed, retry after 30 seconds
[2012-10-12 14:43:05] HTTP request failed: necessary data rewind wasn't possible
[2012-10-12 14:43:05] json_rpc_call failed, retry after 30 seconds
[2012-10-12 14:43:35] HTTP request failed: The requested URL returned error: 401
[2012-10-12 14:43:35] json_rpc_call failed, retry after 30 seconds
[2012-10-12 14:44:05] HTTP request failed: necessary data rewind wasn't possible
[2012-10-12 14:44:05] json_rpc_call failed, retry after 30 seconds
|
|
|
|
|
|
Greedi
|
|
October 12, 2012, 11:01:20 PM |
|
I am seem to be unable to connect with one of my workers. Any idea how to fix this?
[2012-10-12 14:42:34] 4 miner threads started, using 'scrypt' algorithm.
[2012-10-12 14:42:35] HTTP request failed: The requested URL returned error: 401
[2012-10-12 14:42:35] json_rpc_call failed, retry after 30 seconds
[2012-10-12 14:43:05] HTTP request failed: necessary data rewind wasn't possible
[2012-10-12 14:43:05] json_rpc_call failed, retry after 30 seconds
[2012-10-12 14:43:35] HTTP request failed: The requested URL returned error: 401
[2012-10-12 14:43:35] json_rpc_call failed, retry after 30 seconds
[2012-10-12 14:44:05] HTTP request failed: necessary data rewind wasn't possible
[2012-10-12 14:44:05] json_rpc_call failed, retry after 30 seconds
401, looks like you'r URL, worker or pass is wrong |
|
|
|
|
stoppots
|
|
October 13, 2012, 05:22:01 AM |
|
I am seem to be unable to connect with one of my workers. Any idea how to fix this?
[2012-10-12 14:42:34] 4 miner threads started, using 'scrypt' algorithm.
[2012-10-12 14:42:35] HTTP request failed: The requested URL returned error: 401
[2012-10-12 14:42:35] json_rpc_call failed, retry after 30 seconds
[2012-10-12 14:43:05] HTTP request failed: necessary data rewind wasn't possible
[2012-10-12 14:43:05] json_rpc_call failed, retry after 30 seconds
[2012-10-12 14:43:35] HTTP request failed: The requested URL returned error: 401
[2012-10-12 14:43:35] json_rpc_call failed, retry after 30 seconds
[2012-10-12 14:44:05] HTTP request failed: necessary data rewind wasn't possible
[2012-10-12 14:44:05] json_rpc_call failed, retry after 30 seconds
401, looks like you'r URL, worker or pass is wrong Very strange, it just a particular worker. On any machine the same worker came back with that error. I deleted the worker and created another with the exact same name and password and now it works. |
|
|
|
|
|
Greedi
|
|
October 13, 2012, 09:51:24 AM |
|
I am seem to be unable to connect with one of my workers. Any idea how to fix this?
[2012-10-12 14:42:34] 4 miner threads started, using 'scrypt' algorithm.
[2012-10-12 14:42:35] HTTP request failed: The requested URL returned error: 401
[2012-10-12 14:42:35] json_rpc_call failed, retry after 30 seconds
[2012-10-12 14:43:05] HTTP request failed: necessary data rewind wasn't possible
[2012-10-12 14:43:05] json_rpc_call failed, retry after 30 seconds
[2012-10-12 14:43:35] HTTP request failed: The requested URL returned error: 401
[2012-10-12 14:43:35] json_rpc_call failed, retry after 30 seconds
[2012-10-12 14:44:05] HTTP request failed: necessary data rewind wasn't possible
[2012-10-12 14:44:05] json_rpc_call failed, retry after 30 seconds
401, looks like you'r URL, worker or pass is wrong Very strange, it just a particular worker. On any machine the same worker came back with that error. I deleted the worker and created another with the exact same name and password and now it works. may i see your start line? |
|
|
|
|
