[POOL] Coinotron

[coinotron]

with PPC and TRC stabilized, any chance PPS fee will drop for PPC and turned on for TRC?

PPC - Rather no. If I decrease PPS fee I must maintain buffer for almost 520 blocks. By setting high PPS fee I just encourage everyone to use RBPPS where fee is 2%.
TRC - Rather no. There is simply no way to estimate how many orphans will be produced during low difficulty periods. So it is very risky to offer PPS reward type for this coin.

[1714102487]

1714102487

[1714102487]

1714102487

[1714102487]

1714102487

[1714102487]

1714102487

[1714102487]

1714102487

[mrreece]

I switched port and worker to FTC to give it a try. I was showing hashing on the coinotron site, but that was a  while ago. I now show a good hash rate locally, but shares not increasing on FTC. If I switch back to LTC and then things seem to work right and counting shares. Is something wrong on the FTC pool, or is it something on my end?

[coinotron]

I switched port and worker to FTC to give it a try. I was showing hashing on the coinotron site, but that was a  while ago. I now show a good hash rate locally, but shares not increasing on FTC. If I switch back to LTC and then things seem to work right and counting shares. Is something wrong on the FTC pool, or is it something on my end?

Very strange. Please pm me yout account name and approximate time when shares stopped to increase on website.

[coinotron]

Feathercoin pool

Today I enabled auto payouts.

[beppe]

i can't get stratum proxy to send results.
(trying to mine LTC)

as from this output, it seems to receive some work

Code:

minerd -o http://127.0.0.1:8332 -u XXXXXXX -p XXXXXXXXXXX -t 4
[2013-05-19 15:15:55] 4 miner threads started, using 'scrypt' algorithm.
[2013-05-19 15:15:55] Long-polling activated for http://127.0.0.1:8332/lp
[2013-05-19 15:15:55] thread 0: 4104 hashes, 9.10 khash/s
[2013-05-19 15:15:55] thread 1: 4104 hashes, 8.81 khash/s
[2013-05-19 15:15:55] thread 2: 4104 hashes, 8.29 khash/s
[2013-05-19 15:15:55] thread 3: 4104 hashes, 7.63 khash/s
[2013-05-19 15:16:49] thread 3: 457680 hashes, 8.51 khash/s
[2013-05-19 15:16:55] thread 2: 497436 hashes, 8.39 khash/s
[2013-05-19 15:16:57] thread 1: 528384 hashes, 8.51 khash/s
[2013-05-19 15:16:59] thread 0: 545964 hashes, 8.49 khash/s
[2013-05-19 15:17:26] LONGPOLL detected new block
[2013-05-19 15:17:26] thread 3: 318540 hashes, 8.68 khash/s
[2013-05-19 15:17:26] thread 1: 237504 hashes, 8.34 khash/s
[2013-05-19 15:17:26] thread 2: 265668 hashes, 8.51 khash/s
[2013-05-19 15:17:26] thread 0: 224508 hashes, 8.55 khash/s
[2013-05-19 15:18:17] thread 1: 500112 hashes, 9.75 khash/s
[2013-05-19 15:18:18] thread 2: 510552 hashes, 9.71 khash/s
[2013-05-19 15:18:18] thread 0: 512844 hashes, 9.73 khash/s
[2013-05-19 15:18:19] thread 3: 520920 hashes, 9.77 khash/s
[2013-05-19 15:19:20] thread 1: 585132 hashes, 9.34 khash/s
[2013-05-19 15:19:20] thread 2: 572880 hashes, 9.30 khash/s
[2013-05-19 15:19:20] thread 3: 566832 hashes, 9.29 khash/s
[2013-05-19 15:19:20] thread 0: 574212 hashes, 9.30 khash/s
[2013-05-19 15:19:29] LONGPOLL detected new block
[2013-05-19 15:19:29] thread 3: 75396 hashes, 8.78 khash/s
[2013-05-19 15:19:29] thread 1: 78144 hashes, 8.76 khash/s
[2013-05-19 15:19:29] thread 0: 72924 hashes, 8.63 khash/s
[2013-05-19 15:19:29] thread 2: 76008 hashes, 8.76 khash/s
[2013-05-19 15:20:21] thread 0: 517716 hashes, 9.89 khash/s
[2013-05-19 15:20:21] thread 3: 526668 hashes, 9.98 khash/s
[2013-05-19 15:20:22] thread 2: 525804 hashes, 9.90 khash/s
[2013-05-19 15:20:22] thread 1: 525780 hashes, 9.89 khash/s
[2013-05-19 15:21:26] thread 1: 583788 hashes, 9.03 khash/s
[2013-05-19 15:21:27] thread 0: 593124 hashes, 8.95 khash/s
[2013-05-19 15:21:27] thread 3: 598896 hashes, 9.06 khash/s
[2013-05-19 15:21:28] thread 2: 584112 hashes, 8.87 khash/s
[2013-05-19 15:22:24] thread 2: 514548 hashes, 9.20 khash/s
[2013-05-19 15:22:24] JSON-RPC call failed: {
   "message": "Unexpected error during authorization",
   "code": -1
}
[2013-05-19 15:22:24] json_rpc_call failed, retry after 30 seconds
[2013-05-19 15:22:25] thread 0: 527940 hashes, 9.15 khash/s
[2013-05-19 15:22:25] thread 3: 534528 hashes, 9.24 khash/s
[2013-05-19 15:22:26] thread 1: 541836 hashes, 9.17 khash/s
[2013-05-19 15:22:27] LONGPOLL detected new block
^C

it seems it cannot send anything.
and it repeats that error ad libitum.

what can I do?

my cmd lines are:

mining_proxy.exe -o coinotron.com -p 3334 (port for LTC)
minerd -o http://127.0.0.1:8332 -u XXX -p XXX

[coinotron]

i can't get stratum proxy to send results.
(trying to mine LTC)

as from this output, it seems to receive some work

Code:

minerd -o http://127.0.0.1:8332 -u XXXXXXX -p XXXXXXXXXXX -t 4
[2013-05-19 15:15:55] 4 miner threads started, using 'scrypt' algorithm.
[2013-05-19 15:15:55] Long-polling activated for http://127.0.0.1:8332/lp
[2013-05-19 15:15:55] thread 0: 4104 hashes, 9.10 khash/s
[2013-05-19 15:15:55] thread 1: 4104 hashes, 8.81 khash/s
[2013-05-19 15:15:55] thread 2: 4104 hashes, 8.29 khash/s
[2013-05-19 15:15:55] thread 3: 4104 hashes, 7.63 khash/s
[2013-05-19 15:16:49] thread 3: 457680 hashes, 8.51 khash/s
[2013-05-19 15:16:55] thread 2: 497436 hashes, 8.39 khash/s
[2013-05-19 15:16:57] thread 1: 528384 hashes, 8.51 khash/s
[2013-05-19 15:16:59] thread 0: 545964 hashes, 8.49 khash/s
[2013-05-19 15:17:26] LONGPOLL detected new block
[2013-05-19 15:17:26] thread 3: 318540 hashes, 8.68 khash/s
[2013-05-19 15:17:26] thread 1: 237504 hashes, 8.34 khash/s
[2013-05-19 15:17:26] thread 2: 265668 hashes, 8.51 khash/s
[2013-05-19 15:17:26] thread 0: 224508 hashes, 8.55 khash/s
[2013-05-19 15:18:17] thread 1: 500112 hashes, 9.75 khash/s
[2013-05-19 15:18:18] thread 2: 510552 hashes, 9.71 khash/s
[2013-05-19 15:18:18] thread 0: 512844 hashes, 9.73 khash/s
[2013-05-19 15:18:19] thread 3: 520920 hashes, 9.77 khash/s
[2013-05-19 15:19:20] thread 1: 585132 hashes, 9.34 khash/s
[2013-05-19 15:19:20] thread 2: 572880 hashes, 9.30 khash/s
[2013-05-19 15:19:20] thread 3: 566832 hashes, 9.29 khash/s
[2013-05-19 15:19:20] thread 0: 574212 hashes, 9.30 khash/s
[2013-05-19 15:19:29] LONGPOLL detected new block
[2013-05-19 15:19:29] thread 3: 75396 hashes, 8.78 khash/s
[2013-05-19 15:19:29] thread 1: 78144 hashes, 8.76 khash/s
[2013-05-19 15:19:29] thread 0: 72924 hashes, 8.63 khash/s
[2013-05-19 15:19:29] thread 2: 76008 hashes, 8.76 khash/s
[2013-05-19 15:20:21] thread 0: 517716 hashes, 9.89 khash/s
[2013-05-19 15:20:21] thread 3: 526668 hashes, 9.98 khash/s
[2013-05-19 15:20:22] thread 2: 525804 hashes, 9.90 khash/s
[2013-05-19 15:20:22] thread 1: 525780 hashes, 9.89 khash/s
[2013-05-19 15:21:26] thread 1: 583788 hashes, 9.03 khash/s
[2013-05-19 15:21:27] thread 0: 593124 hashes, 8.95 khash/s
[2013-05-19 15:21:27] thread 3: 598896 hashes, 9.06 khash/s
[2013-05-19 15:21:28] thread 2: 584112 hashes, 8.87 khash/s
[2013-05-19 15:22:24] thread 2: 514548 hashes, 9.20 khash/s
[2013-05-19 15:22:24] JSON-RPC call failed: {
   "message": "Unexpected error during authorization",
   "code": -1
}
[2013-05-19 15:22:24] json_rpc_call failed, retry after 30 seconds
[2013-05-19 15:22:25] thread 0: 527940 hashes, 9.15 khash/s
[2013-05-19 15:22:25] thread 3: 534528 hashes, 9.24 khash/s
[2013-05-19 15:22:26] thread 1: 541836 hashes, 9.17 khash/s
[2013-05-19 15:22:27] LONGPOLL detected new block
^C

it seems it cannot send anything.
and it repeats that error ad libitum.

what can I do?

my cmd lines are:

mining_proxy.exe -o coinotron.com -p 3334 (port for LTC)
minerd -o http://127.0.0.1:8332 -u XXX -p XXX

I'm sorry. I don't have any experience in configuring mining_proxy for LTC

[mhps]

i can't get stratum proxy to send results.
(trying to mine LTC)

as from this output, it seems to receive some work

Code:

minerd -o http://127.0.0.1:8332 -u XXXXXXX -p XXXXXXXXXXX -t 4
[2013-05-19 15:15:55] 4 miner threads started, using 'scrypt' algorithm.
[2013-05-19 15:15:55] Long-polling activated for http://127.0.0.1:8332/lp
[2013-05-19 15:15:55] thread 0: 4104 hashes, 9.10 khash/s
[2013-05-19 15:15:55] thread 1: 4104 hashes, 8.81 khash/s
[2013-05-19 15:15:55] thread 2: 4104 hashes, 8.29 khash/s
[2013-05-19 15:15:55] thread 3: 4104 hashes, 7.63 khash/s
[2013-05-19 15:16:49] thread 3: 457680 hashes, 8.51 khash/s
[2013-05-19 15:16:55] thread 2: 497436 hashes, 8.39 khash/s
[2013-05-19 15:16:57] thread 1: 528384 hashes, 8.51 khash/s
[2013-05-19 15:16:59] thread 0: 545964 hashes, 8.49 khash/s
[2013-05-19 15:17:26] LONGPOLL detected new block
[2013-05-19 15:17:26] thread 3: 318540 hashes, 8.68 khash/s
[2013-05-19 15:17:26] thread 1: 237504 hashes, 8.34 khash/s
[2013-05-19 15:17:26] thread 2: 265668 hashes, 8.51 khash/s
[2013-05-19 15:17:26] thread 0: 224508 hashes, 8.55 khash/s
[2013-05-19 15:18:17] thread 1: 500112 hashes, 9.75 khash/s
[2013-05-19 15:18:18] thread 2: 510552 hashes, 9.71 khash/s
[2013-05-19 15:18:18] thread 0: 512844 hashes, 9.73 khash/s
[2013-05-19 15:18:19] thread 3: 520920 hashes, 9.77 khash/s
[2013-05-19 15:19:20] thread 1: 585132 hashes, 9.34 khash/s
[2013-05-19 15:19:20] thread 2: 572880 hashes, 9.30 khash/s
[2013-05-19 15:19:20] thread 3: 566832 hashes, 9.29 khash/s
[2013-05-19 15:19:20] thread 0: 574212 hashes, 9.30 khash/s
[2013-05-19 15:19:29] LONGPOLL detected new block
[2013-05-19 15:19:29] thread 3: 75396 hashes, 8.78 khash/s
[2013-05-19 15:19:29] thread 1: 78144 hashes, 8.76 khash/s
[2013-05-19 15:19:29] thread 0: 72924 hashes, 8.63 khash/s
[2013-05-19 15:19:29] thread 2: 76008 hashes, 8.76 khash/s
[2013-05-19 15:20:21] thread 0: 517716 hashes, 9.89 khash/s
[2013-05-19 15:20:21] thread 3: 526668 hashes, 9.98 khash/s
[2013-05-19 15:20:22] thread 2: 525804 hashes, 9.90 khash/s
[2013-05-19 15:20:22] thread 1: 525780 hashes, 9.89 khash/s
[2013-05-19 15:21:26] thread 1: 583788 hashes, 9.03 khash/s
[2013-05-19 15:21:27] thread 0: 593124 hashes, 8.95 khash/s
[2013-05-19 15:21:27] thread 3: 598896 hashes, 9.06 khash/s
[2013-05-19 15:21:28] thread 2: 584112 hashes, 8.87 khash/s
[2013-05-19 15:22:24] thread 2: 514548 hashes, 9.20 khash/s
[2013-05-19 15:22:24] JSON-RPC call failed: {
   "message": "Unexpected error during authorization",
   "code": -1
}
[2013-05-19 15:22:24] json_rpc_call failed, retry after 30 seconds
[2013-05-19 15:22:25] thread 0: 527940 hashes, 9.15 khash/s
[2013-05-19 15:22:25] thread 3: 534528 hashes, 9.24 khash/s
[2013-05-19 15:22:26] thread 1: 541836 hashes, 9.17 khash/s
[2013-05-19 15:22:27] LONGPOLL detected new block
^C

it seems it cannot send anything.
and it repeats that error ad libitum.

what can I do?

my cmd lines are:

mining_proxy.exe -o coinotron.com -p 3334 (port for LTC)
minerd -o http://127.0.0.1:8332 -u XXX -p XXX

I use a stratum proxy to mine LTC, too. I think at your hash rate you can expect to find about  2 shares an hour per thread. You perhaps just have to wait longer to see any results.

I also get this

Code:

 JSON-RPC call failed: {
   "message": "Unexpected error during authorization",
   "code": -1
}

and assume it is disconnection for some reason. I get this every 5 min and my miner will wait for 15 sec to connect. This results  a loss of total effective hash rate.

[coinotron]

FYI

Freicoin getwork pool has been closed today.
Please switch your miners to Coinotron FRC stratum pool at port 3336

You can use any miner supporting Stratum protocol.

Example:
cgminer -o stratum+tcp://coinotron.com:3336 -u workername -p password   

[lemonys]

i can't get stratum proxy to send results.
(trying to mine LTC)

as from this output, it seems to receive some work

Code:

minerd -o http://127.0.0.1:8332 -u XXXXXXX -p XXXXXXXXXXX -t 4
[2013-05-19 15:15:55] 4 miner threads started, using 'scrypt' algorithm.
[2013-05-19 15:15:55] Long-polling activated for http://127.0.0.1:8332/lp
[2013-05-19 15:15:55] thread 0: 4104 hashes, 9.10 khash/s
[2013-05-19 15:15:55] thread 1: 4104 hashes, 8.81 khash/s
[2013-05-19 15:15:55] thread 2: 4104 hashes, 8.29 khash/s
[2013-05-19 15:15:55] thread 3: 4104 hashes, 7.63 khash/s
[2013-05-19 15:16:49] thread 3: 457680 hashes, 8.51 khash/s
[2013-05-19 15:16:55] thread 2: 497436 hashes, 8.39 khash/s
[2013-05-19 15:16:57] thread 1: 528384 hashes, 8.51 khash/s
[2013-05-19 15:16:59] thread 0: 545964 hashes, 8.49 khash/s
[2013-05-19 15:17:26] LONGPOLL detected new block
[2013-05-19 15:17:26] thread 3: 318540 hashes, 8.68 khash/s
[2013-05-19 15:17:26] thread 1: 237504 hashes, 8.34 khash/s
[2013-05-19 15:17:26] thread 2: 265668 hashes, 8.51 khash/s
[2013-05-19 15:17:26] thread 0: 224508 hashes, 8.55 khash/s
[2013-05-19 15:18:17] thread 1: 500112 hashes, 9.75 khash/s
[2013-05-19 15:18:18] thread 2: 510552 hashes, 9.71 khash/s
[2013-05-19 15:18:18] thread 0: 512844 hashes, 9.73 khash/s
[2013-05-19 15:18:19] thread 3: 520920 hashes, 9.77 khash/s
[2013-05-19 15:19:20] thread 1: 585132 hashes, 9.34 khash/s
[2013-05-19 15:19:20] thread 2: 572880 hashes, 9.30 khash/s
[2013-05-19 15:19:20] thread 3: 566832 hashes, 9.29 khash/s
[2013-05-19 15:19:20] thread 0: 574212 hashes, 9.30 khash/s
[2013-05-19 15:19:29] LONGPOLL detected new block
[2013-05-19 15:19:29] thread 3: 75396 hashes, 8.78 khash/s
[2013-05-19 15:19:29] thread 1: 78144 hashes, 8.76 khash/s
[2013-05-19 15:19:29] thread 0: 72924 hashes, 8.63 khash/s
[2013-05-19 15:19:29] thread 2: 76008 hashes, 8.76 khash/s
[2013-05-19 15:20:21] thread 0: 517716 hashes, 9.89 khash/s
[2013-05-19 15:20:21] thread 3: 526668 hashes, 9.98 khash/s
[2013-05-19 15:20:22] thread 2: 525804 hashes, 9.90 khash/s
[2013-05-19 15:20:22] thread 1: 525780 hashes, 9.89 khash/s
[2013-05-19 15:21:26] thread 1: 583788 hashes, 9.03 khash/s
[2013-05-19 15:21:27] thread 0: 593124 hashes, 8.95 khash/s
[2013-05-19 15:21:27] thread 3: 598896 hashes, 9.06 khash/s
[2013-05-19 15:21:28] thread 2: 584112 hashes, 8.87 khash/s
[2013-05-19 15:22:24] thread 2: 514548 hashes, 9.20 khash/s
[2013-05-19 15:22:24] JSON-RPC call failed: {
   "message": "Unexpected error during authorization",
   "code": -1
}
[2013-05-19 15:22:24] json_rpc_call failed, retry after 30 seconds
[2013-05-19 15:22:25] thread 0: 527940 hashes, 9.15 khash/s
[2013-05-19 15:22:25] thread 3: 534528 hashes, 9.24 khash/s
[2013-05-19 15:22:26] thread 1: 541836 hashes, 9.17 khash/s
[2013-05-19 15:22:27] LONGPOLL detected new block
^C

it seems it cannot send anything.
and it repeats that error ad libitum.

what can I do?

my cmd lines are:

mining_proxy.exe -o coinotron.com -p 3334 (port for LTC)
minerd -o http://127.0.0.1:8332 -u XXX -p XXX

I use a stratum proxy to mine LTC, too. I think at your hash rate you can expect to find about  2 shares an hour per thread. You perhaps just have to wait longer to see any results.

I also get this

Code:

 JSON-RPC call failed: {
   "message": "Unexpected error during authorization",
   "code": -1
}

and assume it is disconnection for some reason. I get this every 5 min and my miner will wait for 15 sec to connect. This results  a loss of total effective hash rate.

I am seeing the exact same issue.  I switched to coinotron today because my previous pool has a string of really bad luck.  I pointed my proxy to coinotron and it works for a few minutes and then the proxy looses its connection and all my miners as a result stop mining for about 15 seconds, then the proxy reconnects and the miners start working again....   I have used this proxy for three other LTC pools and one BTC pool, and all worked perfectly.  Coinotron is the only that it disconnects from intermittently.

[crazyearner]

Still cant access website maybe you should look at clod hosting to services to balance out your website. Losing fath in this site as I am trying so bloody hard to connect here and want to mine some of the new coins.

[rammy2k2]

site working just fine but autopayments are not .. at least for FRC .. please fix or i move elsewhere ...

[coinotron]

site working just fine but autopayments are not .. at least for FRC .. please fix or i move elsewhere ...

My fault, I didn't announce that:

I suspended FRC payouts before hard fork block 28336. Just in case.
I will enable payouts as soon as we are sure that whole "fork" operation was successful.

[coinotron]

FYI

FRC withdrawals are enabled. All coins waiting to withdraw have been sent.

[ohiwastedmylif]

Coinotron is frozen

0 hash rate & 0 new shares coming in.

Numerous other FTC pools are experiencing issues right now. And LTC is also having issues.

[Lukke]

Same here. 0.0 KH/s on all my machines in statistics (workers are hashing correctly).

[tex83rb]

Same here. 0.0 KH/s on all my machines in statistics (workers are hashing correctly).

me too, please keep us updated.

[Lukke]

Working from now.

[coinotron]

This morning we had 4 hours long outage. It was caused by stupid bug in SQL database. There was overflow error on an identity field in Shares table. Unfortunately this field was of int type and today number of shares submitted to our pool hit max int value: 2^31-1 (2,147,483,647). As a result shares were not registered in db. Statistics on pool showed 0.

Overflow issue is fixed, pool works fine now.

Fortunately, all shares which solved blocks were submitted to the network. For example LTC pool mined during outage 23 blocks.  
I will add rewards from those blocks to the reward for last round before outage.  

I'm very sorry for this outage.

[coinotron]

FYI

I have added  to your balances rewards for blocks solved during outage:

FRC pool: 1 block = 226.33 FRC
FTC pool: 1 block = 200 FTC
TRC pool: 55 blocks = 1100 TRC
LTC pool: 23 blocks = 1150 LTC

Those amounts were distributed among miners who were mining just before outage, proportionally to their hashrates.

[Ultraviolet]

Is your webpage down? I want to switch to you but I can't access your site on any of my systems.