I hope this isn't a dumb question...
Going through some of my debug logs, I noticed that the generated stratum header has the version like this:
[2018-02-15 23:08:23.772] Generated stratum header 20000000ed37665c908b8f6b9120d09918afa1ef1c3bd3fa0024d3f700000000000000005fb360c99001606 f4f9aeb9293c5776d6e3e666adf0e6dacdbb9526ae3561fa95a86592f1761e9f800000000000000 8000000000000000000000000000000000000000000000000000000000
Shouldn't it be like this?:
[2018-02-15 23:08:23.772] Generated stratum header 00000020ed37665c908b8f6b9120d09918afa1ef1c3bd3fa0024d3f700000000000000005fb360c99001606 f4f9aeb9293c5776d6e3e666adf0e6dacdbb9526ae3561fa95a86592f1761e9f800000000000000 8000000000000000000000000000000000000000000000000000000000
I didn't see anywhere in the code where the bbversion was reversed. Unless I missed it. I did see some previous posts from way back where the block version is shown in the logs like my second example.
The version gets put in the header_bin as in the first example, not reversed. Raw block headers have the version reversed and when test hashed, produce the correct hashes.
Thanks,
-Ken
Take a look at some blocks to see what version looks like these days, eg: https://btc.com/00000000000000000077140243064000ba35b22d3e2440e936a722b90cd09365Compare with older blocks, eg: https://btc.com/00000000000000001ed61d4b7dd337c8eb1de0f21a0bd310a8733fb35f21991c |
|
|
|
"...provided you keep mining"
So, just to clarify, if I get in the payout queue after finding a block and then stop mining before the next block - Does that mean I'll evenly cycle through and be paid? Or do I have to keep mining to maintain the spot?
My understanding is that you pay out only 150 at a time and the smaller miners that have earned a payout go on a payout list - but when they actually get to the top of that list is just a matter of time... Or does it mean we have to keep mining to hold our place on the list?
If you don't keep mining when you hit the payout list there is a chance, however slight, that we end up having a block that is over 500% diff and then you won't get anything whereas continuing to mine will maintain your spot. |
|
|
|
Thinking of pointing my new miners over here. They aren't very big, though. I am trying to see if it is worth my effort. What is the current dust limit to get on the payout list?
And just to confirm my understanding after reading through these last few pages : if I contribute shares and earn above the payout threshold, as a little guy I go on the list to eventually get paid, even if I stop mining here in the interim?
The current dust limit is the smallest amount you can spend on the bitcoin network. However even if you get above the dust limit it means you will then get into the queue for a payout in one of the subsequent blocks, but you will eventually be paid provided you keep mining. The only caveat is that blocks are so infrequent at our current hashrate it could be a year or more before that happens unless through some miracle our hashrate gets much larger. |
|
|
|
|
My bad sorry, bitmain warranty is now called myrig. BTW I have absolutely no financial stake in the company whatsoever beyond being paid to do cgminer driver cleanups so I have nothing to gain by staking my reputation on them.
|
|
|
|
|
I've been hired by bitmain warrantymyrig, I know the person by name personally who hired me, the scope is extremely flexible just to clean up whatever's involved with the driver, my reputation speaks for itself, the device is definitely real but I couldn't possibly speak for timelines of production and guarantee delivery ffs that has nothing to do with me.
|
|
|
|
I'm now renting 82T for about 72 hours using port 3333. I did see the too low error message for about 30 minutes, but now everything has level out.
The default port should scale to any hashrate. Port 4334 won't go below 1 million and is purely for shit rental services that limit connections to 1M+ |
|
|
|
Just out of curiosity why did the difficulty drop from 190' to low 180's? Also with the group best share it has not changes for weeks. Are we trying to find everything in between? I have heard that best share dose not mean much but just looks like we are stuck.
Bitcoin network difficulty rose to over 3 trillion, therefore our percentage of diff dropped. We simply haven't found a higher share in that time. |
|
|
|
I installed my own bitcoin mining pool using unomp (ubuntu VM) and I now try to run cgminer to test GPU mining on it.
I use CGMiner 3.7.2 and I have a NVIDIA 1050 TI
Unsupported. Only the current version and bitcoin mining with ASICs is supported here. |
|
|
|
..Again, I'm only working remotely on them but they're quite different to anything I've worked with before.
Any idea why they are only releasing such unclear videos, pictures and details about the hardware? Or do you mean something else by the they're quite different to anything you've worked with before? No idea on the hardware side what's going on as I've said previously. What I mean is they're uniquely different in terms of what software support they need to work which makes it clear they're different to any other hardware. So from my perspective, it's pretty clear this is different hardware and not just faked, even if I'm only getting to work on them remotely for now. |
|
|
|
|
I'm now currently working on cleaning up the drivers for these devices. The code is the usual disaster area I've come to expect from in-house drivers but hopefully by the time you see the code it won't be so bad. Again, I'm only working remotely on them but they're quite different to anything I've worked with before.
|
|
|
|
... stolen several accounts. See if any of you are there.
...
Wha dafuq are you on about? What am I talking about? That such people are stopped. And those who are affected by it, remember it early. I noticed that my miner software no longer displayed my BTC address. What you are saying is that you foolishly ran mining hardware from those bitmain fucking morons that turns on open write access to the API for the entire world and someone just logged into it and changed your mining address. This has nothing to do with this pool though. |
|
|
|
I'm getting the following error message for MRR. Is there anything I can do about it?
One or more workers on this rig has been assigned a share/worker difficulty by your pool that is too low. Hashrate performance issues may occur.
The OPTIMAL Difficulty range for this rig is 18,626 - 112k
Please either adjust your worker settings at your pool, or change pools if you are unable to do this at your current pool. Thanks!
It will adjust so shouldn't be a problem. If it's a problem, connect to port 4334 instead. Thanks for your help CK. I changed the port to 4334 and removed the worker extension. The owner of the rig is saying "diff shows 1MEG on the miner. It will never return any hash at that diff. Diff should be about 12k." Doesn't matter. Leave it there and it will adjust down as soon as 3 shares have been submitted. |
|
|
|
I'm getting the following error message for MRR. Is there anything I can do about it?
One or more workers on this rig has been assigned a share/worker difficulty by your pool that is too low. Hashrate performance issues may occur.
The OPTIMAL Difficulty range for this rig is 18,626 - 112k
Please either adjust your worker settings at your pool, or change pools if you are unable to do this at your current pool. Thanks!
It will adjust so shouldn't be a problem. If it's a problem, connect to port 4334 instead. |
|
|
|
Seems like that's already been said 5,000,000,000,000,000,000,000,000,000,000,000,000,000,000 times in this thread.  Here's hoping that number isn't also a prediction for future difficulty. |
|
|
|
My address is under the "payouts" section, no payout: "14KWusF6jjxCaEi1e2fF2pv4AUFybo6RMe": 0.00395418
Right, it means when we find a block, that's how much you will get as a payout. Oh. So after a cycle? Wait for the second one found for a payout to happen? Was chipping away before the last block came. You weren't in the payouts list at the time the block came. Here are the full block details for the last found block: http://ckpool.org/blocks/507708.confirmedYou'll see you're in the postponed list with this much herp: "14KWusF6jjxCaEi1e2fF2pv4AUFybo6RMe": 1084910365.24, You hadn't mined enough prior to that block find. |
|
|
|
My address is under the "payouts" section, no payout: "14KWusF6jjxCaEi1e2fF2pv4AUFybo6RMe": 0.00395418
Right, it means when we find a block, that's how much you will get as a payout. |
|
|
|
Over month since last block find. Hope someone find one soon.
Say I mine to btc address 1 then move to new btc address it not matter about shares on old address? has no bearing on chance?
Makes no difference here. Feel free to change to a different address, even a native segwit address  |
|
|
|
As I have done on the solo pool, I will be restarting this pool within the next hour to bring native segwit address AKA bech32 support.
Restart completed uneventfully. This pool now supports bech32 addresses. These are currently available on only electrum wallet by default, but the next version of bitcoin core due out, 0.16.0, will be able to natively support them. These are native segwit addresses that start with bc1 instead of 1x or 3x (eg bc1qw508d6qejxtdg4y5r3zarvary0c5xw7kv8f3t4), and the advantage of native segwit addresses is they take up less blockchain space making transactions that use them slightly smaller and thereby having a very slight decrease in transaction fee. For more information, see: https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki |
|
|
|
|
Show Posts
