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

Add:
_workername
or
.workername

to the end of the bitcoin address. Both work. Or if you don't care about separate workers you can just use the bitcoin address for all the worker names.

Sorry too lazy;dr

How do i add workers on each miner please?

To the person who's trying to mine on the pool with a regular username, you will never succeed unless you use a username that is a bitcoin address as the pool will keep rejecting your attempt to authorise (p.s. I recognise your username from kano's ckpool so perhaps you set this as a backup and forgot to use a different username for it).

That makes sense.  There is some hashrate coming your way.  Maybe I'll get lucky and win the lottery?

Yes it does mean that as mining it directly into your btc address means there is no wallet involved to hack and no payout to generate and you can see all the blocks generated on this pool so far at

https://blockchain.info/address/1PKN98VN2z5gwSGZvGKS2bj8aADZBkyhkZ

I found out about this pool when asking in another thread about setting up an extra S3 to solo mine.  I like to very easy to use solo mining option that your pool provides.

When you say that

doesn't that mean that a person could track the block to your pool based on the fee transaction to PKN98VN2z5gwSGZvGKS2bj8aADZBkyhkZ?

Or is the fee address generated when a block is found to provide another layer to anonymity?

many thanks for setting this up. it's appreciated.

Nothing's changed at pool end, all seems fine.

My tube is starting to act up on 3334 and 3333.

I take this to mean that folks should be able to use the tubeminers with the regular BE controllers on the regular pool now?
Thanks for all the hard work. I don't have any of these yet, but I was thinking this may be an issue. Glad to know it won't be a problem.

News updates:

1. I'm planning on consolidating the pool instances into one now that the broken stratum implementations should be able to mine on the main pool. I will run the main pool on both ports (3333/3334) so that people won't need to change their miner settings, but the pool stats for the "tube" pool will simply point back to the same stats as the main pool. I'll keep all the existing links also but suggest that anyone starting up new miners or workers point them to the default location: solo.ckpool.org:3333 . I'm also adding port 443 as an option so now ports 3333,3334 and 443 will all work.

2. In addition, I'm going to give advance warning that I will be taking down the testnet pool in one month's time when the paid subscription for that VPS expires. I can't justify running the pool for free when people happily mine on it and don't donate anything (no I'm not interested in testnet coin donations). So unless someone has a burning need for this service and is happy to donate a few decibitcoins to keep it running, I will shut it down.

3. The provider for the main pool has a scheduled hardware upgrade planned for December 4th at 7:00:00 AM UTC. Due to the timing of the upgrade and timezone differences, and the planned downtime on their end, the pool will be effectively down for maintenance for at least an hour, so expect a period of outage at that time. I will endeavour to keep the downtime as short as possible

EDIT: The changeover described in (1) above is now complete.

Please tell me if you are unable to mine on the default pool now, thanks.

Not really it's 1000x as many accepts as rejects. That's 0.1%

Yes but high rejects.

I think that's good, no? Do the pool stats for that worker concur?

Tried using asicminer tube on normal pool:

Apologies, there was a crash on the main pool. I've fixed the bug in question. I've also changed the nonce settings on the pool which I'd made more configurable in the updated ckpool code.  For those who had proxies that wouldn't work on ckpool and used the tube pool you might want to try it on the main pool now. I don't think tubes and prismas with their regular controller will work directly (but it's worth a try) however they should actually work if you run ckpool locally as a proxy now talking to the upstream ckpool.

EDIT: I've also restarted the tube pool with the same code fix as well, though more miners should be able to use the main pool instance now.

He's dead Jim.

My miner is working ok and stats are being updated for me, I am using the tube pool though. It might just be a problem on regular pool.

I'm also showing the pool as dead.  Oh well, it gave me the opportunity to update my cgminer to 4.8.0 and get my pi updated as well.  My little U2s managed to find a 125M share some time in the past couple weeks... good for them.  Now if they could just find one about 45G .

Yup, you're right. Stats are frozen, I rebooted some miners and they do not connect to solo.ckpool.org 

ckolivas will fix it, no worries