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

[Jam11]

is down r solo pool

[1714219128]

1714219128

[1714219128]

1714219128

[1714219128]

1714219128

[1714219128]

1714219128

[-ck]

is down r solo pool

Pool is fine but I have blocked about 5 users who have been trying to log in with invalid usernames repeatedly for days on end. PM me your IP address or post it here and I'll unblock it to see if that's it.

[Jam11]

1ArhbhvpiMJxehzJLJnfD3mh7bQoMKkrap my worker name ? and the ip of my miners ?

[-ck]

1ArhbhvpiMJxehzJLJnfD3mh7bQoMKkrap my worker name ? and the ip of my miners ?

I remember seeing a username similar to that but you had double pasted so it was double the length it was supposed to be. Check the miner IP address so I can re-enable it and you can try again.

[Jam11]

ty u fix it i just added them to the pool ty for everything

[-ck]

I've added a simple modification to the current cgminer git which is designed to decode the coinbase transactions of a pool for users to confirm where they're mining to. This was done with this pool and ckpool.org in mind for users to be able to confirm what coinbase transactions will be. To use it, one must have a local bitcoind and use their normal login credentials.

For example to check mining to 15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ:

Code:

./cgminer -o http://localhost:8332 -u user -p pass -o solo.ckpool.org:3333 -u 15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ --decode

will produce the following output:

Code:

Pool stratum+tcp://solo.ckpool.org:3333:
{
    "result": {
        "txid": "bc33b38428c3eb299290b35b91f3888a5db86262472e41d159b022b2f79fa62e",
        "hash": "bc33b38428c3eb299290b35b91f3888a5db86262472e41d159b022b2f79fa62e",
        "size": 219,
        "vsize": 219,
        "version": 1,
        "locktime": 0,
        "vin": [
            {
                "coinbase": "03ca13070004bc9a02590430f1fe0c0c9550045900000000000000000a636b706f6f6c112f736f6c6f2e636b706f6f6c2e6f72672f",
                "sequence": 4294967295
            }
        ],
        "vout": [
            {
                "value": 14.21818474,
                "n": 0,
                "scriptPubKey": {
                    "asm": "OP_DUP OP_HASH160 350a22a27dc6bdcff620b66aafe0c49a483d73ef OP_EQUALVERIFY OP_CHECKSIG",
                    "hex": "76a914350a22a27dc6bdcff620b66aafe0c49a483d73ef88ac",
                    "reqSigs": 1,
                    "type": "pubkeyhash",
                    "addresses": [
                        "15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ"
                    ]
                }
            },
            {
                "value": 0.14361802000000001,
                "n": 1,
                "scriptPubKey": {
                    "asm": "OP_DUP OP_HASH160 f4cbe6c6bb3a8535c963169c22963d3a20e76869 OP_EQUALVERIFY OP_CHECKSIG",
                    "hex": "76a914f4cbe6c6bb3a8535c963169c22963d3a20e7686988ac",
                    "reqSigs": 1,
                    "type": "pubkeyhash",
                    "addresses": [
                        "1PKN98VN2z5gwSGZvGKS2bj8aADZBkyhkZ"
                    ]
                }
            },
            {
                "value": 0.0,
                "n": 2,
                "scriptPubKey": {
                    "asm": "OP_RETURN aa21a9ed857001c88a6c5472aa3cfcd1955621191244384e53ddb92dbdbc81339f3920bb",
                    "hex": "6a24aa21a9ed857001c88a6c5472aa3cfcd1955621191244384e53ddb92dbdbc81339f3920bb",
                    "type": "nulldata"
                }
            }
        ]
    },
    "error": null,
    "id": 0
}

You can see the 14.2 bitcoin being directed to 15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ while the remainder is pointed to the pool address. The OP_RETURN is part of the segwit support.

[adz1922]

hey bro..
how do we interpret what the solo.ckpool/users/workername is giving to me?  i am planning to buy 10 s9 and i wanna know if they can all go solo mining, and check whether they are all mining perfectly.

[o_solo_miner]

Come on BLOCK!
 

It is time for one (Friday)
 

[sidehack]

Not sure if it's my crappy upstream provider, but I've been unable to connect to anything ckpool, even the website, for a couple days now. I had been burning in freshly-manufactured stickminers on solo.

[-ck]

Not sure if it's my crappy upstream provider, but I've been unable to connect to anything ckpool, even the website, for a couple days now. I had been burning in freshly-manufactured stickminers on solo.

Characteristic of your IP having been blocked for using an invalid username. Want to PM me your IP address?

[-ck]

 

hey bro..
how do we interpret what the solo.ckpool/users/workername is giving to me?  i am planning to buy 10 s9 and i wanna know if they can all go solo mining, and check whether they are all mining perfectly.

Pretty simple really.
"hashrate1m" shows you average hashrate over the last minute
"hashrate5m" ... last 5 minutes
"hashrate1hr" ... hour
"hashrate1d": ... day
"hashrate7d": ... week
"lastshare": Time the worker last submitted a share in unix seconds
"shares": Total shares submitted
"bestshare": Best diff share submitted this block
"bestever": Best share ever submitted for the life of the worker

[-ck]

There's not much block action happening so I figure I should update solo to include the compatible changes from ckpool.org which means there'll be some restarts in the near future.

Restarts complete, sorry about any downtime you may have experienced.

Pool stat page now shows diff%

Userstats are now formatted for easier reading.
User and workers now show lastshare time instead of last update.
Per worker stats are now deprecated, please monitor workers from within the users page.
Workers idle for a week will eventually disappear from a user's worker list.

An interesting statistic I discovered on this restart is that there have been 15073 different usernames to date using this service, 546 on de. Obviously some people have used multiple addresses so the total number of different users will be much less than this.

[Eagleone]

Love the new look

[-ck]

Going to do one more quick restart for a minor performance optimisation of the main pool for 15k users+.

EDIT: All complete, mine on.

[g00dwin555]

Different workers have the same value "bestshare" and "bestever".
This is normal?

Have all previous decisions been canceled?

[-ck]

Different workers have the same value "bestshare" and "bestever".
This is normal?

Have all previous decisions been canceled?

No? That's not the behaviour I see nor how I designed it. The behaviour is much the same. The only thing different is that all users are loaded at restart now so some users may have stale results from previous blocks if they've been idle for a long time across restarts, but that will never happen again as I'm trying to maintain the state permanently now. I was surprised myself to find 15000 different users loaded up with the new code. Best share is best share this block, best ever is best ever share found. It's per worker, and overall for the user.

EDIT: After PM discussions it's apparent there is an issue with the workers all showing the same best shares. It seems to only have happened on the reload with new worker best shares working correctly and I'll investigate before the pool is restarted again - though I don't foresee another restart any time soon. Luckily it's only cosmetic and won't affect our block finding, so we just need to find a block to reset all the best shares.

[adz1922]

hey bro..
how do we interpret what the solo.ckpool/users/workername is giving to me?  i am planning to buy 10 s9 and i wanna know if they can all go solo mining, and check whether they are all mining perfectly.

Pretty simple really.
"hashrate1m" shows you average hashrate over the last minute
"hashrate5m" ... last 5 minutes
"hashrate1hr" ... hour
"hashrate1d": ... day
"hashrate7d": ... week
"lastshare": Time the worker last submitted a share in unix seconds
"shares": Total shares submitted
"bestshare": Best diff share submitted this block
"bestever": Best share ever submitted for the life of the worker

just a noob question, but may i know what diff share is and what each share means??? just really curious how much chance i have right now for me to not make a mistake in buying 10 S9 for solo mining. thanks

[-ck]

just really curious how much chance i have right now for me to not make a mistake in buying 10 S9 for solo mining. thanks

While I like to encourage people to try mining solo so they can mine on my pool, I think you need to have your eyes opened to what you're trying to do. 10 S9s is about 140TH which has a 1 in 185 chance of solving a block per day at current difficulty, and difficulty will continue to slowly rise. That doesn't mean that after 185 days you'll magically find a block as that's not how mining works. You could find one on the first day and a few over the course of a year, or you might not find one in years. If that's the sort of gamble you're happy to take then that's fine, but there's no guarantees at all with solo mining.

[adz1922]

just really curious how much chance i have right now for me to not make a mistake in buying 10 S9 for solo mining. thanks

While I like to encourage people to try mining solo so they can mine on my pool, I think you need to have your eyes opened to what you're trying to do. 10 S9s is about 140TH which has a 1 in 185 chance of solving a block per day at current difficulty, and difficulty will continue to slowly rise. That doesn't mean that after 185 days you'll magically find a block as that's not how mining works. You could find one on the first day and a few over the course of a year, or you might not find one in years. If that's the sort of gamble you're happy to take then that's fine, but there's no guarantees at all with solo mining.

thanks for the answer bro

[ComputerGenie]

Yeah, when people talk about mining, they tend to forget the words "on average, you're statistically likely to..." and present likelihood as a factual number (ignoring that unlucky bastards like me often take upwards of 200% of "expected" shares to hit a single block). Luck is a factor that must be accounted for in decisions, even if shared pool mining.
Extreme luck examples with pool:
@~220PH - slushpool hit a block(#462151) last week that took just over 14hr 27mins between blocks (with an "expected" time of ~2hr 56min)
@~38PH - kano.is hit a block(#463197) this week that took just over 7 seconds between blocks (with an "expected" time of ~16hr 27min)