[∞ YH] US/EU/AU solo.ckpool.org 2% fee solo mining 311 blocks solved!

[-ck]

I don't recognise that address type, have never set any donation address for any shitcoins, and don't intend to set up a wallet. Whoever maintains that shitcoin fork of ckpool set the address and you should contact them.

[NotFuzzyWarm]

Dear Con Kolivas and Andrew Smith,
I am writing to you regarding Block 940600 which I successfully mined on the Bitcoin Cash (BCH) network using ckpool-solo. This was my very first block ever mined, achieved after an immense amount of effort, time, and personal resources. <Snip>

BCH has nothing to do with BTC
They are two entirely different coins and are not interchangable. -ck and Kano want nothing to do with BCH. Sorry you screwed up but there is nothing that can be done about it.

[Nexus9090]

Dear Con Kolivas (-ck),
I am writing to you regarding a block I successfully mined on the Bitcoin Cash (BCH) network using ckpool-solo.
Due to a configuration error on my part, the block reward was redirected to a fallback/donation address. I am reaching out to see if there is any possibility of recovering these funds.
-SNIP-

First, where did you clone your ckpool-solo code from?

Because whoever you've cloned it from probably holds that donation address. As CK said, ckpool doesnt support shitcoin. The main ckpool code does not handle BCH it is for Bitcoin BTC only.

So the code-base would have had to have been modified and you must have cloned it from an unsupported source.

Contact the owner of the source you cloned.

The chances of you getting back the BCH you mined is literally zero unless the owner of the cloned code is kind enough to send it to you.

Bottom line as NotFuzzyWarm said, you've screwed up.

Sorry but there's nothing any of us here can do about it. Go back to where you got your source code from.

[blockhilltop]

Day 86 without a Block
US Pool 253% luck; 366.5T shares submitted - nothing
EU Pool 76% luck; 110T shares submitted - zero
AU Pool 13% luck; 19T shares submitted - zilch

Meanwhile BTC down over 30% since the last Block found here.. PoW Gods, I'm begging you! Please make it happen!

[caijh369]

Day 86 without a Block
US Pool 253% luck; 366.5T shares submitted - nothing
EU Pool 76% luck; 110T shares submitted - zero
AU Pool 13% luck; 19T shares submitted - zilch

Meanwhile BTC down over 30% since the last Block found here.. PoW Gods, I'm begging you! Please make it happen!

https://media2.giphy.com/media/v1.Y2lkPTc5MGI3NjExc3Vzc2toNTFzY3d0Z2pkcHc3MDRsNTYwdXc0cTh5cnkzMmh6bzR1ciZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw/xT5LMqhaaz8WkfVcI0/giphy.gif

I have 6T computing power. Will it be me in the next round?

[ethanhunt2023]

I have 6T computing power. Will it be me in the next round?
[/quote]

It can be you but it would be better if it was me because I would donate at least 10% of the block to the community here

[Real-Duke]

I have 6T computing power. Will it be me in the next round?

Everything is possible at any time -> in the end it’s just a matter of luck to solve a block.
Fingers crossed for you, but even more for our group in Willi’s solo pool… why not join us with your 6T @ https://solorun.lima.zone

I would donate at least 10% of the block to the community here

That’s really generous of you
Could you share your mining address here so we can all keep our fingers crossed for you and monitor the address together?

[itrider]

Hi CK

I'm running a solo mining setup with CKPool and I'm trying to implement something similar to the architecture used on solo.ckpool.org.

The idea would be to have:
- one standard instance with a low vardiff for regular miners
- another instance with a much higher vardiff intended for hashpower rentals

Both would ultimately point to the same upstream pool instance that generates the block templates.

My question is the following: 
Would it be possible to keep a single upstream (the low vardiff instance) and run the high vardiff endpoint as a passthrough?

In other words, the upstream instance would still handle the block templates and work generation, while the passthrough would only enforce a higher difficulty for the connected miners.

So the template/work would always come from the upstream, and the passthrough would only modify the expected share difficulty.

Is this a valid approach with ckpool/ckproxy, or would this require a separate pool instance for the high vardiff endpoint?

Thanks for your work on CKPool.

[-ck]

Hi CK

I'm running a solo mining setup with CKPool and I'm trying to implement something similar to the architecture used on solo.ckpool.org.

The idea would be to have:
- one standard instance with a low vardiff for regular miners
- another instance with a much higher vardiff intended for hashpower rentals

Both would ultimately point to the same upstream pool instance that generates the block templates.

My question is the following: 
Would it be possible to keep a single upstream (the low vardiff instance) and run the high vardiff endpoint as a passthrough?

In other words, the upstream instance would still handle the block templates and work generation, while the passthrough would only enforce a higher difficulty for the connected miners.

So the template/work would always come from the upstream, and the passthrough would only modify the expected share difficulty.

Is this a valid approach with ckpool/ckproxy, or would this require a separate pool instance for the high vardiff endpoint?

Thanks for your work on CKPool.

That's complicated. The original ckpool had a cknode mode that did this, but it is NOT compatible with running it in solo mode. However, any port you specify above 4000 instantly makes it a high diff port (1 million min), so just specify two ports, one for regular vardiff and one for high. That's how the public pool currently operates.

[itrider]

That's complicated. The original ckpool had a cknode mode that did this, but it is NOT compatible with running it in solo mode. However, any port you specify above 4000 instantly makes it a high diff port (1 million min), so just specify two ports, one for regular vardiff and one for high. That's how the public pool currently operates.

Hi CK,

I tried it with a port above 4000 for the high diff and it works perfectly.

I also noticed in the logs that the config seems to support a highdiff field to set the difficulty for the high diff port, but I didn’t see it mentioned in the README documentation.

Thanks for the tip!

[mahdi13709]

Hello CK
It seems the pool has encountered a problem after the last update

[caijh369]

Hello CK
It seems the pool has encountered a problem after the last update

I also felt something was wrong. For such a long time, we haven't been able to discover a single block.

[mahdi13709]

Hello CK
It seems the pool has encountered a problem after the last update

I also felt something was wrong. For such a long time, we haven't been able to discover a single block.

lOOK


https://mempool.space/mining/pool/solock


hashrate is dead

[NotFuzzyWarm]

^^ You should ref https://bitcointalk.org/index.php?topic=5568398.msg66496148#msg66496148
Nothing wrong...

[-ck]

The main pool solo.ckpool.org is currently experiencing a DDoS attack. It's probably being caught in the crossfire of an attack directed at the data centre and not being directly attacked. Anyone already connected is unlikely to be affected but it may cause issues for new connections to the pool.

[blockhilltop]

The main pool solo.ckpool.org is currently experiencing a DDoS attack. It's probably being caught in the crossfire of an attack directed at the data centre and not being directly attacked. Anyone already connected is unlikely to be affected but it may cause issues for new connections to the pool.

Thanks for the heads up CK.

I'm guessing this is still ongoing?

I just checked my rigs, they all show they're mining to their assigned secondary server (EU) rather than their assigned primary server (US). Just rebooted one of them to see if they switch back to the US..

[-ck]

The DDoS is finally over, and everyone has fallen back to the pool as far as I can tell. This is the longest DDoS I can ever recall. There is a small possibility it will return which has happened in the past.