A new Bestshare
Live View Link:
https://solo.ckpool.org/users/bc1qprzt4ks2ne8s7pfazgwxu59kgxj9j6j6ekful7
now 7.9T Live View Link:
https://solo.ckpool.org/users/bc1qprzt4ks2ne8s7pfazgwxu59kgxj9j6j6ekful7
Topic: [∞ YH] solo.ckpool.org 2% fee solo mining 256 blocks solved! - page 5. (Read 102344 times)
October 14, 2024, 09:26:15 PM
October 14, 2024, 12:26:56 PM
we are started with Blockparty 71 at 25 PHs (Runtime ~ 3d 15h)
Live View Link:
https://solo.ckpool.org/users/bc1qprzt4ks2ne8s7pfazgwxu59kgxj9j6j6ekful7
Bitcoin Difficulty:
92.049.594.548.485
Best Share:
3.897.944.946
531.518.966
327.596.649
68.139.490
51.463.812
Live View Link:
https://solo.ckpool.org/users/bc1qprzt4ks2ne8s7pfazgwxu59kgxj9j6j6ekful7
Bitcoin Difficulty:
92.049.594.548.485
Best Share:
3.897.944.946
531.518.966
327.596.649
68.139.490
51.463.812
good luck to all!
Live View Link:
https://solo.ckpool.org/users/bc1qprzt4ks2ne8s7pfazgwxu59kgxj9j6j6ekful7
{
"hashrate1m": "27.1P",
"hashrate5m": "24.4P",
"hashrate1hr": "21.5P",
"hashrate1d": "13.4P",
"hashrate7d": "6.21P",
"lastshare": 1728931654,
"workers": 1,
"shares": 27754348087867,
"bestshare": 6899243272646.506,
"bestever": 56165933569967,
"authorised": 1705433626,
"worker": [
{
"workername": "bc1qprzt4ks2ne8s7pfazgwxu59kgxj9j6j6ekful7_blockparty71",
"hashrate1m": "27.1P",
"hashrate5m": "24.4P",
"hashrate1hr": "21.5P",
"hashrate1d": "13.4P",
"hashrate7d": "2.94P",
"lastshare": 1728931654,
"shares": 448314567828,
"bestshare": 2719301435941.619,
"bestever": 2719301435941
}
]
}
Bitcoin Difficulty:
92.049.594.548.485
Best Share:
2.719.301.435.941
189.437.616.341
40.384.655.579
3.897.944.946
531.518.966
327.596.649
68.139.490
51.463.812
October 14, 2024, 12:16:36 PM
we are started with Blockparty 71 at 25 PHs (Runtime ~ 3d 15h)
Live View Link:
https://solo.ckpool.org/users/bc1qprzt4ks2ne8s7pfazgwxu59kgxj9j6j6ekful7
Bitcoin Difficulty:
92.049.594.548.485
Best Share:
3.897.944.946
531.518.966
327.596.649
68.139.490
51.463.812
Live View Link:
https://solo.ckpool.org/users/bc1qprzt4ks2ne8s7pfazgwxu59kgxj9j6j6ekful7
Bitcoin Difficulty:
92.049.594.548.485
Best Share:
3.897.944.946
531.518.966
327.596.649
68.139.490
51.463.812
good luck to all!
October 14, 2024, 04:15:06 AM
The longer scale looks good, but the dynamic sliders aren't working presently.
If I click or drag the sliders the charts go blank and the page requires a refresh to bring them back.
I know its a work in progress, so I'll keep watching and let you have feedback as and when I can.
Its coming together though, thanks again for your efforts.
If I click or drag the sliders the charts go blank and the page requires a refresh to bring them back.
I know its a work in progress, so I'll keep watching and let you have feedback as and when I can.
Its coming together though, thanks again for your efforts.
Thanks! Yeah, still testing it, what browser are you using?
Nice job on the variable chart scales, all seems to be working well now.
I was wondering, as an additonal feature, would it be possible to put markers on the chart showing when a new block was started and its block number?
Thanks
October 13, 2024, 12:27:25 PM
we are started with Blockparty 71 at 25 PHs (Runtime ~ 3d 15h)
Live View Link:
https://solo.ckpool.org/users/bc1qprzt4ks2ne8s7pfazgwxu59kgxj9j6j6ekful7
{
"hashrate1m": "25.7P",
"hashrate5m": "16.1P",
"hashrate1hr": "2.15P",
"hashrate1d": "106T",
"hashrate7d": "3.81P",
"lastshare": 1728840392,
"workers": 1,
"shares": 27307927511680,
"bestshare": 6899243272646.506,
"bestever": 56165933569967,
"authorised": 1705433626,
"worker": [
{
"workername": "bc1qprzt4ks2ne8s7pfazgwxu59kgxj9j6j6ekful7_blockparty71",
"hashrate1m": "25.7P",
"hashrate5m": "16.1P",
"hashrate1hr": "2.15P",
"hashrate1d": "93.9T",
"hashrate7d": "13.4T",
"lastshare": 1728840392,
"shares": 1893991641,
"bestshare": 3897944946.761396,
"bestever": 3897944946
}
]
}
Bitcoin Difficulty:
92.049.594.548.485
Best Share:
3.897.944.946
531.518.966
327.596.649
68.139.490
51.463.812
Live View Link:
https://solo.ckpool.org/users/bc1qprzt4ks2ne8s7pfazgwxu59kgxj9j6j6ekful7
{
"hashrate1m": "25.7P",
"hashrate5m": "16.1P",
"hashrate1hr": "2.15P",
"hashrate1d": "106T",
"hashrate7d": "3.81P",
"lastshare": 1728840392,
"workers": 1,
"shares": 27307927511680,
"bestshare": 6899243272646.506,
"bestever": 56165933569967,
"authorised": 1705433626,
"worker": [
{
"workername": "bc1qprzt4ks2ne8s7pfazgwxu59kgxj9j6j6ekful7_blockparty71",
"hashrate1m": "25.7P",
"hashrate5m": "16.1P",
"hashrate1hr": "2.15P",
"hashrate1d": "93.9T",
"hashrate7d": "13.4T",
"lastshare": 1728840392,
"shares": 1893991641,
"bestshare": 3897944946.761396,
"bestever": 3897944946
}
]
}
Bitcoin Difficulty:
92.049.594.548.485
Best Share:
3.897.944.946
531.518.966
327.596.649
68.139.490
51.463.812
October 13, 2024, 06:10:28 AM
i'm sorry but the calculations are wrong
98298136921020 is 106.78823454159% of 92049594548485.47.
and yet it is displaying 107% , it did not reach 107% yet according to calculations
98298136921020 is 106.78823454159% of 92049594548485.47.
and yet it is displaying 107% , it did not reach 107% yet according to calculations
Rounding up?
106.49999999 = 106%
106.50000000 = 107%
October 13, 2024, 05:47:42 AM
i'm sorry but the calculations are wrong
98298136921020 is 106.78823454159% of 92049594548485.47.
and yet it is displaying 107% , it did not reach 107% yet according to calculations
98298136921020 is 106.78823454159% of 92049594548485.47.
and yet it is displaying 107% , it did not reach 107% yet according to calculations
October 13, 2024, 05:02:14 AM
hello it seems that the stats are stuck at 106%
while at the time of writing it should be 106.4 %
{"diff": 106.0, "accepted": 97998006578111,
It rounds off once above 100%, it's still rising and is 107% now. while at the time of writing it should be 106.4 %
{"diff": 106.0, "accepted": 97998006578111,
October 13, 2024, 04:53:17 AM
Thanks! Yeah, still testing it, what browser are you using?
Firefox build 131.02 (64bit) on Win 10.
October 13, 2024, 02:22:00 AM
hello it seems that the stats are stuck at 106%
while at the time of writing it should be 106.4 %
{"diff": 106.0, "accepted": 97998006578111,
while at the time of writing it should be 106.4 %
{"diff": 106.0, "accepted": 97998006578111,
October 12, 2024, 09:28:33 PM
The longer scale looks good, but the dynamic sliders aren't working presently.
If I click or drag the sliders the charts go blank and the page requires a refresh to bring them back.
I know its a work in progress, so I'll keep watching and let you have feedback as and when I can.
Its coming together though, thanks again for your efforts.
If I click or drag the sliders the charts go blank and the page requires a refresh to bring them back.
I know its a work in progress, so I'll keep watching and let you have feedback as and when I can.
Its coming together though, thanks again for your efforts.
Thanks! Yeah, still testing it, what browser are you using?
October 12, 2024, 03:32:45 PM
Testing selectable/dynamic x-axis now here: https://ckstats.com/users/bc1qeuupt2tgerfum8jclt8aklu9cdmzzkwml9lg7c
If it looks good, we can push an update
If it looks good, we can push an update
The longer scale looks good, but the dynamic sliders aren't working presently.
If I click or drag the sliders the charts go blank and the page requires a refresh to bring them back.
I know its a work in progress, so I'll keep watching and let you have feedback as and when I can.
Its coming together though, thanks again for your efforts.
October 12, 2024, 02:15:00 PM
Thanks for the suggestion. To keep testing costs down, only doing updates every 10min there. The new version looks to be updating every 1 minute now
solostats.ckpool.org has been set to update one minutely since I put it on my vps from the beginning since the pool only updates the stats that frequently itself. Only the stratum templates update every 30s October 12, 2024, 10:08:40 AM
Your stats are not real, pool update happens once every 30 sec. You are reading updated stats once every 10-30 mins or so 
). 1m 5m etc has changed many times in this interval, not to mention users stats.
). 1m 5m etc has changed many times in this interval, not to mention users stats.Thanks for the suggestion. To keep testing costs down, only doing updates every 10min there. The new version looks to be updating every 1 minute now
October 12, 2024, 10:07:21 AM
Dynamic or selectable scaling would be a real nice to have. Some of the graphs on other bitcoin stats scale with the mouse-wheel. So this might be a cool feature to include if you can.
BTW, thanks for fixing the "unnamed worker"
Thanks for your help.
Cheers
G.
BTW, thanks for fixing the "unnamed worker"
Thanks for your help.
Cheers
G.
Testing selectable/dynamic x-axis now here: https://ckstats.com/users/bc1qeuupt2tgerfum8jclt8aklu9cdmzzkwml9lg7c
If it looks good, we can push an update
October 12, 2024, 09:54:38 AM
No problem -CK, thanks for taking a look.
With reference to the charts, they are only 2 hours in length; its been monitoring for about 5 hours now but only 2 hours are shown.
It would be nice if this was 24hour if you can do it without too much hassle or as an extension selectable from 30minutes to 7 days maybe?
Anway, thank you and the author for your efforts.
With reference to the charts, they are only 2 hours in length; its been monitoring for about 5 hours now but only 2 hours are shown.
It would be nice if this was 24hour if you can do it without too much hassle or as an extension selectable from 30minutes to 7 days maybe?
Anway, thank you and the author for your efforts.
Hey
Dynamic scaling of the x axis can be looked at. It's only showing 2 hours of data because it originally assumed 10 min updates, but they are happening faster now. Dynamic scaling should fix this, if not the hardcoded number can be updated to reflect the faster updates and show more data points
https://github.com/mrv777/ckstats/blob/main/lib/api.ts#L11
The backend is setup to save up to 7 days worth of data i believe before the cleaning script removes old data points, so 7 days worth of data should already be available, just a matter of showing it on the frontend in a nice way
https://github.com/mrv777/ckstats/blob/main/scripts/cleanOldStats.js#L7
Dynamic or selectable scaling would be a real nice to have. Some of the graphs on other bitcoin stats scale with the mouse-wheel. So this might be a cool feature to include if you can.
BTW, thanks for fixing the "unnamed worker"
Thanks for your help.
Cheers
G.
October 12, 2024, 09:52:36 AM
It only showed 2 hours because that's when the stats began; it will show longer over time (I think.) The difficulty is notated wrong - that's meant to be pool % not T, I'd already informed the author and it will be fixed.
No problem -CK, thanks for taking a look.
With reference to the charts, they are only 2 hours in length; its been monitoring for about 5 hours now but only 2 hours are shown.
It would be nice if this was 24hour if you can do it without too much hassle or as an extension selectable from 30minutes to 7 days maybe?
Anway, thank you and the author for your efforts.
Thank you!
October 12, 2024, 09:45:56 AM
No problem -CK, thanks for taking a look.
With reference to the charts, they are only 2 hours in length; its been monitoring for about 5 hours now but only 2 hours are shown.
It would be nice if this was 24hour if you can do it without too much hassle or as an extension selectable from 30minutes to 7 days maybe?
Anway, thank you and the author for your efforts.
With reference to the charts, they are only 2 hours in length; its been monitoring for about 5 hours now but only 2 hours are shown.
It would be nice if this was 24hour if you can do it without too much hassle or as an extension selectable from 30minutes to 7 days maybe?
Anway, thank you and the author for your efforts.
Hey
Dynamic scaling of the x axis can be looked at. It's only showing 2 hours of data because it originally assumed 10 min updates, but they are happening faster now. Dynamic scaling should fix this, if not the hardcoded number can be updated to reflect the faster updates and show more data points
https://github.com/mrv777/ckstats/blob/main/lib/api.ts#L11
The backend is setup to save up to 7 days worth of data i believe before the cleaning script removes old data points, so 7 days worth of data should already be available, just a matter of showing it on the frontend in a nice way
https://github.com/mrv777/ckstats/blob/main/scripts/cleanOldStats.js#L7
Your stats are not real, pool update happens once every 30 sec. You are reading updated stats once every 10-30 mins or so
). 1m 5m etc has changed many times in this interval, not to mention users stats. October 12, 2024, 09:20:10 AM
No problem -CK, thanks for taking a look.
With reference to the charts, they are only 2 hours in length; its been monitoring for about 5 hours now but only 2 hours are shown.
It would be nice if this was 24hour if you can do it without too much hassle or as an extension selectable from 30minutes to 7 days maybe?
Anway, thank you and the author for your efforts.
With reference to the charts, they are only 2 hours in length; its been monitoring for about 5 hours now but only 2 hours are shown.
It would be nice if this was 24hour if you can do it without too much hassle or as an extension selectable from 30minutes to 7 days maybe?
Anway, thank you and the author for your efforts.
Hey
Dynamic scaling of the x axis can be looked at. It's only showing 2 hours of data because it originally assumed 10 min updates, but they are happening faster now. Dynamic scaling should fix this, if not the hardcoded number can be updated to reflect the faster updates and show more data points
https://github.com/mrv777/ckstats/blob/main/lib/api.ts#L11
The backend is setup to save up to 7 days worth of data i believe before the cleaning script removes old data points, so 7 days worth of data should already be available, just a matter of showing it on the frontend in a nice way
https://github.com/mrv777/ckstats/blob/main/scripts/cleanOldStats.js#L7
October 12, 2024, 08:28:25 AM
It only showed 2 hours because that's when the stats began; it will show longer over time (I think.) The difficulty is notated wrong - that's meant to be pool % not T, I'd already informed the author and it will be fixed.
No problem -CK, thanks for taking a look.
With reference to the charts, they are only 2 hours in length; its been monitoring for about 5 hours now but only 2 hours are shown.
It would be nice if this was 24hour if you can do it without too much hassle or as an extension selectable from 30minutes to 7 days maybe?
Anway, thank you and the author for your efforts.
Jump to: