[∞ YH] solo.ckpool.org 2% fee solo mining USA/DE 255 blocks solved!

[willi9974]

If any of you have any asicminer tubes, I'm experimenting with setting a proxy that should hopefully work with them. Could you please try pointing them to
stratum+tcp://ckpool.org:3333
This is only a temporary url to see if they work. Please give it a go. Use the normal sort of login credentials you would otherwise use on the solo pool as that's where the hashes are going. All workernames are consolidated into the one username on solo.ckpool.org so you'll only see the one worker with the basic username.

Did you Need a 6THs Miner for 1 or 2 days, i Can point it to your Test pool

[o_solo_miner]

  Willi, er meint diese Miner:
https://bitcointalk.org/index.php?topic=735728.0

Con is talking about those type of Miners:
https://bitcointalk.org/index.php?topic=735728.0

[-ck]

If any of you have any asicminer tubes, I'm experimenting with setting a proxy that should hopefully work with them. Could you please try pointing them to
stratum+tcp://ckpool.org:3333
This is only a temporary url to see if they work. Please give it a go. Use the normal sort of login credentials you would otherwise use on the solo pool as that's where the hashes are going. All workernames are consolidated into the one username on solo.ckpool.org so you'll only see the one worker with the basic username.

Did you Need a 6THs Miner for 1 or 2 days, i Can point it to your Test pool

Sure point some more please, it will make a good test if I can manage to redirect different logins.

[BannedDK]

CK pointed 1 controller to the ckpool with around 1.5th gonna let it run all day

Thanks for that. Fiddling with a few settings at the moment but it appears I can get the hashrate going. Unfortunately they don't seem to be supporting redirect and sessionid (not surprisingly since they don't run a full stratum client such as cgminer) which means that this proxy isn't a permanent solution and I may need to be running a second instance of the pool to support them fully. I'll see what I can do. For the time being since sessionid isn't supported the hashes are all going to my mining address instead of 15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ so monitor your hashrate with that address on the solo website. If you are lucky enough to find a block rest assured I'll send you the regular reward to the address you're logged into the proxy with.

cool, thanks for trying to sort it out, can let t run as long as you want. i got free electricity 

[o_solo_miner]

Sorry con, did you mean any miner typ or just a specific one?

[-ck]

Sorry con, did you mean any miner typ or just a specific one?

Just the asicminer tubes with their dodgy miner controllers

[-ck]

CK pointed 1 controller to the ckpool with around 1.5th gonna let it run all day

Thanks for that. Fiddling with a few settings at the moment but it appears I can get the hashrate going. Unfortunately they don't seem to be supporting redirect and sessionid (not surprisingly since they don't run a full stratum client such as cgminer) which means that this proxy isn't a permanent solution and I may need to be running a second instance of the pool to support them fully. I'll see what I can do. For the time being since sessionid isn't supported the hashes are all going to my mining address instead of 15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ so monitor your hashrate with that address on the solo website. If you are lucky enough to find a block rest assured I'll send you the regular reward to the address you're logged into the proxy with.

cool, thanks for trying to sort it out, can let t run as long as you want. i got free electricity 

Alrighty, got it working! They will connect, be told to reconnect and if they don't within 2 minutes, they're dropped. These tubes seem to stay disconnected for about 1 minute before they try reconnecting. On reconnecting the proxy will look to see if they have an old sessionid (which the tubes don't support) and if not, it will try to match them by IP address. If it does, then it starts mining to a new proxy instance pointed to the upstream pool.

Practical upshot: You are now mining to your actual address at solo.ckpool.org \o/ So you should be able to check on them as regular stats.

I will probably move where the proxy is but for now you can leave them there to give it a good run. Other miners with tubes please feel free to give it a try

[BannedDK]

running smooth so far, but no blocks yet

anyway, is it gonna work with kano.is to or is it just your solo pool?

[-ck]

running smooth so far, but no blocks yet

anyway, is it gonna work with kano.is to or is it just your solo pool?

Solo's always the testing ground for new code which eventually goes upstream (except for the discrete solo address mining code which is private to this pool only). I'll probably help kano set up a special port on kano.is to work with them.

[-ck]

There will be a very brief blip in mining while I restart the pool for updates.

EDIT: Complete

[o_solo_miner]

  Hashrate drop to 523 TH... before 3 PH.

[SISAR]

There will be a very brief blip in mining while I restart the pool for updates.

EDIT: Complete

Pool 0 message: Failed authorisation :(

[-ck]

Pool 0 message: Failed authorisation

Is this a new issue with a login that worked previously? It's probably a symptom of the work in progress between restarts not working properly and should get better with the next restart, sorry.

I will likely issue another restart in the near future again too, just a heads up.

EDIT: Completed. Sorry about any inconvenience, the last update didn't quite complete the necessary improvements and introduced a temporary regression. No blocks were harmed in the making of this restart.

The login issue was found to be a problem with that first restart. The second one fixed most of the remaining problems but there is one tiny issue left so there is one more brief blip in mining coming up again, sorry about that but most of you aren't failing over anyway during the restarts.

EDIT: All complete, sorry about any inconvenience.

[-ck]

Sorry about the multiple restarts. The changes are all for intrinsic pool performance and were all required and overdue. Specifically I've made it much harder for the pool to ever lose contact with a bitcoind and miss block changes etc. In addition, the way diff is sent out on first connecting miners is now more compatible with some of the dodgier miners out there like the BFL mofarchers, and will lead to less spillage of low diff work at startup from whatever mining source (including rentals).

There are no further scheduled restarts in the short to medium future now. Thanks for your patience. Feel free to check the blockchange performance of the solo pool here:
http://poolbench.antminer.link/
and remember that unlike f2pool, solo does full block validation on a block change, AND it always includes transactions.

[iglasses]

If any of you have any asicminer tubes, I'm experimenting with setting a proxy that should hopefully work with them. Could you please try pointing them to
stratum+tcp://ckpool.org:3333
This is only a temporary url to see if they work. Please give it a go. Use the normal sort of login credentials you would otherwise use on the solo pool as that's where the hashes are going. All workernames are consolidated into the one username on solo.ckpool.org so you'll only see the one worker with the basic username.

Just got a Prisma 2.0 today and I am mining here.
Settings are straight to solo.ckpool.org and port 3333

It shows the pool status ok and is definitely hashing because I can see it pulling the wattage form the wall and the stats screen shows 1351Ghs %98 efficiency.

Is there any way to monitor/pull any other stats from this device when solo mining?  Like best share, etc.

ig

[portice]

If any of you have any asicminer tubes, I'm experimenting with setting a proxy that should hopefully work with them. Could you please try pointing them to
stratum+tcp://ckpool.org:3333
This is only a temporary url to see if they work. Please give it a go. Use the normal sort of login credentials you would otherwise use on the solo pool as that's where the hashes are going. All workernames are consolidated into the one username on solo.ckpool.org so you'll only see the one worker with the basic username.

Just got a Prisma 2.0 today and I am mining here.
Settings are straight to solo.ckpool.org and port 3333

It shows the pool status ok and is definitely hashing because I can see it pulling the wattage form the wall and the stats screen shows 1351Ghs %98 efficiency.

Is there any way to monitor/pull any other stats from this device when solo mining?  Like best share, etc.

ig

Statistics:
Simple total pool statistics can be found at http://solo.ckpool.org/pool/
Solo.ckpool.org currently only displays minimal per user and per worker information based on btcaddress.
To access this, enter your BTC address at the end of: http://solo.ckpool.org/users/
or your workername at the end of: http://solo.ckpool.org/workers/

[iglasses]

Perfect!

Thank you!!

ig

[o_solo_miner]

  congrats to 1FCsjVb87kf2QDETvEgpRkHwE3rYfi4dky for solving block 388533!

[o_solo_miner]

  and the next one, wow

  congrats to 1CArLeSkmBT1BkkcADtNrHoLSgHVhBcesk for solving block 388540!

And the Pool only got around 700 TH/S!!!

[727miner]

and the next one, wow

  congrats to 1CArLeSkmBT1BkkcADtNrHoLSgHVhBcesk for solving block 388540!

And the Pool only got around 700 TH/S!!!

Nice to see the solo pool bringing in some more blocks!!