issues with odds to find a block

[Bitdolorian]

I compiled everything and data is flowing from my ckpool clone from ckolivas bit bucket on my own node, the odds to find a block show N/A even after 24hrs of mining

[pdath]

Try CTRL+F5 in your browser.
Failing that, try a "pnpm build" again.

[Bitdolorian]

Try CTRL+F5 in your browser. Failing that, try a "pnpm build" again.

I've done that and still same results.....

[pdath]

If you manually run it from the command line, then browse to the website, do you see any errors appearing in the console?

Something like:
pnpm start --port 3334
(or whatever port you want to use)

[Bitdolorian]

No errors..... I even had copilot help out and ai claims somehow the ckpool clone that I did is not feeding the difficulty of the network

[Z3r0XG]

Ckpool does not save net diff to any files. It only saves % of net diff (as diff in pool.status). This is reverse engineered by ckstats to try to figure out the net diff but it's imprecise. Until the pool itself achieves 0.1% share difficulties the value will be 0 and no calculations can be made.

I had to modify my ckpool fork to save net diff in pool.status, then this could be used with hashrate to calculate the time to solve in ckstats.

If you want to see: stats.heliospool.com

[pdath]

This function calculates the value.

https://github.com/mrv777/ckstats/blob/main/utils/helpers.ts#L139

[Bitdolorian]

I forgot to mention that ckpool makes a bunch of logs per blocks instead of just one log file being updated

Edit
my ckpool config was in debug mode, I fixed the excess logs it was doing, I deleted mrv777 ckstats and reinstall it and still NA for odds block section......

[Bitdolorian]

Ckpool does not save net diff to any files. It only saves % of net diff (as diff in pool.status). This is reverse engineered by ckstats to try to figure out the net diff but it's imprecise. Until the pool itself achieves 0.1% share difficulties the value will be 0 and no calculations can be made.

I had to modify my ckpool fork to save net diff in pool.status, then this could be used with hashrate to calculate the time to solve in ckstats.

If you want to see: stats.heliospool.com

out of curiousity, if that's your page, do you happen to have the script?

[Z3r0XG]

That's my pool, running my forks. My code is a hot mess but here:

https://github.com/Z3r0XG/ckstats-lhr
https://github.com/Z3r0XG/ckpool-lhr

[Bitdolorian]

That's my pool, running my forks. My code is a hot mess but here:

https://github.com/Z3r0XG/ckstats-lhr https://github.com/Z3r0XG/ckpool-lhr

thanks......

[Bitdolorian]

That's my pool, running my forks. My code is a hot mess but here:

https://github.com/Z3r0XG/ckstats-lhr https://github.com/Z3r0XG/ckpool-lhr

Everything is working except the Avg Time to Find a Block I'm guessing is because I haven't found one?

[Z3r0XG]

There is a cut-off - I believe it's 1000 years. So if your hashrate is not high enough to statistically find a block in less than that time, it will show N/A.

Edit: and let me clarify, this is an estimate of how long it would be to find a block based on hashrate, not an average time between blocks. Neither ckpool nor ckstats tracks this.

[Bitdolorian]

There is a cut-off - I believe it's 1000 years. So if your hashrate is not high enough to statistically find a block in less than that time, it will show N/A.

Edit: and let me clarify, this is an estimate of how long it would be to find a block based on hashrate, not an average time between blocks. Neither ckpool nor ckstats tracks this.

oh I know is just an estimate......I'm just making sure I didn't screw up anything, I edited your script to add a BTC icon in the top left corner (you can see in the picture)

[Z3r0XG]

Cool! You can actually create a "public" folder in the root and put things into it, like favicon.ico, and they will be rendered correctly.