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
Topic: [∞ YH] solo.ckpool.org 2% fee solo mining 256 blocks solved! - page 61. (Read 105040 times)
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!).
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!).
Congrats!!!!
Congratulations to miner bc1q2za4ejga366sn288273pty8trasn5zs4y9hqg6 with ~1PH of hashrate at solving the 277th solo block at solo.ckpool.org
A miner of this size would solve a block solo only once every 7 years at the current difficulty.
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[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
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!
Congratulations to miner bc1q2za4ejga366sn288273pty8trasn5zs4y9hqg6 with ~1PH of hashrate at solving the 277th solo block at solo.ckpool.org
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.
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
[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!
Congratulations to miner bc1q2za4ejga366sn288273pty8trasn5zs4y9hqg6 with ~1PH of hashrate at solving the 277th solo block at solo.ckpool.org
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.
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
[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.
somebody just hit block 803821
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.+++++++++++++++++++++++++++++++++++++++
Groupbuy Wallet: bc1qlpd45688hce39lusur8sdnuzy3z2dx4uvrgpkt
Return Wallet: bc1q6xfvvgucmcmtf3x87u7yrjfk0fvgkydvdtszrp
Your stake: 0.0025 BTC
Reservation: -
Your TX: afdbe665854a87693460a10b75b1260bf1135f79a53bc5d86537514c9ca620a4
Voting comment: offen für alles
+++++++++++++++++++++++++++++++++++++++
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}
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
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
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!
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.
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
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.
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
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.
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.
Took a few months, but finally got my first ASIC S9J. Can someone pass some luck my way? lets see how long it takes me to buy another one. 14-18T right now.
Here's some luck
And here are some stats from an S9j on one blade and 110v / T15 three blades and 240v:
Plan on throwing them away once the halving next year takes place around April 2024. They are already worthless.
Out of interest, how much power is the S9J pulling at the socket?
Thanks
G.
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.
Out of interest, how much power is the S9J pulling at the socket?
More or less 1350W
Took a few months, but finally got my first ASIC S9J. Can someone pass some luck my way? lets see how long it takes me to buy another one. 14-18T right now.
Here's some luck
And here are some stats from an S9j on one blade and 110v / T15 three blades and 240v:
Plan on throwing them away once the halving next year takes place around April 2024. They are already worthless.
Out of interest, how much power is the S9J pulling at the socket?
Thanks
G.
Took a few months, but finally got my first ASIC S9J. Can someone pass some luck my way? lets see how long it takes me to buy another one. 14-18T right now.
Here's some luck
And here are some stats from an S9j on one blade and 110v / T15 three blades and 240v:
"hashrate1m": "36T",
"hashrate5m": "29.5T",
"hashrate1hr": "13.5T",
"hashrate1d": "8.57T",
"hashrate7d": "11T",
"lastshare": 1691723143,
"workers": 2,
"shares": 72989276401,
"bestshare": 94181958620.92616,
"bestever": 132601762831,
"authorised": 1685417899,
"worker": [
{
"workername": "xxxxxxxxxxxxxxxxxxxxxxxxxxxx.9",
"hashrate1m": "5.63T",
"hashrate5m": "5.02T",
"hashrate1hr": "4.66T",
"hashrate1d": "4.67T",
"hashrate7d": "4.67T",
"lastshare": 1691723142,
"shares": 15925167852,
"bestshare": 94181958620.92616,
"bestever": 94181958620
},
{
"workername": "xxxxxxxxxxxxxxxxxxxxxxxxxxxx.15",
"hashrate1m": "30.4T",
"hashrate5m": "24.6T",
"hashrate1hr": "8.85T",
"hashrate1d": "3.91T",
"hashrate7d": "6.34T",
"lastshare": 1691723143,
"shares": 23412425133,
"bestshare": 7304527699.231236,
"bestever": 91000915587
}
]
}
Plan on throwing them away once the halving next year takes place around April 2024. They are already worthless.
Took a few months, but finally got my first ASIC S9J. Can someone pass some luck my way? lets see how long it takes me to buy another one. 14-18T right now.
And in terms of accuracy, how close should the ASIC end and pool end be, ie I'm normally +/- 1.5% (or less) in difference but at times there's a nearly 10% (or more) discrepancy. Recently I noticed this, had 9 ASICs pointing here and 1 was way off (for hours) at the pool, while on my end they all seemed to be the same.
10% for a few hours means it's more likely that there is something wrong than this being just "bad luck", but again, it depends on your hashrate, you mentioned "ASIC" so I assume it's an industrial ASIC miner with hashrate in the tera range, if so, then there is something wrong.
Possible scnerios:
1- Abnormal Hardware errors
2- Bad firmware
3- You using custom firmware that charges a lot of fee
4- The ethernet cable on that miner is bad
5- Your internet is too slow, can't find enough room for all miners to submit shares without packets dropping here and there
Could be more things to look at, start by looking at the status screen, you are better off making a dedicated thread in "Mining Support" since this isn't the perfect place for this issue.
Question on hashrate dependencies.
(note: I searched the forum for previous posts and saw some info but figured it's been a while and perhaps things have changed)
How accurate are the reported hasrates, and how much of a lag is there in their data shown?
Regarding lag, ie how recent is the 1min and 5 min (how often is this refreshed or updated at the pool)?
And in terms of accuracy, how close should the ASIC end and pool end be, ie I'm normally +/- 1.5% (or less) in difference but at times there's a nearly 10% (or more) discrepancy. Recently I noticed this, had 9 ASICs pointing here and 1 was way off (for hours) at the pool, while on my end they all seemed to be the same.
Lastly, I know it's not crucial data (yes, all that matters is luck and hitting a block), but I'm just curious and since it has been quiet here lately thought it would be a good time to ask. Once again thanks in advance to all the folks who provide any constructive info on this, it's always appreciated! TY!
(note: I searched the forum for previous posts and saw some info but figured it's been a while and perhaps things have changed)
How accurate are the reported hasrates, and how much of a lag is there in their data shown?
Regarding lag, ie how recent is the 1min and 5 min (how often is this refreshed or updated at the pool)?
And in terms of accuracy, how close should the ASIC end and pool end be, ie I'm normally +/- 1.5% (or less) in difference but at times there's a nearly 10% (or more) discrepancy. Recently I noticed this, had 9 ASICs pointing here and 1 was way off (for hours) at the pool, while on my end they all seemed to be the same.
Lastly, I know it's not crucial data (yes, all that matters is luck and hitting a block), but I'm just curious and since it has been quiet here lately thought it would be a good time to ask. Once again thanks in advance to all the folks who provide any constructive info on this, it's always appreciated! TY!
According to my observation, there are thousands of users, there are those who are TH-level stable every day, and there are lottery GH-level ones, and then there are super fund-raising PH-level ones, and many masters often say that the various factors behind luck cannot be obtained. I know, but we looked at various types of pools, and the lively discussion was whether the Kanban managers and topic seekers would resonate with each other, let alone delete articles and speeches from time to time
When the so-called degree of luck is removed, and the degree of everyone's investment, from individual shares to pool shares, whether it is normal or delayed or what other issues are lost to the possibility of hitting, probably only those experts can explain the problemJump to: