guess the Diff. / Profitability display is some kind of stuck at the moment. At least TRC Diff. 10458 and Profitability 3.57 did not change since... some blocks? As this information is quite useful, would it be possible to fix it?
Thanks a bunch!
Topic: [POOL] --- Coinotron --- RavenCoin PPS: 1.5% ----- PPLNS, RBPPS: 0% --------- - page 58. (Read 295323 times)
July 04, 2013, 08:44:26 PM
Hi,
guess the Diff. / Profitability display is some kind of stuck at the moment. At least TRC Diff. 10458 and Profitability 3.57 did not change since... some blocks? As this information is quite useful, would it be possible to fix it?
Thanks a bunch!
guess the Diff. / Profitability display is some kind of stuck at the moment. At least TRC Diff. 10458 and Profitability 3.57 did not change since... some blocks? As this information is quite useful, would it be possible to fix it?
Thanks a bunch!
July 04, 2013, 08:17:27 AM
2013-07-03 00:25:40,508 ERROR proxy worker_registry._on_failure # Cannot authorize worker 'dragonus.trc3'
It's important from me because I'm using asicminer blade which have strange configuration panel, and I prefer pool configuration over stratum proxy
I see that you are currently mining using different worker. Does it mean that problem is solved ?
No, it doesn't
I need to pass creditentials by asicminer config (which is quite awkward)
You can easily replicate that error by trying to connect by stratum proxy with added user/pass
mining_proxy.py -rt -o coinotron.com -p 3336 -gp 5055 -cu dragonus.frc3 -cp xxxxx
2013-07-04 15:13:57,417 INFO proxy mining_proxy.on_disconnect # Disconnected from Stratum pool at coinotron.com:3336
same proxy works good with other pools
[nest] ~> mining_proxy.py -rt -o multipool.in -p 3333 -gp 5034 -cu dragonus.blade1 -cp xxxx
2013-07-04 15:15:36,947 INFO proxy jobs.
2013-07-04 15:15:36,949 WARNING proxy mining_proxy.main # Stratum proxy version: 1.5.2
2013-07-04 15:15:36,959 WARNING proxy mining_proxy.test_update # Checking for updates...
2013-07-04 15:15:37,077 WARNING proxy mining_proxy.main # Trying to connect to Stratum pool at multipool.in:3333
2013-07-04 15:15:37,275 INFO stats stats.print_stats # 1 peers connected, state changed 1 times
2013-07-04 15:15:37,276 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at multipool.in:3333
2013-07-04 15:15:37,276 WARNING proxy mining_proxy.on_connect # Authorizing custom user dragonus.blade1, password xxxx
2013-07-04 15:15:37,277 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs
July 03, 2013, 05:04:12 AM
let's see how well this pool can do for me while mining LTC fingers crossed ^^
fingers crossed ^^ July 03, 2013, 04:36:16 AM
my stratum proxy can't authenticate when I pass user/password from command line
pi@ztex28 ~ $ /usr/local/bin/mining_proxy.py -o coinotron.com -p 3335 -sp 5123 -gp 5004 -cu dragonus.trc3 -cp xxxx
2013-07-03 00:25:40,010 INFO proxy jobs. # C extension for midstate not available. Using default implementation instead.
2013-07-03 00:25:40,168 WARNING proxy mining_proxy.main # Stratum proxy version: 1.5.2
2013-07-03 00:25:40,215 WARNING proxy mining_proxy.test_update # Checking for updates...
2013-07-03 00:25:40,389 WARNING proxy mining_proxy.main # Trying to connect to Stratum pool at coinotron.com:3335
2013-07-03 00:25:40,453 INFO stats stats.print_stats # 1 peers connected, state changed 1 times
2013-07-03 00:25:40,457 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at coinotron.com:3335
2013-07-03 00:25:40,461 WARNING proxy mining_proxy.on_connect # Authorizing custom user dragonus.trc3, password xxxx
2013-07-03 00:25:40,465 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs
2013-07-03 00:25:40,508 ERROR proxy worker_registry._on_failure # Cannot authorize worker 'dragonus.trc3'
It's important from me because I'm using asicminer blade which have strange configuration panel, and I prefer pool configuration over stratum proxy
pi@ztex28 ~ $ /usr/local/bin/mining_proxy.py -o coinotron.com -p 3335 -sp 5123 -gp 5004 -cu dragonus.trc3 -cp xxxx
2013-07-03 00:25:40,010 INFO proxy jobs.
2013-07-03 00:25:40,168 WARNING proxy mining_proxy.main # Stratum proxy version: 1.5.2
2013-07-03 00:25:40,215 WARNING proxy mining_proxy.test_update # Checking for updates...
2013-07-03 00:25:40,389 WARNING proxy mining_proxy.main # Trying to connect to Stratum pool at coinotron.com:3335
2013-07-03 00:25:40,453 INFO stats stats.print_stats # 1 peers connected, state changed 1 times
2013-07-03 00:25:40,457 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at coinotron.com:3335
2013-07-03 00:25:40,461 WARNING proxy mining_proxy.on_connect # Authorizing custom user dragonus.trc3, password xxxx
2013-07-03 00:25:40,465 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs
2013-07-03 00:25:40,508 ERROR proxy worker_registry._on_failure # Cannot authorize worker 'dragonus.trc3'
It's important from me because I'm using asicminer blade which have strange configuration panel, and I prefer pool configuration over stratum proxy
I see that you are currently mining using different worker. Does it mean that problem is solved ?
July 02, 2013, 05:43:30 PM
my stratum proxy can't authenticate when I pass user/password from command line
pi@ztex28 ~ $ /usr/local/bin/mining_proxy.py -o coinotron.com -p 3335 -sp 5123 -gp 5004 -cu dragonus.trc3 -cp xxxx
2013-07-03 00:25:40,010 INFO proxy jobs. # C extension for midstate not available. Using default implementation instead.
2013-07-03 00:25:40,168 WARNING proxy mining_proxy.main # Stratum proxy version: 1.5.2
2013-07-03 00:25:40,215 WARNING proxy mining_proxy.test_update # Checking for updates...
2013-07-03 00:25:40,389 WARNING proxy mining_proxy.main # Trying to connect to Stratum pool at coinotron.com:3335
2013-07-03 00:25:40,453 INFO stats stats.print_stats # 1 peers connected, state changed 1 times
2013-07-03 00:25:40,457 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at coinotron.com:3335
2013-07-03 00:25:40,461 WARNING proxy mining_proxy.on_connect # Authorizing custom user dragonus.trc3, password xxxx
2013-07-03 00:25:40,465 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs
2013-07-03 00:25:40,508 ERROR proxy worker_registry._on_failure # Cannot authorize worker 'dragonus.trc3'
It's important from me because I'm using asicminer blade which have strange configuration panel, and I prefer pool configuration over stratum proxy
pi@ztex28 ~ $ /usr/local/bin/mining_proxy.py -o coinotron.com -p 3335 -sp 5123 -gp 5004 -cu dragonus.trc3 -cp xxxx
2013-07-03 00:25:40,010 INFO proxy jobs.
2013-07-03 00:25:40,168 WARNING proxy mining_proxy.main # Stratum proxy version: 1.5.2
2013-07-03 00:25:40,215 WARNING proxy mining_proxy.test_update # Checking for updates...
2013-07-03 00:25:40,389 WARNING proxy mining_proxy.main # Trying to connect to Stratum pool at coinotron.com:3335
2013-07-03 00:25:40,453 INFO stats stats.print_stats # 1 peers connected, state changed 1 times
2013-07-03 00:25:40,457 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at coinotron.com:3335
2013-07-03 00:25:40,461 WARNING proxy mining_proxy.on_connect # Authorizing custom user dragonus.trc3, password xxxx
2013-07-03 00:25:40,465 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs
2013-07-03 00:25:40,508 ERROR proxy worker_registry._on_failure # Cannot authorize worker 'dragonus.trc3'
It's important from me because I'm using asicminer blade which have strange configuration panel, and I prefer pool configuration over stratum proxy
June 29, 2013, 06:09:26 AM
FYI
Today we switched TRC pool reward system to PPLNS ( starting from block 151055 )
RBPPS or PPS are almost impossible to properly implement under current difficulty adjustment conditions in TRC network. Even with very high 4% RBPPS fee TRC pool was generating losses.
Today we switched TRC pool reward system to PPLNS ( starting from block 151055 )
RBPPS or PPS are almost impossible to properly implement under current difficulty adjustment conditions in TRC network. Even with very high 4% RBPPS fee TRC pool was generating losses.
June 29, 2013, 05:28:53 AM
We could use a lot more BTC'ers at the moment. A 20 day round...
June 28, 2013, 05:59:42 AM
Hmmm, get lots of pool disconnections... whats up?
June 28, 2013, 05:24:09 AM
Coinotron down?
June 27, 2013, 05:42:09 AM
FYI
Minimum FTC payout has been reduced to 5 FTC
Minimum FTC payout has been reduced to 5 FTC
June 27, 2013, 03:15:46 AM
Are there any problems with LTC pool? I cannot connect since few hours...
Thare are no problems with LTC pool.
It seems that sth was wrong on my side, cgminer told me this: "Failed to resolve (?wrong URL)".
When I restart it everything back to normal, I can connect to LTC pool without nay problems.
June 27, 2013, 02:55:33 AM
Are there any problems with LTC pool? I cannot connect since few hours...
Thare are no problems with LTC pool.
June 27, 2013, 02:28:45 AM
Are there any problems with LTC pool? I cannot connect since few hours...
June 22, 2013, 02:48:54 AM
what is the point of removing so many of the coins from the "hot wallet"?
seems like the pool would take out their percentage and leave everything else there as it is not the pool's coins.
afraid of getting owned?
seems like the pool would take out their percentage and leave everything else there as it is not the pool's coins.
afraid of getting owned?
The idea of hot wallet is to put only minimum amount of coins at risk. Rest is totally safe in cold wallet which is not connected to the Internet.
June 21, 2013, 09:41:33 PM
what is the point of removing so many of the coins from the "hot wallet"?
seems like the pool would take out their percentage and leave everything else there as it is not the pool's coins.
afraid of getting owned?
seems like the pool would take out their percentage and leave everything else there as it is not the pool's coins.
afraid of getting owned?
June 21, 2013, 12:47:40 PM
Freicoin hotwallet might need to be filled again
And now feathercoin's.
June 20, 2013, 03:44:21 AM
Freicoin hotwallet might need to be filled again
True. Sorry for this
June 19, 2013, 09:18:02 PM
Freicoin hotwallet might need to be filled again
June 19, 2013, 01:19:59 PM
I've had a rig mining for almost a week on this unusually long BTC block (DGM) and now it says "Estimated current round rewards: 0.00000000". What gives? That should be at least 0.2 BTC - I had checked it maybe a day prior.
It can happen when DGM rewards are recalculated. When round is long it can take some time. Please check it out again. If there is still 0.000 please pm me your account name: [email protected]
I have confirmed rewards in BTC over threshold for over a week now. I'd like to get them sent. Need email?
Please send me your account name: [email protected]
June 19, 2013, 06:04:39 AM
I've had a rig mining for almost a week on this unusually long BTC block (DGM) and now it says "Estimated current round rewards: 0.00000000". What gives? That should be at least 0.2 BTC - I had checked it maybe a day prior.
It can happen when DGM rewards are recalculated. When round is long it can take some time. Please check it out again. If there is still 0.000 please pm me your account name: [email protected]
I have confirmed rewards in BTC over threshold for over a week now. I'd like to get them sent. Need email?
Jump to: