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

lots and lots and lots of switching from coin to coin does cause issues.

I highly doubt that Nicehash has any control over the frequency of your miner's hash board, you are probably aren't running a fixed-frequency firmware and this is why the frequency would fluctuate from time to time, I know (without any rational explanation) that mining to Nicehash seems to cause a much higher failure rate than the ordinary pools with fixed difficulty, but I don't think that has anything to do with the frequency unless I am missing something.

Thank you for your response. The miner does show alive. I do have another question. I noticed the frequency per card is lower when mining on Ckpool. Is that because Nicehash overclocks even when genuine Bitmain firmware is installed?

You got the wrong port and location for the last one, it's actually

stratum+tcp://rfpool.org:3333 (Germany)


This is a passthrough service provided by o_solo_miner, not sure if Ck has anything to do with it, but I have tried it and it works flawlessly, this is great for those countries who piss off the U.S government and are banned from accessing U.S based servers, sort of a mining VPN.


Exactly, I have Cksolo pool as a back-up pool on hundreds of miners, it's a great way to tell if your miner or internet is having issues or it's the primary pool, it's easy to test and it's one of the few (very rare) mining pools that allow you to mine and see your mining status without having to go through the registration and creating worker names process.

Then i have these in my notes for solo.cpool.org unless i missed anything:

stratum+tcp://solo.ckpool.org:3333 (USA)
stratum+tcp://de.ckpool.org:3333 (Germany)
stratum+tcp://rfpool.org:3334 (France)

This pool is also great to diagnose issues some people have with less reliable pools out there, and the fact you don't need an account to mine and verify hash is a huge plus.

It is truly a service to the community.

They keep hitting blocks on NiceHash because they mine Altcoins with very low difficulty, there is no "keep hitting blocks" when you start mining BTC only, so don't set your hopes too high.



Addresses that start with bc1 bech32 (native Segwit) addresses, as far as I know, Ckpool allows that kind of address, as long as your miner status shows "alive" next to cksolo pool and you see your miners getting accepted shares on the pool status page, then you are good to go.

It would be a waste. PC mining bitcoin became redundant over half a dozen years ago.

Would mining to this pool with my gaming pc be a waste of time for me because of a low hash rate or is it worth a try? 

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.