Welcome aboard to the new miners. All your hashes are welcome and help  Thanks. I'll probably ask a bunch of dumb questions. I'm an infrastructure guy so though more technology savvy than your average soccer mom, I'm out of my depth here.
Dumb question #1-- If I stop my miner to make tweaks (I haven't seen anything anywhere that would indicate I could tweak anything in real time?) do I just start it back with the exact same command? E.g., ./cgminer -o stratum+tcp://pool.ckpool.org:3333 -u blahblahblahblahblahblah.0 -p x --suggest-diff 32 and it will pick up where I left off (minus some herp degradation due to missed hashes)? It's not going to reset me effectively to zero, correct? Same basic question if I were to add more ASICs? I stop it, add a couple ASICs, and re-start there isn't anything special that needs to be done is there?
Second dumb question-- If I bring another miner online is it just append .1 instead of .0 to my wallet address?
There is no such thing as "progress" in mining, it's just accumulated credit so if you stop working for a while, you're just not adding credit to your existing credit while your miner is off. You can pause, stop restart at any time but obviously you only accumulate credit while your miner is working. |
|
|
|
The documentation for the proxy says: Note that the upstream pool needs to be a ckpool for it to scale to large hashrates
Is there any guidance for what is "large" in the hashrate? Would 50 TH/s, for example, be large? This is no longer the case. Any pool can be used upstream. |
|
|
|
if only it was that simple, but I don't think vm will let me use my own router. as I say, my routers mac address is registered to their system, but I can ask them. if I put the router into modem mode, ie its only using one eth port and use my own connected to the router, do you think that would help or will the vm routers socket connection issue still persist?
thank you for your help!!
That may well help provided you can use a separate router for everything such as wifi and the dhcp server as well. It's hard to know what part is responsible but it's often the act of maintaining tcp sockets that's responsible. Note that most modern routers allow you to clone a MAC address and use that so if it's just the MAC address of the existing router that is registered to the system you should be able to mimic that. |
|
|
|
|
Some routers are terrible and mining requires persistent socket connections to work. There is a small chance that even though you have loads of capacity, your router is not capable of reliably holding persistent connections, especially if it's the standard cheap crap that your ISP gave you with your plan. Investing in a decent router is worth it on multiple level anyway.
|
|
|
|
If i hit one block i have to finish him? Because i won' t mine 24 hours a day. There is no start or finish or accumulating shares on solo. Mine whenever you want to mine here. |
|
|
|
[2017-10-14 07:06:31.030] Possible block solve diff 3313873686180.219238 !
[2017-10-14 07:06:31.145] BLOCK ACCEPTED!
[2017-10-14 07:06:31.305] Solved and confirmed block 489739 by 17CopX7BYruEPZrGhSikiFn5iGWU3X4CGJ.44047
[2017-10-14 07:06:31.305] User 17CopX7BYruEPZrGhSikiFn5iGWU3X4CGJ:{"hashrate1m": "1.2P", "hashrate5m": "1.19P", "hashrate1hr": "1.12P", "hashrate1d": "1.04P", "hashrate7d": "675T"}
[2017-10-14 07:06:31.305] Worker 17CopX7BYruEPZrGhSikiFn5iGWU3X4CGJ.44047:{"hashrate1m": "95.5T", "hashrate5m": "96T", "hashrate1hr": "91.6T", "hashrate1d": "36.4T", "hashrate7d": "26.8T"}
[2017-10-14 07:06:31.305] Block solved at 135% diff Checked the stats for that address, doesn't seem to show the bestever diff as 3313873686180.219238. That's right it was found on the DE node which unfortunately wasn't communicating with the main pool at the time. I'm sure he cares more about his reward than his bestever stat  |
|
|
|
There's a communication issue between DE and the main pool. I need to restart DE to correct it. Sorry about that (the hashrate was happening just not being recorded as you can see since DE still managed to find a block).
Okay should be sorted now. I had to take DE offline for a bit there sorry about the inconvenience. |
|
|
|
Is there still something wrong with the status page? My page shows no workers and no hash rate at the moment?
but the miners all say alive and are submitting shares.
Stopped working late last night after the issues.
There's a communication issue between DE and the main pool. I need to restart DE to correct it. Sorry about that (the hashrate was happening just not being recorded as you can see since DE still managed to find a block). |
|
|
|
[2017-10-14 07:06:31.030] Possible block solve diff 3313873686180.219238 !
[2017-10-14 07:06:31.145] BLOCK ACCEPTED!
[2017-10-14 07:06:31.305] Solved and confirmed block 489739 by 17CopX7BYruEPZrGhSikiFn5iGWU3X4CGJ.44047
[2017-10-14 07:06:31.305] User 17CopX7BYruEPZrGhSikiFn5iGWU3X4CGJ:{"hashrate1m": "1.2P", "hashrate5m": "1.19P", "hashrate1hr": "1.12P", "hashrate1d": "1.04P", "hashrate7d": "675T"}
[2017-10-14 07:06:31.305] Worker 17CopX7BYruEPZrGhSikiFn5iGWU3X4CGJ.44047:{"hashrate1m": "95.5T", "hashrate5m": "96T", "hashrate1hr": "91.6T", "hashrate1d": "36.4T", "hashrate7d": "26.8T"}
[2017-10-14 07:06:31.305] Block solved at 135% diff |
|
|
|
Some kind of network flood at the pool again. Not sure if it's a DDoS or what. Investigating.
DDoS in the datacentre and the pool was collateral damage in the DDoS protection it seems. As far as I can tell things are returning to normal now. EDIT: Still an issue so will restart main pool too now. |
|
|
|
Does ckpool work as a generic stratum proxy when run in proxy mode (-p) or is this Bitcoin specific? Documentation goes to great pains to say it's bitcoin only. |
|
|
|
... This isn't straight forward but you asked so I'll try to simplify it as much as possible.
13 TH is about 180,000 diff 1 shares per minute which is about 260 million shares per day. The current N shares is 2.2 trillion shares. If you look at the current pool work, the top miner is actually about 3,000 times bigger than the 100th miner so you need only 1/3000th of the 2.2 trillion shares. That's about 750 million. So with 1 S9 you should get into the payouts in about 3 days - but then the payout will keep rising too. This would be very different if every miner was the same size. I did this over morning coffee so I may be out but that sounds about right.
This is EXACTLY the kind of answer I was looking for, thank you very very much! I just came online with an s9 a few days ago and it did not even take 48 hours to get into the payout pool at roughly that hash rate. Javede Payout pool yes, but he was asking about top 100 specifically. |
|
|
|
... Anyone in the top 100 hashers will always get into the payout queue once they've mined enough shares (and enough keeps changing.) If you look at http://ckpool.org/pool/ you'll see the current "lns" - Last N Shares is 2241427919578 and the HERP is about the same so it's your proportion of this amount specifically. To help me visualize this better: could you answer my original question ( how long should one mine at 13TH to get into the top 100 ) assuming (impossibly) that both difficulty and the amount of pool participants stays the same from here on out As I said it's constantly changing at the moment with the pool N shares still rising so it will change continuously till we reach steady state even if everything else stays the same. This isn't straight forward but you asked so I'll try to simplify it as much as possible. 13 TH is about 180,000 diff 1 shares per minute which is about 260 million shares per day. The current N shares is 2.2 trillion shares. If you look at the current pool work, the top miner is actually about 3,000 times bigger than the 100th miner so you need only 1/3000th of the 2.2 trillion shares. That's about 750 million. So with 1 S9 you should get into the top 100 payouts in about 3 days - but then the payout will keep rising too. This would be very different if every miner was the same size. I did this over morning coffee so I may be out but that sounds about right. |
|
|
|
Right on. So meaning is it luck that push me from postpone to payouts or all of the contributed hashrate previously will accumulate until I am push to payouts?
Mostly hashrate and a small contribution by luck. Ok, so I seem to be missing something. I have read the explanation on the first page of this thread, and have a rough idea how the calculation works. However I can't seem to answer the following question: What is the actual formula to approximate when does one get into the 150-member coinbase list, considering the current state of the queue? Let's say I get my hands on an 13TH S9 today, and start mining. At current difficulty/reward I am "gaining" about 0.02 BTC / week. How long should my miner remain plugged to guarantee an actual payout whenever the next block is found? The reason I ask this is because even the lowest entry in the pool ( at the time of writing it is "18XcjTLs1rkwhgYjncUaKmoYwKpXuvGV17": 0.00014845 ) has a luck of 1.0 ( http://ckpool.org/users/18XcjTLs1rkwhgYjncUaKmoYwKpXuvGV17 ). And that's a payout 135 times(!) smaller than what a weekly "statistical-payout" would be for a 13TH miner. Thanks in advance for your time explaining this It's spread out over the last 5 x diff shares (or herp specifically which is approximately equal to the shares over a long time.) The bigger the pool is the faster that time will clock up but for the moment that is a very long time. However unlike traditional PPLNS it ramps up more quickly since it's score based. Additionally this pool has never yet mined 5 x diff shares so it's still rising so it will ramp up faster again meaning it hasn't currently met equilibrium and the true answer is constantly changing at the moment. On the other hand, guaranteeing a payout you just need to be above the threshold which is really quite easy. Anyone in the top 100 hashers will always get into the payout queue once they've mined enough shares (and enough keeps changing.) If you look at http://ckpool.org/pool/ you'll see the current "lns" - Last N Shares is 2241427919578 and the HERP is about the same so it's your proportion of this amount specifically. |
|
|
|
What is the number that follows the addresses that are in the postponed section of the pool work? is that an accumulation of user/address HERP?
Yes it's HERP. |
|
|
|
4.9.2 windows 7 .zip link is broken or just not there.
That's right there are no zip files, only .7z files as the zip files were falsely flagged as viruses by google which kept them off my back for a while. However in the meantime google has falsely flagged almost my entire website due to it containing bitcoin mining software even though it's impossible to do anything malicious with current versions of cgminer since it only works on asic mining hardware. I gave up trying to appeal to google about that. They even flagged web pages that are just text patches which is nonsense. that really sucks  does 4.9.2 support more devices like gekko-2pac? 4.10.0 has support for more devices than 4.9.2, so I'm not sure why you're trying to find an older version but new versions of the official cgminer are rare since almost everyone develops drivers and their own fork outside the core development now. Gekko-2pac has someone working on a cgminer fork with dedicated support https://bitcointalk.org/index.php?topic=1764803.0 |
|
|
|
4.9.2 windows 7 .zip link is broken or just not there.
That's right there are no zip files, only .7z files as the zip files were falsely flagged as viruses by google which kept them off my back for a while. However in the meantime google has falsely flagged almost my entire website due to it containing bitcoin mining software even though it's impossible to do anything malicious with current versions of cgminer since it only works on asic mining hardware. I gave up trying to appeal to google about that. They even flagged web pages that are just text patches which is nonsense. |
|
|
|
Did something happen to DE pool? miners just went to failover ?
Yup same for me. In fact it gave me a scare. Thought my apartment caught on fire and that's why they stopped mining. Had to leave a party early to check things out. There was some instability at the DE pool which has now been corrected, sorry about any inconvenience. I ended up having to restart forgot I left failover to the normal ck pool when I should have had it on the other server. Can you explain to me how to pool selected the diff for each miner. I just restarted all my s3's and they all seem to start up having a wide range of LSDiff how does the pool determine the diff a miner should be at? is it worked out by shares per second/min/hour? ~18 shares per minute. |
|
|
|
Did something happen to DE pool? miners just went to failover ?
Yup same for me. In fact it gave me a scare. Thought my apartment caught on fire and that's why they stopped mining. Had to leave a party early to check things out. There was some instability at the DE pool which has now been corrected, sorry about any inconvenience. |
|
|
|
Right on. So meaning is it luck that push me from postpone to payouts or all of the contributed hashrate previously will accumulate until I am push to payouts?
Mostly hashrate and a small contribution by luck. |
|
|
|
|
Show Posts
