Author

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

-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
DDoS on the front end again. Those of you already mining won't be affected. Will redirect the front end shortly.
DDoS redirected. New gateway is up. Keep on mining.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
There's some kind of connectivity issue at solo main at the moment (DDoS?). Looking into it...  De is unaffected.

EDIT: Seems to have recovered now. Hashrate climbing again.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
As mentioned here I'm taking down the SG node now. Apologies to the remaining 1.5TH mining there.

SG Node has been removed. There will be a brief blip at both the DE and main solo pools for updates.

Updates all complete. Mine on.
legendary
Activity: 1554
Merit: 1001
Wink congrats to 3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY for the Block!

{"hashrate1m": "125T", "hashrate5m": "123T", "hashrate1hr": "124T", "hashrate1d": "124T", "hashrate7d": "112T", "lastupdate": 1453146737, "workers": 112, "shares": 249386150227, "bestshare": 5858515.5556973545, "bestever": 252987485486}

That's 3 in a row for this particular user.  Nice returns for 125T.  Congrats!

X

Guess I'm gonna have to up the ante to find one myself Wink
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
hi,

ive set up my S3 on a "balance" between your de.solo pool and another regular pool. Im just checking to see if the "diff" stat on my miner is meant to read 1000 as the other pool is 256.

By the way im new to mining so please excuse me if this is a stupid question  Smiley
Diff starts at 1000 on this pool so that's normal. It will change over time though to suit your hashrate.
hero member
Activity: 2534
Merit: 623
hi,

ive set up my S3 on a "balance" between your de.solo pool and another regular pool. Im just checking to see if the "diff" stat on my miner is meant to read 1000 as the other pool is 256.

By the way im new to mining so please excuse me if this is a stupid question  Smiley
sr. member
Activity: 413
Merit: 250
148. block was came. congratulations to winner 3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY .
legendary
Activity: 3500
Merit: 2792
Enjoy 500% bonus + 70 FS
concrats !!!

A nice wallet https://blockchain.info/address/3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY 300 BTC and the most of them are mined by solo pool or it self....

member
Activity: 66
Merit: 10
Wink congrats to 3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY for the Block!

{"hashrate1m": "125T", "hashrate5m": "123T", "hashrate1hr": "124T", "hashrate1d": "124T", "hashrate7d": "112T", "lastupdate": 1453146737, "workers": 112, "shares": 249386150227, "bestshare": 5858515.5556973545, "bestever": 252987485486}

That's 3 in a row for this particular user.  Nice returns for 125T.  Congrats!

X
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
New solo miner. Read your instructions and have a question about the following statement:
"Proxy support: Miners with many devices wishing to consolidate their devices into a single connection to solo ckpool are recommended to use the complementary ckpool code as ckproxy stratum proxy (for linux)."

I have 7 miners.

Is there's any advantage to using the proxy support versus just setting all 7 miners to the same payout address?
In particular I'm wondering whether it makes the overall odds better due to some increase in processing efficiency or provides some other advantage.

Also, with regards to overall odds of one of my rigs solving a block, does it make any difference whether I use the same payout address for all 7 miners or whether I give them each a separate address?
With 7 miners it's probably not worth it. When I say many miners I mean miners with 100+ devices. Decreasing the network bandwidth is the only real advantage. Nothing changes your chances of finding a block - only overall hashrate matters.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Code:
[2016-01-18 13:47:30.755] Possible block solve diff 114715923118.361893 !
[2016-01-18 13:47:30.875] BLOCK ACCEPTED!
[2016-01-18 13:47:30.876] Solved and confirmed block 393904 by 3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY.101
[2016-01-18 13:47:30.876] User 3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY:{"hashrate1m": "126T", "hashrate5m": "124T", "hashrate1hr": "124T", "hashrate1d": "124T", "hashrate7d": "112T"}
[2016-01-18 13:47:30.876] Worker 3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY.101:{"hashrate1m": "1.89T", "hashrate5m": "1.33T", "hashrate1hr": "1.15T", "hashrate1d": "1.14T", "hashrate7d": "1.03T"}

https://www.blocktrail.com/BTC/block/00000000000000000995a1d73f17369dd6fec32738f4c53fb99c258e645f6fbe

Finally breaking the dry spell.
legendary
Activity: 3583
Merit: 1094
Think for yourself
New solo miner. Read your instructions and have a question about the following statement:
"Proxy support: Miners with many devices wishing to consolidate their devices into a single connection to solo ckpool are recommended to use the complementary ckpool code as ckproxy stratum proxy (for linux)."

I have 7 miners.

Is there's any advantage to using the proxy support versus just setting all 7 miners to the same payout address?
In particular I'm wondering whether it makes the overall odds better due to some increase in processing efficiency or provides some other advantage.

Also, with regards to overall odds of one of my rigs solving a block, does it make any difference whether I use the same payout address for all 7 miners or whether I give them each a separate address?

All that really matters is your total hash rate.  If you want to use 7 different workers and BTC addresses to help manage your systems that is fine.
full member
Activity: 133
Merit: 100
the lucky winner 3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY  Wink
legendary
Activity: 1638
Merit: 1005
Wink congrats to 3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY for the Block!

{"hashrate1m": "125T", "hashrate5m": "123T", "hashrate1hr": "124T", "hashrate1d": "124T", "hashrate7d": "112T", "lastupdate": 1453146737, "workers": 112, "shares": 249386150227, "bestshare": 5858515.5556973545, "bestever": 252987485486}
legendary
Activity: 2483
Merit: 1482
-> morgen, ist heute, schon gestern <-
 Wink congrats to 3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY for the Block!
sr. member
Activity: 442
Merit: 250
Found Lost beach - quiet now
New solo miner. Read your instructions and have a question about the following statement:
"Proxy support: Miners with many devices wishing to consolidate their devices into a single connection to solo ckpool are recommended to use the complementary ckpool code as ckproxy stratum proxy (for linux)."

I have 7 miners.

Is there's any advantage to using the proxy support versus just setting all 7 miners to the same payout address?
In particular I'm wondering whether it makes the overall odds better due to some increase in processing efficiency or provides some other advantage.

Also, with regards to overall odds of one of my rigs solving a block, does it make any difference whether I use the same payout address for all 7 miners or whether I give them each a separate address?





-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
SG node is coming up on a week of uptime tomorrow. Unfortunately its total hashrate over that time hasn't even averaged one modern mining piece of mining hardware so I'm sorry to say that I'm forced to give it up. It appears that there really is only room for 2 solo mining nodes in 2 major parts of the world. I'll give it another day so that existing miners can take note and move their hashes but I'll be shutting down SG tomorrow (unless someone dumps a whole lot of hash on there or it finds a block), leaving only solo main and the DE node.

hi ck,

just curious, is the "sg.kano.is" take up ok? we should be able to get most of South East Asia and ANZ users...

I mean, if there 100 user at sg.kano, I would assume at least half will do solo mining at sg.ckpool, unless the solo miners are mining somewhere else. I may wrong, since not all solo mining is not for the faint hearted :-)
I'm in control of both of those nodes.
sg.kano.is currently has 207TH
sg.ckpool.org currently has 3TH

There are effectively no solo miners here.
legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
SG node is coming up on a week of uptime tomorrow. Unfortunately its total hashrate over that time hasn't even averaged one modern mining piece of mining hardware so I'm sorry to say that I'm forced to give it up. It appears that there really is only room for 2 solo mining nodes in 2 major parts of the world. I'll give it another day so that existing miners can take note and move their hashes but I'll be shutting down SG tomorrow (unless someone dumps a whole lot of hash on there or it finds a block), leaving only solo main and the DE node.

hi ck,

just curious, is the "sg.kano.is" take up ok? we should be able to get most of South East Asia and ANZ users...

I mean, if there 100 user at sg.kano, I would assume at least half will do solo mining at sg.ckpool, unless the solo miners are mining somewhere else. I may wrong, since not all solo mining is not for the faint hearted :-)
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
SG node is coming up on a week of uptime tomorrow. Unfortunately its total hashrate over that time hasn't even averaged one modern mining piece of mining hardware so I'm sorry to say that I'm forced to give it up. It appears that there really is only room for 2 solo mining nodes in 2 major parts of the world. I'll give it another day so that existing miners can take note and move their hashes but I'll be shutting down SG tomorrow (unless someone dumps a whole lot of hash on there or it finds a block), leaving only solo main and the DE node.
legendary
Activity: 1414
Merit: 1077
Maybe I picked a bad time to expand the solo infrastructure  Tongue
Blame that annoying frog, it scared the blocks away Tongue

Dont blame the frog its not his fault Tongue. I thought he was bringing a bit of colour and fun at a miserable time Wink.

-ck I think your comment is right, its now becoming clear exactly how much difference the recent increased network size and difficulty spikes have made Sad.
Jump to: