Pages:
Author

Topic: [∞ YH] solo.ckpool.org 2% fee solo mining 256 blocks solved! - page 24. (Read 102344 times)

jr. member
Activity: 72
Merit: 3
I think this is the first time I've seen 200% diff or pool luck, though I'm relatively new here. Good luck everyone, hope the next Block drops soon. Willi, I'm trying to get into run 66, but I think I'm going to have to skip this one buddy. Fingers crossed for everyone, I hope a small SOLO artist hits this next one, and soon Smiley
legendary
Activity: 3500
Merit: 2792
Enjoy 500% bonus + 70 FS
At the moment a little unlucky

{"runtime": 31755195, "lastupdate": 1718198772, "Users": 5640, "Workers": 12138, "Idle": 4014, "Disconnected": 1098}
{"hashrate1m": "146P", "hashrate5m": "147P", "hashrate15m": "148P", "hashrate1hr": "151P", "hashrate6hr": "262P", "hashrate1d": "347P", "hashrate7d": "506P"}
{"diff": 200.0, "accepted": 167121813174119, "rejected": 154817363533, "bestshare": 50721548677912, "SPS1m": 903.0, "SPS5m": 910.0, "SPS15m": 910.0, "SPS1h": 912.0}

cross my fingers for a new block and bestcase for our LongtimeRun, Blockparty 66 or WilliPool Bitaxe Group !!!

PS: Blockparty 66 will start, if we collect last 0,01 BTC from one ore more member...
member
Activity: 249
Merit: 83
So many numbers and so little time
That sounds like a nice feature, but there are some challenges with implementing it. The pool best share value is incremented until a better share replaces it, so the best share for each block would mostly repeat. This means there wouldn't be much variation in the data to visualize.

I could query the entire set of monitored users for their best shares, but this might not be relevant for what you're looking for.

Thanks for the suggestion!

Thanks VK,

I guess that would require changes to the pool code as well so that it tracked a best share for a given block as well as the overall best share since the last block was discovered.

I had another though on it as well, such that you could do a 3D graph of the data so X axis would be block number, Y axis would be best share, Z could be either by miner or by hash rate. That might have been interesting.

Nevertheless, it seems like the current pool code isnt able to provide meaningful data to do this, which is a shame.

Anyway it was just an idea.

Thanks

G.

member
Activity: 59
Merit: 18
Added SPS chart on solostats.ckpool.org
If any need custom things, let me know.

Hi VK

I was wondering if you might be able to add a "best share this block" report?

While we can track the overall best share since the last block was found, we cant see what the best was achieved for a given block.

To elaborate, I was thinking you might be able to graph a block number on the X axis and the best share for that block on the Y? for the last 100 blocks or something like that?

I know its largely another meaningless statistic but I find it interesting never the less.

Thanks

G.

That sounds like a nice feature, but there are some challenges with implementing it. The pool best share value is incremented until a better share replaces it, so the best share for each block would mostly repeat. This means there wouldn't be much variation in the data to visualize.

I could query the entire set of monitored users for their best shares, but this might not be relevant for what you're looking for.

Thanks for the suggestion!
member
Activity: 249
Merit: 83
So many numbers and so little time
Added SPS chart on solostats.ckpool.org
If any need custom things, let me know.

Hi VK

I was wondering if you might be able to add a "best share this block" report?

While we can track the overall best share since the last block was found, we cant see what the best was achieved for a given block.

To elaborate, I was thinking you might be able to graph a block number on the X axis and the best share for that block on the Y? for the last 100 blocks or something like that?

I know its largely another meaningless statistic but I find it interesting never the less.

Thanks

G.
jr. member
Activity: 68
Merit: 3
cool.  thank you ck!

so as long there isn't some generic work distribution method that different pool operators use, but instead each pool operator uses their own, unique work distribution method, then every ASIC miner in the world should be have unique starting work and have unique hashes...and that is an amazing technology!!!
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
jr. member
Activity: 68
Merit: 3
The mining hardware gets a base of work that it can send off unique starting work to trillions of hashing units. Unless the hardware is a broken design there is zero chance of their work overlapping. Speed is irrelevant, every single hash unit operates on its own independently.

Yes, thank you for taking the time to answer this question.  So the individual hashing units in an ASIC should be trying unique hashes, but what about separate ASICs in a farm?  Are they each getting unique starting work too?  If so, is that because of the pool software?  I've always been so curious about this.  I don't doubt that it's fair, but I wonder if there is another ASIC somewhere in the world that is getting the same starting work as my weaker ASIC is, in which case, they would beat me to the solution every time.  I would imagine the pools have a way to randomly distribute unique starting work to every worker.  That way another pool doesn't assign the same starting work to a worker in their pool.  That would make sense in my head, but I won't be surprised if I'm wrong  Cheesy
jr. member
Activity: 68
Merit: 3

[/quote]

Trx fees are up, would be nice for a solo miner to hit a nice big block - I like big blocks and I cannot lie!

[/quote]

...you other miners can't deny!  had to laugh at your remix  Grin


hey while i'm here....I forgot, how do i calculate what my best share needs to be based on current difficulty?  seems like a couple years ago I was looking for a 12 digit number...maybe?
jr. member
Activity: 72
Merit: 3
The mining hardware gets a base of work that it can send off unique starting work to trillions of hashing units. Unless the hardware is a broken design there is zero chance of their work overlapping. Speed is irrelevant, every single hash unit operates on its own independently.

Appreciate the clarification CK, thank you for sticking around to teach and help the willing masses my brother! Truly legendary effort, once again thank you CK!

And again thanks to (VKBit, Victor?) the gentleman who has provided us with the enhanced stats page -very nicely done sir!

Trx fees are up, would be nice for a solo miner to hit a nice big block - I like big blocks and I cannot lie!

Good luck everyone and LFG gentlemen!
member
Activity: 249
Merit: 83
So many numbers and so little time
The mining hardware gets a base of work that it can send off unique starting work to trillions of hashing units. Unless the hardware is a broken design there is zero chance of their work overlapping. Speed is irrelevant, every single hash unit operates on its own independently.

Hi -ck

Thanks for the response.

Arguably, isnt it the miner software that issues starting nonce to an ASIC, not hardware.

So while a pool may issue a base of work to the miner software, the miner software must surely determine if that base of work is followed and what starting nonce to issue to an ASIC.

Which means the miner software must track what nonce's it has issued from the base of work that would be sent to an ASIC in order to prevent overlap or rehashing from a previously used nonce.


I've dug through the code of CGMiner to try and understand how the work is issued, but it is a very complex piece of software with little in the way of code level documentation making it quite hard to understand the program flow.

Thanks for your help, just trying to make sense of the flow of work.

-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
The mining hardware gets a base of work that it can send off unique starting work to trillions of hashing units. Unless the hardware is a broken design there is zero chance of their work overlapping. Speed is irrelevant, every single hash unit operates on its own independently.
member
Activity: 249
Merit: 83
So many numbers and so little time
I've always wondered how each ASIC guesses the solution to a block.  Like if I had 2 ASICs, 1 very powerful and 1 very weak, do they both start at the same hash and continue incrementing up until a solution is found?  If that were the case, the weaker ASIC would never find the solution, so surely that isn't how it works.

So if both of the ASICs are making different random guesses, what controls the guesses?  In other words, how is each ASIC choosing what to input in the hashing function to see if it hashes into the correct solution to the block?

I don't even know if I'm explaining myself clearly for anyone to even understand me lol I'm sure I'm saying something wrong...but if anyone is able to make sense out of that question, and are able to answer, I would be most grateful!

I've often wondered the same thing, what determines the starting nonce for each chip?

In a system with more than one chip in a chain, how is the workload distributed across the chain of chips, or is each chip given its own starting nonce at random?

If its a random selection for each chip what's to stop two overlapping nonces or a nonce that has already been scanned? Which would reduce the efficiency of a miner

Does the pool determine starting nonce for each share? If it does what's to stop it preferentially issuing shares to faster miners or what is to stop it from duplication of nonces issued?

Without really digging into the guts of both the miner control software and the pool server software, it is difficult to find an answer.

jr. member
Activity: 68
Merit: 3
I've always wondered how each ASIC guesses the solution to a block.  Like if I had 2 ASICs, 1 very powerful and 1 very weak, do they both start at the same hash and continue incrementing up until a solution is found?  If that were the case, the weaker ASIC would never find the solution, so surely that isn't how it works.

So if both of the ASICs are making different random guesses, what controls the guesses?  In other words, how is each ASIC choosing what to input in the hashing function to see if it hashes into the correct solution to the block?

I don't even know if I'm explaining myself clearly for anyone to even understand me lol I'm sure I'm saying something wrong...but if anyone is able to make sense out of that question, and are able to answer, I would be most grateful!
member
Activity: 249
Merit: 83
So many numbers and so little time
Those fees are eye watering  Shocked




Good luck everyone!

Mine on.
member
Activity: 59
Merit: 18
Added SPS chart on solostats.ckpool.org
If any need custom things, let me know.
newbie
Activity: 1
Merit: 0
Congratulations to our whale miner with 1.5EH for solving the 289th solo block solved at solo.ckpool.org !

Code:
[2024-05-30 03:08:08.005] Possible block solve diff 118808888859878.171875 !
[2024-05-30 03:08:08.116] BLOCK ACCEPTED!
[2024-05-30 03:08:08.122] Solved and confirmed block 845735 by 3Kbu2CKYAQ5F7FzbvMKDAXWK9AaMiQRjZj.trit05
[2024-05-30 03:08:08.122] User 3Kbu2CKYAQ5F7FzbvMKDAXWK9AaMiQRjZj:{"hashrate1m": "1.42E", "hashrate5m": "1.38E", "hashrate1hr": "1.35E", "hashrate1d": "725P", "hashrate7d": "150P", "shares": 22543766287400, "authorised": 1716946332}
[2024-05-30 03:08:08.122] Worker 3Kbu2CKYAQ5F7FzbvMKDAXWK9AaMiQRjZj.trit05:{"hashrate1m": "134P", "hashrate5m": "131P", "hashrate1hr": "124P", "hashrate1d": "49P", "hashrate7d": "8.71P"}
[2024-05-30 03:08:08.160] Block solved after 128314299876180 shares at 152.1% diff

