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

Someone just got a block
https://blockchain.info/block-index/509485/00000000000000000f2f71296fab8ffbdd91b4678e87245c6d10afbd114377e6

Here's a funny story:

I was mining on here for a few days, haven't found any blocks with my 18 TH/s of Antminers + 18 TH/s rented hashing...
Had Slush's pool as a failover.

During the time the Con's solo pool was down, all 18 TH of my miners went over to Slush's pool, but as I wasn't awake and there was no way to set up a failover, none of the rented miners went over (except the last 15 minutes or so).

Then, like a squad of commandos, my Antminers find a block for Slush's pool (my 4th), and then go back to mining for the solo pool when it comes back up.

So, I did find a block -for Slush... oh well ...

Back to swinging for the fences.

Migration's complete, all mining appears to have resumed as normal. Thanks for your patience.

LOL, I wish...

So, has the migration been completed at this point?

I'm giving you all the hashrate that my AM usb block erupter can give!

You got it!

Just a reminder that the migration downtime is scheduled for the next 24 hours (approximately 17 hours from this post). It will likely be approximately 1 hour's worth though the pool should automatically restart as soon as it has migrated. Worst case scenario I will have to manually intervene to get it going again according to my availability which may take a little longer. Sorry about any inconvenience. Make sure you find your blocks before then, okay?

ta. will check what rejects i get on single address first.

EDIT: no rejects, and only a triple of errors on first boot. 2 x SP10 @ low clock.

ADD:

and a bfl single @55GH/s


lots of rejects on an s3

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%