[∞ YH] solo.ckpool.org 2% fee solo mining 283 blocks solved!

[Derter]

This is private question. Need direct contact of support.

[1715417961]

1715417961

[1715417961]

1715417961

[willi9974]

This is private question. Need direct contact of support.

Than use a PM direkt to CK 

[armenma]

Hi, I am attempting to run the setupsoloproxy.sh on ubuntu and ckproxy is missing. I checked the http://ck.kolivas.org/apps/soloproxy and ckproxy is missing from the directory as well. Can someone please help me run the script? Is there a step by step direction I can use? or connect with the author?

Please help! I can send snapshots is the ask in unclear.

Thank you in advance.

[hiaxis]

Question for you all. I was looking at the solo pool stats and noticed the number of rejected shares versus total shares accepted.

"accepted": 24575964250308, "rejected": 8543041616789,

Is it normal to have such a high ratio of rejected to accepted shares? It's almost 35%.

Just curious...

[Josek8]

Question for you all. I was looking at the solo pool stats and noticed the number of rejected shares versus total shares accepted.

"accepted": 24575964250308, "rejected": 8543041616789,

Is it normal to have such a high ratio of rejected to accepted shares? It's almost 35%.

Just curious...

Good questiong¡¡

I would add that CKPool has been almost two months with an average of 19P more or less without hitting a block, could it be due to the increase of the difficulty in these last months?

I think that 19P is like 190 asics of 100Th/s and it scares me to believe that it takes so many machines to not hit a block in 2 months.

[-ck]

I would add that CKPool has been almost two months with an average of 19P more or less without hitting a block, could it be due to the increase of the difficulty in these last months?

I think that 19P is like 190 asics of 100Th/s and it scares me to believe that it takes so many machines to not hit a block in 2 months.

Nope, it's just because 19P is a piddly small amount of hashrate. The difficulty increases have only been modest recently.

[-ck]

Question for you all. I was looking at the solo pool stats and noticed the number of rejected shares versus total shares accepted.

"accepted": 24575964250308, "rejected": 8543041616789,

Is it normal to have such a high ratio of rejected to accepted shares? It's almost 35%.

Just curious...

It's not normal, it's likely shitty asic firmware. If the reported hashrate is still fine and consistent with the hardware then just ignore it, it means it's submitting shares below difficulty or something stupid.

[Josek8]

Question for you all. I was looking at the solo pool stats and noticed the number of rejected shares versus total shares accepted.

"accepted": 24575964250308, "rejected": 8543041616789,

Is it normal to have such a high ratio of rejected to accepted shares? It's almost 35%.

Just curious...

It's not normal, it's likely shitty asic firmware. If the reported hashrate is still fine and consistent with the hardware then just ignore it, it means it's submitting shares below difficulty or something stupid.

Ck, I think you are referring to the Ckpool Pool data, now marked as rejected 8544606234606 and accepted 25021741637908.

[hiaxis]

Question for you all. I was looking at the solo pool stats and noticed the number of rejected shares versus total shares accepted.

"accepted": 24575964250308, "rejected": 8543041616789,

Is it normal to have such a high ratio of rejected to accepted shares? It's almost 35%.

Just curious...

It's not normal, it's likely shitty asic firmware. If the reported hashrate is still fine and consistent with the hardware then just ignore it, it means it's submitting shares below difficulty or something stupid.

So there's enough shitty firmware out there running in miners solo mining on this pool to cause over 1/3 of the total shares submitted by the entire solo pool to be rejected? That seems crazy! I could understand if a small portion of the miners connected to the pool had that issue but over 1/3 of our shares submitted are being rejected. Is this due to rentals maybe?

I'm not an expert by any stretch in this area which is why I'm trying to understand more about it. It just seems like a very gross inefficiency if 1/3 of our total shares on the solo pool as a whole are being rejected.

[-ck]

Question for you all. I was looking at the solo pool stats and noticed the number of rejected shares versus total shares accepted.

"accepted": 24575964250308, "rejected": 8543041616789,

Is it normal to have such a high ratio of rejected to accepted shares? It's almost 35%.

Just curious...

It's not normal, it's likely shitty asic firmware. If the reported hashrate is still fine and consistent with the hardware then just ignore it, it means it's submitting shares below difficulty or something stupid.

So there's enough shitty firmware out there running in miners solo mining on this pool to cause over 1/3 of the total shares submitted by the entire solo pool to be rejected? That seems crazy! I could understand if a small portion of the miners connected to the pool had that issue but over 1/3 of our shares submitted are being rejected. Is this due to rentals maybe?

I'm not an expert by any stretch in this area which is why I'm trying to understand more about it. It just seems like a very gross inefficiency if 1/3 of our total shares on the solo pool as a whole are being rejected.

It's probably one miner, likely a rental related phenomenon. I might investigate.

[hiaxis]

Question for you all. I was looking at the solo pool stats and noticed the number of rejected shares versus total shares accepted.

"accepted": 24575964250308, "rejected": 8543041616789,

Is it normal to have such a high ratio of rejected to accepted shares? It's almost 35%.

Just curious...

It's not normal, it's likely shitty asic firmware. If the reported hashrate is still fine and consistent with the hardware then just ignore it, it means it's submitting shares below difficulty or something stupid.

So there's enough shitty firmware out there running in miners solo mining on this pool to cause over 1/3 of the total shares submitted by the entire solo pool to be rejected? That seems crazy! I could understand if a small portion of the miners connected to the pool had that issue but over 1/3 of our shares submitted are being rejected. Is this due to rentals maybe?

I'm not an expert by any stretch in this area which is why I'm trying to understand more about it. It just seems like a very gross inefficiency if 1/3 of our total shares on the solo pool as a whole are being rejected.

It's probably one miner, likely a rental related phenomenon. I might investigate.

Thank you ck. I'm curious what you find. Looking at it today, rejected total seems to still be ticking up quickly. If our average hash rate since the last block was let's say 15PH, it's concerning if we, as a "pool", had 5PH worth of those shares rejected. Something just doesn't seem right but again, I'm not an expert in this.

[-ck]

Looking through the logs I can see one miner submitting mostly rejects - all below target level, suggesting dodgy firmware on his hardware, but I don't see anything else untoward. That might be enough on its own. I suggest each individual user check their own stats and see if their hashrate at the pool reflects their hardware - ckpool reports hashrate based ONLY on accepted shares.

[demag]

New to this.  Bought a futurebit apollo btc to try it out.  It keeps showing inactive for my status connection to ckpool.  Does anyone know why?

[Sledge0001]

New to this.  Bought a futurebit apollo btc to try it out.  It keeps showing inactive for my status connection to ckpool.  Does anyone know why?

You must have your pool configured incorrectly.

Use this as your pool url:

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

Then enter your BTC address . miner name... For an example on the Username if my worker name was ApolloBTC01 I would enter  bc1qzmntuax0kgys5elzwcn6sj04yxxxxxxx.ApolloBTC01

And enter a lower case x as the password.


Then save and restart the apollo and you should be mining.

[hiaxis]

Looking through the logs I can see one miner submitting mostly rejects - all below target level, suggesting dodgy firmware on his hardware, but I don't see anything else untoward. That might be enough on its own. I suggest each individual user check their own stats and see if their hashrate at the pool reflects their hardware - ckpool reports hashrate based ONLY on accepted shares.

Thank you for the info ck. That's good to know. So if the difficulty is too low on a particular miner, even one with a relatively low hash rate, it's possible to rack up a large amount of rejected shares. That's good to know!

[citb0in]

Solo miners - Attention
If you are interested in group based solo runs, you are welcome to join the BLOCK SOLVERS group



Stake is only 0.001 BTC, we rent hashpower 2-3 PH/s and send it to soloCK pool. The motto of this solo mining group is: participate cheaply and regularly with the hope of mining a block and collecting the reward.

All info can be found in the citb0in Solo-Mining Group - BLOCK SOLVERS thread. Join now, may the luck be with us 

[Josek8]

Looking through the logs I can see one miner submitting mostly rejects - all below target level, suggesting dodgy firmware on his hardware, but I don't see anything else untoward. That might be enough on its own. I suggest each individual user check their own stats and see if their hashrate at the pool reflects their hardware - ckpool reports hashrate based ONLY on accepted shares.

Reviewing one of my miners, he has been mining in CKPool for 18 days and yields the following data:

Diff   Priorit   Accepted         DiffA             DiffR   Rejected Stale           LSDiff           LSTime

105K     0         458879 38400602087   19012175     227         22           104698            0:00:00

Would it be possible to get a screenshot of what my miner is doing?

I try to look for information in Spanish about what the miner actually does, what data it takes into account, the Hashes it sends but I can't find any information about this.

[demag]

New to this.  Bought a futurebit apollo btc to try it out.  It keeps showing inactive for my status connection to ckpool.  Does anyone know why?

You must have your pool configured incorrectly.

Use this as your pool url:

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

Then enter your BTC address . miner name... For an example on the Username if my worker name was ApolloBTC01 I would enter  bc1qzmntuax0kgys5elzwcn6sj04yxxxxxxx.ApolloBTC01

And enter a lower case x as the password.


Then save and restart the apollo and you should be mining.

I copied and pasted the url.  But, for the username.  I don't know the worker name(s), so I just put my BTC address; since it said I could do it without the worker name(s). Then I put x for the password.  It still shows inactive.

[mondayshot]

When I point my USB-Miner (GekkoScience Newpac) to solo.ckpool.org and I'm running cgminer as mining-software, is it technical possible to use a Bech32-adress as payout-adress

I am refering to this post https://bitcointalk.org/index.php?topic=5373190.0 where user 100knot2dae said cgminer does not support Bech (bc1...) addresses for solo mining.

So this command in cgminer would not work?!

Code:

sudo ./cgminer -o stratum+tcp://solo.ckpool.org:3333 -u bc1q-my-btc-payout-adress.gekko -p x --suggest-diff 256 --gekko-newpac-freq 400

[citb0in]

The link you referred to means "SOLO mining on an own full-node". In this case you are using solo.ckpool.org and you can use a bc1q... address of course. Just look at so many posting, a lot of users mining on soloCK pool with Bech32 address. In case it would not have been supported, you would have received an error message All good, you are ready to mine