https://mempool.space/block/000000000000000000025e7da31fc781c585f700675f344a03d7ccccdf448a31


Amazing !!
member
Activity: 249
Merit: 83
So many numbers and so little time
Congratulations to our whale miner with 1.5EH for solving the 289th solo block solved at solo.ckpool.org !

Code:
[2024-05-30 03:08:08.005] Possible block solve diff 118808888859878.171875 !
[2024-05-30 03:08:08.116] BLOCK ACCEPTED!
[2024-05-30 03:08:08.122] Solved and confirmed block 845735 by 3Kbu2CKYAQ5F7FzbvMKDAXWK9AaMiQRjZj.trit05
[2024-05-30 03:08:08.122] User 3Kbu2CKYAQ5F7FzbvMKDAXWK9AaMiQRjZj:{"hashrate1m": "1.42E", "hashrate5m": "1.38E", "hashrate1hr": "1.35E", "hashrate1d": "725P", "hashrate7d": "150P", "shares": 22543766287400, "authorised": 1716946332}
[2024-05-30 03:08:08.122] Worker 3Kbu2CKYAQ5F7FzbvMKDAXWK9AaMiQRjZj.trit05:{"hashrate1m": "134P", "hashrate5m": "131P", "hashrate1hr": "124P", "hashrate1d": "49P", "hashrate7d": "8.71P"}
[2024-05-30 03:08:08.160] Block solved after 128314299876180 shares at 152.1% diff

https://mempool.space/block/000000000000000000025e7da31fc781c585f700675f344a03d7ccccdf448a31

Congratulations again CK and the whale miner.

This is a good run for solo.ckpool
newbie
Activity: 22
Merit: 0
Congratulations to our whale miner with 1.5EH for solving the 289th solo block solved at solo.ckpool.org !

Code:
[2024-05-30 03:08:08.005] Possible block solve diff 118808888859878.171875 !
[2024-05-30 03:08:08.116] BLOCK ACCEPTED!
[2024-05-30 03:08:08.122] Solved and confirmed block 845735 by 3Kbu2CKYAQ5F7FzbvMKDAXWK9AaMiQRjZj.trit05
[2024-05-30 03:08:08.122] User 3Kbu2CKYAQ5F7FzbvMKDAXWK9AaMiQRjZj:{"hashrate1m": "1.42E", "hashrate5m": "1.38E", "hashrate1hr": "1.35E", "hashrate1d": "725P", "hashrate7d": "150P", "shares": 22543766287400, "authorised": 1716946332}
[2024-05-30 03:08:08.122] Worker 3Kbu2CKYAQ5F7FzbvMKDAXWK9AaMiQRjZj.trit05:{"hashrate1m": "134P", "hashrate5m": "131P", "hashrate1hr": "124P", "hashrate1d": "49P", "hashrate7d": "8.71P"}
[2024-05-30 03:08:08.160] Block solved after 128314299876180 shares at 152.1% diff

https://mempool.space/block/000000000000000000025e7da31fc781c585f700675f344a03d7ccccdf448a31

 Wow that was some serious investment to get that block! Big congrats!
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Congratulations to our whale miner with 1.5EH for solving the 289th solo block solved at solo.ckpool.org !

Code:
[2024-05-30 03:08:08.005] Possible block solve diff 118808888859878.171875 !
[2024-05-30 03:08:08.116] BLOCK ACCEPTED!
[2024-05-30 03:08:08.122] Solved and confirmed block 845735 by 3Kbu2CKYAQ5F7FzbvMKDAXWK9AaMiQRjZj.trit05
[2024-05-30 03:08:08.122] User 3Kbu2CKYAQ5F7FzbvMKDAXWK9AaMiQRjZj:{"hashrate1m": "1.42E", "hashrate5m": "1.38E", "hashrate1hr": "1.35E", "hashrate1d": "725P", "hashrate7d": "150P", "shares": 22543766287400, "authorised": 1716946332}
[2024-05-30 03:08:08.122] Worker 3Kbu2CKYAQ5F7FzbvMKDAXWK9AaMiQRjZj.trit05:{"hashrate1m": "134P", "hashrate5m": "131P", "hashrate1hr": "124P", "hashrate1d": "49P", "hashrate7d": "8.71P"}
[2024-05-30 03:08:08.160] Block solved after 128314299876180 shares at 152.1% diff

https://mempool.space/block/000000000000000000025e7da31fc781c585f700675f344a03d7ccccdf448a31
Pages:
Jump to: