Topic: [∞ YH] solo.ckpool.org 2% fee solo mining 256 blocks solved! - page 215. (Read 102489 times)

Hey everyone. I'm new. My miners keep hitting blocks in Nicehash so, I had to put at least one on here. I just want to make 100% sure I'm doing the "mining address" correctly. I put it as the bitcoin wallet on my Ledger Nano X. I've noticed some posts in here and the address doesn't start with bc1. Should I use a different address than the wallet address I am using? I also put .worker# after my wallet address. That will work, correct?

Surprisingly close to 100% from memory

I believe the last 5-7 blocks here were all below 100.
I remember one was nearly 400% and one was around 40%.
I do agree and feel its the time to crank up my rentals a tad.

Would be nice to see one drop most of the time I feel we hit one around the 80-90 mark so fingers crossed.

@CK do you have a average diff figure for the last 10 or 20 blocks found on the pool?

Would be cool to see what the average solve was for that period.

Thanks again.

Let get that block boys!
I feel one coming here soon.
To pre-emptively extinguish the comments, I understand it not a pool and its solo mining.
Just happy to see others hit here, almost as much as if I hit myself

BTCBTCBTCBTCBTCBTCBTCBTC

I have not been around 'here' much - you are correct ...

I have been in the CryptoIndustry since the first year Satoshi started BitCoin. Especially in GPU mining and all the headaches involved with dealing with the unscrupulous scumbags involved in that arena as well. Thankfully Crypto in general has a great deal of 'good' people. All good though, as a healthy dose of caution and skepticism is always a good thing. I usually watch in the background and offer/involve when I feel it is worth the effort in helping, so again - all good

As for the mining - NiceHash pools almost every miner it get's through it's systems because it's not 'just' a Stratum based 'Broker', but also a Stratum Proxy System. This leads to losses in all sorts of ways, but mainly in latency. There is positives in doing such things also, but only really for smaller miners as an aggregator.

In any case, I think when a pool like this one is actually used directly (miners connecting directly) and not through a Proxy, then it would mine in a very efficient way. Has anyone tried testing this? Collecting a number of miners connecting separately as opposed to connecting through one 'worker' connection via a proxy?

I would be interested in what the outcome would be.

Edit - looks like a lot of the things mentioned were already discussed. Leveing here for posts' sake

Though that test would be a doozy of a test if it could be done.

#crysx

The usual reason is a hashrate so pathetically small that they don't even submit a single share. What mining hardware are you using?

This is probably because you never connected to the pool with this worker (btc address) if you try any random BTC address which didn't submit anything to the pool you will always get


Are you sure you mined on the solo pool using this address?

I have been trying to check my stats but keep getting error message
http://solo.ckpool.org/users/3PcZTNU4RiUfs4hWUJt5uf1DQZ8YJXkNU5

Yeah, but it's fun to watch it go up.

thanks for the info!

I was quite excited when i saw this but now not so much lol
   
Best Share: 1,018,216,864

Port 443 is not there in the config as it's used by the webserver https and not mentioned on the website, and 3335 is uniquely for asicminer tubes. There is absolutely no point using 3335 for anything else.

Port: 443 and 3335 does not work with me. 3333 works fine.

https://www.bilder-upload.eu/thumb/c7f4d5-1602821295.png


how does that work with inserting the picture?)

Actually there is one more, the previous Europe URL still works.

And this takes me back to my reply on NFW's comment which I need to modify, Moeter81 has the right pool settings in the picture, and those de. URLs are for the solo pool despite not having the word "solo" in them.

As far as i know, there are only two valid URLs:

stratum+tcp://solo.ckpool.org:3333
stratum+tcp://rfpool.org:3334

There was a "denode" uri but seems to have gone down.

The Worker field is just the bitcoin address in case you hit the jackpot, you could optionally add the .workername if you want to distinguish the rigs by name, eg:

1PKN98VN2z5gwSGZvGKS2bj8aADZBkyhkZ.MyAsicName

Well according to https://solo.ckpool.org/ there are also IPv4/6 domains solo4.ckpool.org solo6.ckpool.org which i guess may be useful to force one over the other in case of a dual stack situation (or have both in case? but solo.ckpool.org should be enough i think).

Which firmware are you using? I am pretty positive that any miner with Vnish firmware will work with solo.ckpool.org without an issue, please double-check the URL and worker details, they can get a bit tricky especially with missing the "solo" part in the pool URL>

hmm could not get it to work. i will re test

NFW, that is a neat observation, he indeed is pointed to the other "long gone" pool, he should add the solo part in the pool url. the settings are correct, these two URLs belong to the solo pool, however port 443 is down, so only port 3333 works now.

stratum+tcp://de.ckpool.org:443  > will not work
stratum+tcp://de.ckpool.org:3333 > works fine

As for the .de, i think Ck stopped using the server in Germany but de. Url still directs you to the main server located in the U.S, so it should connect just fine.

Um, didn't -ck kill off the Germany node? He's not only pointed there but at the now defunct 'normal' pool ta boot. Not the solo...

Yeah, just ignore me. Tested now. Works fine.