 Show Posts
|
|
Pages: [1] 2 3 4 5 »
|
|
Hey all, are calculations on solochance.com currently accurate? I've noticed a substantial drop in the estimated time to find a block but haven't seen a large drop in total network hashrate to explain the drop. Thoughts?
|
|
|
|
Hi All, I'm trying to wrap my little brain around the math behind a BTC block being generated. I believe I understand the basics. However, my question is related to the nonce. Let's say I have just one miner. When it starts to "guess" the hash for my proposed solution by incrementing the nonce from 0 to n, followed by the extranonce (rehashing each time and comparing to target), the odds of any duplication of work is zero because I have just one miner.
Now let's say I have two miners here at ckpool solo, both pointing to the same BTC address, different worker names. Are extranonce ranges provided by the pool to prevent duplicate "guesses" by each of the two miners? What if I use no worker name instead? Can this then lead to a possible duplication of work in either case? What if I have 10 miners then? Still no chance of work duplication?
It seems that because I want to avoid testing the same block header twice for the solution that awards me 6.25 BTC, it could be advantageous to control the extranonce ranges for each miner I have pointing to the same BTC address here on ckpool solo to prevent any duplication of work. Is this already happening in the backend and I am just not aware of it?
Just trying to get a better understanding...
This is the solo.ckpool thread, please open a new thread in the main mining section. To your question: No, the stratum send to each individual miner a unique number, that is for every seperate connection, your miner does not have to add a worker name on it. Read the stratum docs. https://bitcointalk.org/index.php?topic=557866.0This was a solo pool question. I am mining on the solo pool. Regardless, I suspected the pool handled it with the extranonce values, I'm guessing by applying a different value to each miner to prevent duplication of work but I will check out the link. Thank you for sharing that. |
|
|
|
|
Hi All, I'm trying to wrap my little brain around the math behind a BTC block being generated. I believe I understand the basics. However, my question is related to the nonce. Let's say I have just one miner. When it starts to "guess" the hash for my proposed solution by incrementing the nonce from 0 to n, followed by the extranonce (rehashing each time and comparing to target), the odds of any duplication of work is zero because I have just one miner.
Now let's say I have two miners here at ckpool solo, both pointing to the same BTC address, different worker names. Are extranonce ranges provided by the pool to prevent duplicate "guesses" by each of the two miners? What if I use no worker name instead? Can this then lead to a possible duplication of work in either case? What if I have 10 miners then? Still no chance of work duplication?
It seems that because I want to avoid testing the same block header twice for the solution that awards me 6.25 BTC, it could be advantageous to control the extranonce ranges for each miner I have pointing to the same BTC address here on ckpool solo to prevent any duplication of work. Is this already happening in the backend and I am just not aware of it?
Just trying to get a better understanding...
|
|
|
|
Reserviert für stats, miner und möglichen Blockfund / reserved for stats, miner and a possible block found Interessierte / Interested I would also be interested, if you need another participant.
Depending on number of participants and potential buy in, I am very interested.
Any "high rollers" interested in doing a large rental? I'm thinking of putting in 0.5BTC and looking for 2-3 more players. Anyone interested? Would be willing to use another member as escrow or manager for the buy in. Post or PM if you're interested... SlimmestarAnd do you have any takers yet? Thank you willi. Please put me down for a spot. I will put in up to 0.5BTC, depending on how many participants and the average buy in others agree to. I vote for a lower hash rate for a longer time, perhaps up to 200PH at most. That is just my own opinion though... |
|
|
|
Any "high rollers" interested in doing a large rental? I'm thinking of putting in 0.5BTC and looking for 2-3 more players. Anyone interested? Would be willing to use another member as escrow or manager for the buy in. Post or PM if you're interested... SlimmestarAnd do you have any takers yet? I will check out willis run. I've done a number of the smaller runs with willi but didn't participate in the last megarun. He always runs a very organized group. |
|
|
|
Any "high rollers" interested in doing a large rental? I'm thinking of putting in 0.5BTC and looking for 2-3 more players. Anyone interested? Would be willing to use another member as escrow or manager for the buy in. Post or PM if you're interested... I participated in willi's run mentioned below last year and would be happy to welcome you as a new participant. I think willi has enough reputation here on the board. Maybe we can get some people together for a monster run. Last year we rented 500 PH/s over 24 hours. Was that your plan as well or were you thinking of a lower hashrate with much more run time (several days)? I'm sorry I overlooked your message. I personally was leaning towards a slightly lower hash rate for a longer period. Maybe 100-150PH until the 2-2.5BTC are spent. I have done a number of rentals with Nicehash and find that when I grab too much of the hash rate, it tends to drive the overall rental rate up to keep up that speed. Last I checked, the fixed rentals are no longer available? |
|
|
|
I think 3 or 4 maybe 5 are in.
So if someone interested here also, I make a new topic to talk about that.
@hiaxis, @verexi1513, are you in for a monster / mega run?
Best regards,
Willi
Depending on number of participants and potential buy in, I am very interested. |
|
|
|
|
Any "high rollers" interested in doing a large rental? I'm thinking of putting in 0.5BTC and looking for 2-3 more players. Anyone interested? Would be willing to use another member as escrow or manager for the buy in. Post or PM if you're interested...
|
|
|
|
Looking through the logs I can see one miner submitting mostly rejects - all below target level, suggesting dodgy firmware on his hardware, but I don't see anything else untoward. That might be enough on its own. I suggest each individual user check their own stats and see if their hashrate at the pool reflects their hardware - ckpool reports hashrate based ONLY on accepted shares.
Thank you for the info ck. That's good to know. So if the difficulty is too low on a particular miner, even one with a relatively low hash rate, it's possible to rack up a large amount of rejected shares. That's good to know! |
|
|
|
Question for you all. I was looking at the solo pool stats and noticed the number of rejected shares versus total shares accepted.
"accepted": 24575964250308, "rejected": 8543041616789,
Is it normal to have such a high ratio of rejected to accepted shares? It's almost 35%.
Just curious...
It's not normal, it's likely shitty asic firmware. If the reported hashrate is still fine and consistent with the hardware then just ignore it, it means it's submitting shares below difficulty or something stupid. So there's enough shitty firmware out there running in miners solo mining on this pool to cause over 1/3 of the total shares submitted by the entire solo pool to be rejected? That seems crazy! I could understand if a small portion of the miners connected to the pool had that issue but over 1/3 of our shares submitted are being rejected. Is this due to rentals maybe? I'm not an expert by any stretch in this area which is why I'm trying to understand more about it. It just seems like a very gross inefficiency if 1/3 of our total shares on the solo pool as a whole are being rejected. It's probably one miner, likely a rental related phenomenon. I might investigate. Thank you ck. I'm curious what you find. Looking at it today, rejected total seems to still be ticking up quickly. If our average hash rate since the last block was let's say 15PH, it's concerning if we, as a "pool", had 5PH worth of those shares rejected. Something just doesn't seem right but again, I'm not an expert in this. |
|
|
|
Question for you all. I was looking at the solo pool stats and noticed the number of rejected shares versus total shares accepted.
"accepted": 24575964250308, "rejected": 8543041616789,
Is it normal to have such a high ratio of rejected to accepted shares? It's almost 35%.
Just curious...
It's not normal, it's likely shitty asic firmware. If the reported hashrate is still fine and consistent with the hardware then just ignore it, it means it's submitting shares below difficulty or something stupid. So there's enough shitty firmware out there running in miners solo mining on this pool to cause over 1/3 of the total shares submitted by the entire solo pool to be rejected? That seems crazy! I could understand if a small portion of the miners connected to the pool had that issue but over 1/3 of our shares submitted are being rejected. Is this due to rentals maybe? I'm not an expert by any stretch in this area which is why I'm trying to understand more about it. It just seems like a very gross inefficiency if 1/3 of our total shares on the solo pool as a whole are being rejected. |
|
|
|
|
Question for you all. I was looking at the solo pool stats and noticed the number of rejected shares versus total shares accepted.
"accepted": 24575964250308, "rejected": 8543041616789,
Is it normal to have such a high ratio of rejected to accepted shares? It's almost 35%.
Just curious...
|
|
|
|
Willi, can you please update my reservation for runs 16-20. I'm in for 0.01 per run again. I will send 0.05 today for 16-20 once I see your confirmation. Thank you!
Yes you can, if you post the TX ID i update the list. Here you go. Please update my Return wallet address as well. Thank you willi! +++++++++++++++++++++++++++++++++++++++
Groupbuy Wallet: 3KWE8HcunSfvfNBy3CdXZdQ2HyvierBxeT
Return Wallet: 36X4tuCdoCUksbnYEc5VJMZDdb2rGJ7KP4
Your stake: 0.01 x 5 runs = 0.05 total
Reservation: 5x
Your TX: 5ea331cf56c08242ab78ba3598e548d4af8e284d306620e35efc7b404be05b47
Voting comment: 25PH
+++++++++++++++++++++++++++++++++++++++
|
|
|
|
|
Willi, can you please update my reservation for runs 16-20. I'm in for 0.01 per run again. I will send 0.05 today for 16-20 once I see your confirmation. Thank you!
|
|
|
|
Everyone should see it as a fun game or gambling. Doing any math beyond that's not gonna give us any edge. Each ride is different and past drives or how long we are in doesn't improves our odds to our future runs. The only things we can do to improve our odds is the hashrate. A small diminishing interest will take a U turn the moment we find a block. Scheinbar flacht das Interesse langsam ab, nachdem wir jetzt sehr viele Runden dabei sind und die Chancen immer geringer werden einen Block zu finden. Muss auch ehrlich eingestehen, ich habe mich hier auch schon etwas verzockt und mit dem Blockfund würde ich nur mehr mit einer 0 rauskommen  Why do you feel our luck goes down? The more runs we make, the better our odds. As we submit more and more shares, statistically we get more and more likely to hit a block. It's still luck but our odds are much higher the longer we are in it... Don't lose hope! I do agree nothing is guaranteed but this is the whole reason "luck" is calculated based on number of shares, to determine statistically based on your hashrate how lucky or unlucky you are relative to your hash power. Every form of gambling has odds and smart gamblers will always play and consider the odds and payout relative to the investment. The people that don't do that allow the house to take them for all they have. More or less hashrate doesn't matter unless you increase duration as well. 100P for 1 day or 10P for 10 days or 1P for 100 days, your odds are mathematically the same. Still no guarantee in any of the cases, but odds are odds. When you flip a coin, your odds are 1 in 2 of landing on heads. If you get very lucky, you can land on heads 5 times in a row or get very unlucky and land on tails 5 times in a row but if you flip the coin 10000 times and check the odds again, statistically it will be close to 50:50. Not exactly 50:50, but close to it., The same applies here.... |
|
|
|
Scheinbar flacht das Interesse langsam ab, nachdem wir jetzt sehr viele Runden dabei sind und die Chancen immer geringer werden einen Block zu finden. Muss auch ehrlich eingestehen, ich habe mich hier auch schon etwas verzockt und mit dem Blockfund würde ich nur mehr mit einer 0 rauskommen Why do you feel our luck goes down? The more runs we make, the better our odds. As we submit more and more shares, statistically we get more and more likely to hit a block. It's still luck but our odds are much higher the longer we are in it... Don't lose hope! |
|
|
|
|
Holy $$&+ that is amazing! Seriously, very very happy for you. It just goes to show that anyone in the game has a shot. People may be buying more lottery tickets with more TH to increase their odds but anyone with a ticket can win. Gotta be in it to win it! That is epic!
|
|
|
|
|
What's the cost of rentals doing right now given the massive drop in BTC price? Much change there yet? Hoping we can get more shares for our money...
|
|
|
|
|
Since we began the 2022 runs, we have submitted 5,247,936,069,040 shares in runs 1-8. Since the last block was hit through Willi's group, we have a total of 10,633,894,180,900 shares. Statistically, we are less than half way there but hopefully our luck will turn and we will hit it early!
|
|
|
|
Willi, here is my BTC for runs 11-15. Please update my return wallet address using the template below. Thank you! +++++++++++++++++++++++++++++++++++++++
Groupbuy Wallet: 3KWE8HcunSfvfNBy3CdXZdQ2HyvierBxeT
Return Wallet: 36w2v1z34DEi9gFRPCsUVdzbMUVMi4jHow
Your stake: 0.01
Reservation: 5x
Your TX: 30a433fe97f64179eafd9db5330345a2b4f9dcb403981fb3ad34eb0d9b31776b
Voting comment: group decides
+++++++++++++++++++++++++++++++++++++++
|
|
|
|
|
