[∞ YH] solo.ckpool.org 2% fee solo mining 282 blocks solved!

[VashTSX]

My S9J is pulling around 500 watts in its current configuration since the other two blades failed a long time ago probably due to running on 110v. It did three blades for about a year before two of them wiped themselves out. Restoration on them failed. So many of the ASIC chips burned up and there were OL everywhere.
Currently it is venting to the attic and then to atmosphere; intake has a used K&N car filter cone on it and is quietly churning at 4.8 TH in the closet at a steady 88C.

Thanks for the info, I was considering getting an S9 series miner but on the looks of power consumption alone its just not worth it.

I might try and get an S17 pro instead and run that on 1 card, that should give about 14-16T at around 600Watts

Thanks

G.

I agree with your assessment completely! Sell the cards you don't use before all this equipment becomes less than worthless lol 

Talk about timing. S9 PSU died this morning 
Breaking it apart in a few minutes

[1714605262]

1714605262

[1714605262]

1714605262

[blockhilltop]

Willie, has the latest blockparty come and gone already? Or on you still on holiday, if so when do you think we can run it? TY!

[willi9974]

Hi all,

I'm back from holiday and hope the summer hole closes slowly.
As far as I have not forgotten anything, the post should be up to date (I could not leave it on vacation)

So some places free and we wait with the start Blockparty Run 45 still until a few more come.

Many greetings
Willi

[willi9974]

Coins sind auf dem Weg....

+++++++++++++++++++++++++++++++++++++++
Groupbuy Wallet: bc1qlpd45688hce39lusur8sdnuzy3z2dx4uvrgpkt
Return Wallet: bc1q6xfvvgucmcmtf3x87u7yrjfk0fvgkydvdtszrp
Your stake: 0.0025 BTC
Reservation: -
Your TX: afdbe665854a87693460a10b75b1260bf1135f79a53bc5d86537514c9ca620a4
Voting comment: offen für alles
+++++++++++++++++++++++++++++++++++++++

I have added you, coins have arrived.
Currently we have 0.0875 BTC in the wallet with 12 participants.
Are still about 2-3 places free then we can start the block party 45....

Fingers crossed that it will start soon.

Solo pool is just at a Luck / Diff of 126%, so is purely statistically overdue.
https://solo.ckpool.org/pool/

{"runtime": 5894720, "lastupdate": 1692338297, "Users": 4161, "Workers": 6492, "Idle": 4114, "Disconnected": 1368}
{"hashrate1m": "96P", "hashrate5m": "96P", "hashrate15m": "93.7P", "hashrate1hr": "84.1P", "hashrate6hr": "53.5P", "hashrate1d": "44.3P", "hashrate7d": "54.1P"}
{"diff": 126.0, "accepted": 65995153836809, "rejected": 245215372131, "bestshare": 49342333232336, "SPS1m": 490.0, "SPS5m": 488.0, "SPS15m": 487.0, "SPS1h": 485.0}

[blockhilltop]

somebody just hit block 803821

[-ck]

Congratulations to miner bc1q2za4ejga366sn288273pty8trasn5zs4y9hqg6 with ~1PH of hashrate at solving the 277th solo block at solo.ckpool.org

Code:

[2023-08-18 23:35:26.985] Possible block solve diff 166457402539689.843750 !
[2023-08-18 23:35:27.053] BLOCK ACCEPTED!
[2023-08-18 23:35:27.056] Solved and confirmed block 803821 by bc1q2za4ejga366sn288273pty8trasn5zs4y9hqg6
[2023-08-18 23:35:27.056] User bc1q2za4ejga366sn288273pty8trasn5zs4y9hqg6:{"hashrate1m": "1.05P", "hashrate5m": "1.04P", "hashrate1hr": "1.01P", "hashrate1d": "1.01P", "hashrate7d": "1.01P", "shares": 1944392199944, "authorised": 1685417900}
[2023-08-18 23:35:27.056] Worker bc1q2za4ejga366sn288273pty8trasn5zs4y9hqg6:{"hashrate1m": "1.05P", "hashrate5m": "1.04P", "hashrate1hr": "1.01P", "hashrate1d": "1.01P", "hashrate7d": "1.01P"}
[2023-08-18 23:35:27.062] Block solved after 66873411563189 shares at 127.6% diff

https://explorer.btc.com/btc/block/803821

A miner of this size would solve a block solo only once every 7 years at the current difficulty.

[philipma1957]

Congratulations to miner bc1q2za4ejga366sn288273pty8trasn5zs4y9hqg6 with ~1PH of hashrate at solving the 277th solo block at solo.ckpool.org

Code:

[2023-08-18 23:35:26.985] Possible block solve diff 166457402539689.843750 !
[2023-08-18 23:35:27.053] BLOCK ACCEPTED!
[2023-08-18 23:35:27.056] Solved and confirmed block 803821 by bc1q2za4ejga366sn288273pty8trasn5zs4y9hqg6
[2023-08-18 23:35:27.056] User bc1q2za4ejga366sn288273pty8trasn5zs4y9hqg6:{"hashrate1m": "1.05P", "hashrate5m": "1.04P", "hashrate1hr": "1.01P", "hashrate1d": "1.01P", "hashrate7d": "1.01P", "shares": 1944392199944, "authorised": 1685417900}
[2023-08-18 23:35:27.056] Worker bc1q2za4ejga366sn288273pty8trasn5zs4y9hqg6:{"hashrate1m": "1.05P", "hashrate5m": "1.04P", "hashrate1hr": "1.01P", "hashrate1d": "1.01P", "hashrate7d": "1.01P"}
[2023-08-18 23:35:27.062] Block solved after 66873411563189 shares at 127.6% diff

