Author

Topic: [∞ YH] solo.ckpool.org 2% fee solo mining USA/DE 255 blocks solved! - page 273. (Read 1514780 times)

legendary
Activity: 3500
Merit: 2792
Enjoy 500% bonus + 70 FS
member
Activity: 112
Merit: 10
hi guys can i use the same bitcoin address for 2 miners ? got 2 x s1 i wanna use but just want the one lot of stats

or do i use a _ant1   or .amt1 etc cheers all
newbie
Activity: 36
Merit: 0
Grin and the next one, wow

 Cheesy congrats to 1CArLeSkmBT1BkkcADtNrHoLSgHVhBcesk for solving block 388540!

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



 Roll Eyes

many thanks to Con & Kano, best dev team ever for sure!

long live to your sockets connections!
legendary
Activity: 2483
Merit: 1482
-> morgen, ist heute, schon gestern <-
Yeah, thats the reason why mining here!
The best developer Team try their best for the benefit of all.

-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Bang bang fuckyeah.jpg. Two of the closest blocks ever in solo pool history.

Code:
[2015-12-15 11:09:02.204] Possible block solve diff 149096079299.403168 !
[2015-12-15 11:09:02.310] BLOCK ACCEPTED!
[2015-12-15 11:09:02.311] Solved and confirmed block 388533 by 1FCsjVb87kf2QDETvEgpRkHwE3rYfi4dky.k11
[2015-12-15 11:09:02.311] User 1FCsjVb87kf2QDETvEgpRkHwE3rYfi4dky:{"hashrate1m": "82.7T", "hashrate5m": "82.4T", "hashrate1hr": "83.2T", "hashrate1d": "43.6T", "hashrate7d": "12T"}
[2015-12-15 11:09:02.311] Worker 1FCsjVb87kf2QDETvEgpRkHwE3rYfi4dky.k11:{"hashrate1m": "4.71T", "hashrate5m": "4.63T", "hashrate1hr": "4.45T", "hashrate1d": "2.31T", "hashrate7d": "445G"}

https://www.blocktrail.com/BTC/block/0000000000000000075fd8ff11a90488f94af1528e2711797d3ce825a12259f0

Code:
[2015-12-15 12:06:56.164] Possible block solve diff 144092808176.335114 !
[2015-12-15 12:06:56.554] BLOCK ACCEPTED!
[2015-12-15 12:06:56.554] Solved and confirmed block 388540 by 1CArLeSkmBT1BkkcADtNrHoLSgHVhBcesk.2
[2015-12-15 12:06:56.554] User 1CArLeSkmBT1BkkcADtNrHoLSgHVhBcesk:{"hashrate1m": "10.5T", "hashrate5m": "11T", "hashrate1hr": "10.7T", "hashrate1d": "7.22T", "hashrate7d": "4.45T"}
[2015-12-15 12:06:56.554] Worker 1CArLeSkmBT1BkkcADtNrHoLSgHVhBcesk.2:{"hashrate1m": "4.55T", "hashrate5m": "4.55T", "hashrate1hr": "4.85T", "hashrate1d": "2.53T", "hashrate7d": "1.14T"}

https://www.blocktrail.com/BTC/block/000000000000000007a1660700b145e6e60f698de80a0a0a095118596d272749


Note the first block was only seconds after the previous block solve
Previous block was found by f2pool and accepted by the solo bitcoind at
Code:
2015-12-15 11:08:56.620977 UpdateTip: new best=000000000000000004cd81e2559a5ead00e0d2eb306f0d97d8384d0767e4c47d  height=388532
 
then Solo found this block and it was confirmed by the solo bitcoind at
Code:
2015-12-15 11:09:02.293504 UpdateTip: new best=0000000000000000075fd8ff11a90488f94af1528e2711797d3ce825a12259f0

Despite that, there were still all the pending high priority transactions in the block, even if it was on the small side. Had it been an SPV and/or zero transaction mining block pool that block would have been empty.

The second block had a monstrous >2% in fees due to being quite some time after the block before it and being absolutely full. Lucky miner with only 11TH.
hero member
Activity: 543
Merit: 500
Grin and the next one, wow

 Cheesy 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!!
legendary
Activity: 2483
Merit: 1482
-> morgen, ist heute, schon gestern <-
 Grin and the next one, wow

 Cheesy congrats to 1CArLeSkmBT1BkkcADtNrHoLSgHVhBcesk for solving block 388540!

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

legendary
Activity: 2483
Merit: 1482
-> morgen, ist heute, schon gestern <-
 Cheesy congrats to 1FCsjVb87kf2QDETvEgpRkHwE3rYfi4dky for solving block 388533!
legendary
Activity: 1148
Merit: 1000
Perfect!

Thank you!!

ig
legendary
Activity: 999
Merit: 1000
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/

legendary
Activity: 1148
Merit: 1000
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
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
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.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Pool 0 message: Failed authorisation Sad
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.
hero member
Activity: 651
Merit: 518
There will be a very brief blip in mining while I restart the pool for updates.

EDIT: Complete

Pool 0 message: Failed authorisation :(
legendary
Activity: 2483
Merit: 1482
-> morgen, ist heute, schon gestern <-
 Huh Hashrate drop to 523 TH... before 3 PH.

-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
There will be a very brief blip in mining while I restart the pool for updates.

EDIT: Complete
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
running smooth so far, but no blocks yet Cheesy

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.
member
Activity: 109
Merit: 10
running smooth so far, but no blocks yet Cheesy

anyway, is it gonna work with kano.is to or is it just your solo pool?
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
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  Wink
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 Smiley
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Sorry con, did you mean any miner typ or just a specific one?
Just the asicminer tubes with their dodgy miner controllers
Jump to: