CKpool minimum difficulty question | Bitcointalksearch.org

BlackHatCoiner

legendary

Activity: 1512

Merit: 7340

Farewell, Leo

Quote from: Sledge0001 on January 15, 2025, 10:31:03 AM

As I understand it, the mindiff is the lowest difficulty the pool will send to the miners and allow shares back from a miner.

That's what I've understood as well, but I may be unfortunate enough to have found a bug. When my pool solves a block, and sends it to node, node restarts with new difficulty 1. That's expected, normal behavior, because that's how testnet4 works. Once you solve a block with normal, high difficulty, and time travel the chain into the past, then the next blocks can be mined with timestamp up to 2 hours into the future with difficulty=1 (getblocktemplate returns bits=0x1d00ffff). But, with mindiff=100000, I should expect my miners to work on difficulty=100000, not 1.

The problem is that with difficulty=1, and hundreds of TH/s, a chaos prevails, because miners can solve thousands of those blocks within a few seconds, and my computer lags, trying to broadcast all these, if it does not crash.

Edit: From ckpool.log:

Quote

[2025-01-20 21:23:40.523] Possible block solve diff 4404935753.803804 !
[2025-01-20 21:23:40.523] Submitting block data!
[2025-01-20 21:23:40.538] BLOCK ACCEPTED!
[2025-01-20 21:23:40.539] Solved and confirmed block 65995 by tb1qxslu4zwg2fugczrh9qrs722wsr889lj2uktrpz
[2025-01-20 21:23:40.539] User tb1qxslu4zwg2fugczrh9qrs722wsr889lj2uktrpz:{"hashrate1m": "218T", "hashrate5m": "182T", "hashrate1hr": "245T", "hashrate1d": "210T", "hashrate7d": "103T", "shares": 19447215725, "authorised": 1736953782}
[2025-01-20 21:23:40.539] Worker tb1qxslu4zwg2fugczrh9qrs722wsr889lj2uktrpz:{"hashrate1m": "218T", "hashrate5m": "182T", "hashrate1hr": "245T", "hashrate1d": "210T", "hashrate7d": "103T"}
[2025-01-20 21:23:40.539] Block solved after 42701979 shares at 7.5% diff
[2025-01-20 21:23:40.539] Submitting possible block solve share diff 4404935753.803804 !
[2025-01-20 21:23:45.070] Stored local workbase with 0 transactions
[2025-01-20 21:23:45.070] Network diff set to 1.0
[2025-01-20 21:23:45.071] Block hash changed to 0000000000000000f99aee19c8e56dee8ef83d0ae55689c5409d71a6178cc4af
[2025-01-20 21:23:45.536] Possible stale share block solve diff 330589.659255 !
[2025-01-20 21:23:45.537] Submitting block data!
[2025-01-20 21:23:45.542] SUBMIT BLOCK RETURNED: high-hash
[2025-01-20 21:23:45.543] Hash for forced possibly stale block, height 65995 confirms block was REJECTED
[2025-01-20 21:23:45.543] Submitted, but had block 65995 rejected
[2025-01-20 21:23:45.543] Submitting possible block solve share diff 330589.659255 !
[2025-01-20 21:23:45.566] Possible stale share block solve diff 125240.123878 !
[2025-01-20 21:23:45.567] Submitting block data!
[2025-01-20 21:23:45.568] SUBMIT BLOCK RETURNED: high-hash
[2025-01-20 21:23:45.569] Hash for forced possibly stale block, height 65995 confirms block was REJECTED
[2025-01-20 21:23:45.569] Submitted, but had block 65995 rejected
[2025-01-20 21:23:45.569] Submitting possible block solve share diff 125240.123878 !
[2025-01-20 21:23:46.270] Dropped client 679 216.238.102.232 user tb1qkej5t7dd836dykssg9v9mdmsch2z3qq9yv2lf8 worker tb1qkej5t7dd836dykssg9v9mdmsch2z3qq9yv2lf8
[2025-01-20 21:23:46.272] Stored local workbase with 0 transactions
[2025-01-20 21:23:47.617] Possible block solve diff 686566.768655 !
[2025-01-20 21:23:47.617] Submitting block data!
[2025-01-20 21:23:47.618] BLOCK ACCEPTED!
[2025-01-20 21:23:47.618] Solved and confirmed block 65996 by tb1qkej5t7dd836dykssg9v9mdmsch2z3qq9yv2lf8
[2025-01-20 21:23:47.618] User tb1qkej5t7dd836dykssg9v9mdmsch2z3qq9yv2lf8:{"hashrate1m": "246T", "hashrate5m": "224T", "hashrate1hr": "402T", "hashrate1d": "291T", "hashrate7d": "140T", "shares": 26690797387, "authorised": 1736880340}
[2025-01-20 21:23:47.618] Worker tb1qkej5t7dd836dykssg9v9mdmsch2z3qq9yv2lf8:{"hashrate1m": "246T", "hashrate5m": "224T", "hashrate1hr": "402T", "hashrate1d": "291T", "hashrate7d": "140T"}
[2025-01-20 21:23:47.618] Block solved after 700000 shares at 70000000.0% diff
[2025-01-20 21:23:47.618] Submitting possible block solve share diff 686566.768655 !
[2025-01-20 21:23:48.131] Possible block solve diff 64.411158 !
[2025-01-20 21:23:48.131] Submitting block data!
[2025-01-20 21:23:48.132] SUBMIT BLOCK RETURNED: inconclusive

See?

Sledge0001

full member

Activity: 633

Merit: 159

Quote from: BlackHatCoiner on January 15, 2025, 09:29:33 AM

I'm using ckpool software to run my own pool. In the configuration file, it shows this:

Code:

"mindiff" : 1,

Does this mean that the minimum difficulty required for miners to accept my block template is mindiff, or does it mean that regardless of the block template, miners will mine with at least mindiff difficulty? For example, if difficulty is 1, and I set mindiff=1000, will miners mine with difficulty=1000?

As I understand it, the mindiff is the lowest difficulty the pool will send to the miners and allow shares back from a miner.

A Bitaxe for instance may find its difficulty sweet spot around 350-650.

If you set it to 1000 then miners like the Bitaxe will only be allowed get jobs from the pool at 1000 and must submit shares back to the pool at a diff of 1000 or higher.

But that setting does not stop the difficulty from being able to rise faster on larger miners which will end up having a diff well above that 1000 mark.

This setting just sets and locks in the very bottom difficulty for all jobs sent by the pool to the miners.

Hope that helps.