https://explorer.btc.com/btc/block/803821

A miner of this size would solve a block solo only once every 7 years at the current difficulty.

Nice
166,457,402,539,689.843750


a lot of room to spare!

[o_solo_miner]

Congratulations to miner bc1q2za4ejga366sn288273pty8trasn5zs4y9hqg6 with ~1PH of hashrate at solving the 277th solo block at solo.ckpool.org

Code:

[2023-08-18 23:35:26.985] Possible block solve diff 166457402539689.843750 !
[2023-08-18 23:35:27.053] BLOCK ACCEPTED!
[2023-08-18 23:35:27.056] Solved and confirmed block 803821 by bc1q2za4ejga366sn288273pty8trasn5zs4y9hqg6
[2023-08-18 23:35:27.056] User bc1q2za4ejga366sn288273pty8trasn5zs4y9hqg6:{"hashrate1m": "1.05P", "hashrate5m": "1.04P", "hashrate1hr": "1.01P", "hashrate1d": "1.01P", "hashrate7d": "1.01P", "shares": 1944392199944, "authorised": 1685417900}
[2023-08-18 23:35:27.056] Worker bc1q2za4ejga366sn288273pty8trasn5zs4y9hqg6:{"hashrate1m": "1.05P", "hashrate5m": "1.04P", "hashrate1hr": "1.01P", "hashrate1d": "1.01P", "hashrate7d": "1.01P"}
[2023-08-18 23:35:27.062] Block solved after 66873411563189 shares at 127.6% diff

https://explorer.btc.com/btc/block/803821
A miner of this size would solve a block solo only once every 7 years at the current difficulty.

Congratulations to miner bc1q2za4ejga366sn288273pty8trasn5zs4y9hqg6 even more!

[madmartyk]

Congrats!!!!

[blockhilltop]

Big congrats to the miner! Atta boy!

Did it with only 1PH and less than 2T shares submitted [1,944,392,199,944]..

Here's to hoping the next BlockParty can provide a back-to-back soon (yes, unlikely but nothing sweeter than a repeater boys!).

[willi9974]

Yes we hope that also and just for the info.

For our last block in the Blockparty Run we start 38 runs and submitted 486.455.389.518.928 shares to get a block by a diff from 43.551.722.213.591.
And we had a best share with high from 100.571.298.452.432

so the actual unknown block finder is very lucky with only 1.944.392.199.944 submitted shares and a best share from 166.457.402.539.689

Fingers crosst for our running longtime runs and the upcoming block partys

Best regards,
Willi

[Dark Akuma]

How long was that miner mining for that just found the block of Bitcoin?

[g5120u]

At least few seniors who can continue to submit 1.944.392.199.944 shares in the same account have achieved it,
 and they are still working hard at 12 digits
 

[Gholly]

CK if you will, I have a few questions about how the pool works.

-As I understand on CKpool each miner is mining their own version of the current block. Because the Coin base transaction is preloaded with each miners wallet address and the pool wallet with its %fee it has to be differant. The rest of the transactions are the same in all the other miners blocks ... this makes the block we work on uniquely different from everybody else's work block ... correct?

Does the pool restart the nonce/extra-nonce/version bits/miner signature variables to zero every time the network/(pool?) moves on to the next block to solve every 10 minutes? or does the basic nonce variables continue basically where they let off from the last block?

-How much of this nonce related churn is handled by the pool and what is actually handed to the miner (asic) to do? I believe most ASICs still use your CGminer as at least the basis of their internal software. I have combed through bitcoin documents  online and reviewed some of the your pool source code (beyond me at this point, its been 40 years since i programmed much in C),but so much of the interaction between the pool and the miner isn't well described online or I just can't understand it... I was hoping for someone of great knowledge such as yourself to enlighten me a bit.

If you can give me a very basic pool to miner flow narrative/explanation, I would very much appreciate it.
Thank you

[philipma1957]

your miner is spinning a code created wheel of fortune.

you are making an effort to spin higher than 50trillion and change faster than all miners pointed to all pools for the BTC block chain.

Ck pool acts like a sorting device for a spin higher than 50 trillion plus

if you do it submits it and you get a block.

[Gholly]

philipma1957,
Was that intended as a response to my question for CK?

I understand pools and ASICs and have been mining for years solo and on pools .... I was asking detailed questions about this specific pool software and how it treats the Nonce/ExtraNonce and related variable fields in the header, per user, from block to block and what it sends to the miner itself.
I was hoping for a little input from the master himself seeing that he wrote the pool software and the base software that runs in most of the miners today.

Thanks away

 

[-ck]

1 correct
2 nonce happens so quickly the entire range is always done by hardware. Extranonce is set by pool and also incremented by hardware, reset with every work update
3 all the churn handled by miner

None of this makes any difference to probability.

[Gholly]

-CK
Thank You for the answer,
I understand it makes no real difference, Just had the thought and wondered if everything started from the beginning every time(new block)... it was just a thought.

[citb0in]

@Gholly: all miners work on their own block, they have unique tasks. Even if a block has been solved and confirmed on the network, individual miners continue to work on the constantly updating tasks. The miner fetches the transactions from the pool and thus fills the work pool locally on the miner. The complete nonce range is completely run through in fractions of a second at the ASIC speeds available today. That is why the extra nonces exist, so that the miner can be supplied with work without gaps.

[Gholly]

"he miner fetches the transactions from the pool and thus fills the work pool locally on the miner.",..?

I thought the pool created the current block header  using transactions from the MemPool, not the miner... I thought the miner only spun through the hashing for the current unique black header/nonce/extra nonce range given to them by the pool ?