In our case, attacker simply targeted stratum IPs. There is no such service as CloudFlare for stratum and no ISP/provider can do null route of UDP therefore you cannot really fight 300gbps UDP flood.
It is not so hard to protect web server. You can move mail server to another server/IP.
So, how come someone protect his mail server ? I never heard Gmail to be down due to DDOS. There must be some way to hide the Mail Server IP as well... Mail server is not so critical to protect. In worst case scenario, sending/receiving of mails will not work, which is not equal as crippling entire service. For attacker is usually not worth to attack only your mail server, because with such attack he doesn't gain much leverage. |
|
|
|
|
In our case, attacker simply targeted stratum IPs. There is no such service as CloudFlare for stratum and no ISP/provider can do null route of UDP therefore you cannot really fight 300gbps UDP flood.
It is not so hard to protect web server. You can move mail server to another server/IP.
|
|
|
|
Script kiddies do not know how to code, they only know how to use existing tools to create attacks. If they knew how to code, they would earn money with coding, not extortions. |
|
|
|
I've been mining with Nicehash for a while now using Eligius. Eligius don't give miners the option to set difficulty but this has never been a problem until now. Suddenly my orders have all crapped out because it says the difficulty is 127.9980. 0.002 short of the minimum. Why is this? Something sounds a bit fishy? Is there an issues between Eligius & Nicehash???
We were forced to up minimum diff for SHA256 due to bad/slow controllers on modern fast ASICs that are not capable of working with low diffs. Because there is not much difference between 128 and 127, we have changed min diff to 127 now. |
|
|
|
If I had to guess I would say it's westhash. I can't say for sure but I've also been having trouble with rejects lately but intermittently, especially on one machine. I'm not too far below you. You can view what kind of rejects you have. If it is stale share, then it is probably network problem - higher latencies. If it is any other type of rejected shares - then check your miners/software as something is must be wrong on your side. |
|
|
|
|
You can fight this attacker by null routing UDP traffic. Since stratum servers don't need any other traffic but TCP, this is nice solution. If anyone knows a company, ISP or whoever who can set BGP null route rule, let me know.
|
|
|
|
I feel that I've totally been stolen from. When I place my bitcoin here and try to mine, I usually pass my hash limit by at least 2x - 3x! You guys need to fix your limit stuff! I usually try to leave my orders on for at least 24 hours at a time, but I ALWAYS have to log back in to check to make sure you guys aren't adding more hash to my order to make it disappear faster! Fix your system and my money needs to come back!
Our speed limitation is only approximate and it can never be exact. The reason for that is simple - we are not fortune tellers, we cannot tell what speeds will rigs that we assign to your order eventually have. When you create the order, you are clearly notified about this. Also, you do not pay anything more. If you pay more, you get more speed, too. At the end, your coins are not stolen. |
|
|
|
Nicehash payout has been less than the normal bitcoin mining lately.
If you do 30 days average compared to any mining pool Nicehash generate more. Simply put 2 similar miners for 30 days one to any pool you wish and the other one in Nicehash and check the result. 4 of every 5 times Nicehash Regards Juan Hello Juan, I wanna believe you and for a time I really thought Nicehash paid out better. Last couple of weeks showed me that wasn't the case, at least any more. I'm mining at f2pool for now. You have to constantly fiddle with the "p=xxx" and it's not worth the hassle anymore; can't they arrange it so the sellers don't have to fiddle with it? Why would any buyer pay more for mining than buying a bitcoin directly? You need to fiddle with p only once per two weeks, because that is when bitcoin profitability change. As for %p, it is on todo list, but it does not have so heavy weight, there are more important things to be done first. |
|
|
|
Nicehash down for maintenance at a stupid time YET AGAIN!!! Decent site slowly turning to crap!
All of our stratum servers are under heavy DDOS attack. Working on mitigation, please be patient. |
|
|
|
hey , please could you stop thoses fuckings bots order with 0.02 btc and no limits to hash who always appear to up the price of rent ...
its horrible , i can't leave pc 5 min without this happen ...
i talk about nicehash.com / scrypt ...
You have 2 solutions: 1. Place fixed order and you will not have to worry about any bots any more. 2. Use bot on your own: https://github.com/nicehash/NiceHashBot and you will be able to leave the PC  |
|
|
|
This should not matter. When pool rolls out new diff, this diff is used with new job - official stratum mining specifications say that: This means that difficulty 2 will be applied to every next job received from the server. If the pool does not respect this stratum rule, you may get lower hashpower. Slush mentioned it here too: https://bitcointalk.org/index.php?topic=557866.msg6078264#msg6078264 |
|
|
|
|
Where are now all the arbitragers? Scrypt price on NiceHash/WestHash is wooping 46% below litecoin price. You can earn a lot by just doing arbitrage between NH and litecoin.
|
|
|
|
Anybody know the minimum payout done by nice/west-hash, i have showing 0.00328230 in "un-paid" btc since this morning and can see there has been payouts through the day already but my btc was not paid out to my btc address? Checked the FAQ but could not see anything on minimum payouts, thanks.
https://www.nicehash.com/index.jsp?p=faq#faqs5 |
|
|
|
|
Nobody will loose any coins. We have mailed private keys of old deposit addresses. If you sent to old address, just use that private key to recover the coins. If you didn't get private key, contact our support and we will mail you the key again.
|
|
|
|
|
It is called bad luck. Miners have to be "lucky" to find shares. And higher the diff, the more luck is needed. I think someone good with statistics can actually calculate you the odds to have 20% difference.
If you want to avoid this bad luck, and get exact expected shares - set diff to 128. That is the lowest miner diff we support for SHA256. But also keep in mind that this will NOT increase your chance to find bitcoin block.
|
|
|
|
|
Ah yes, you would get exact amount of shares only if you used low diff shares. Check this thread (I don't know which page, was long time ago) - we already had debate about this.
Keep in mind that our pool on the miners side allows miners to have diffs lower than what pool provides - they get paid for these shares but are not submitted to pool if being under pool diff.
|
|
|
|
Problem with submitted shares not matching what i paid for. I verified the orders i submitted yesterday and today for the amount of shares actually submitted to the pool and they are at least 20% off. Which means i am paying 20% more for the hashrate i hired. Has anyone else had similar problems? Here follows my calculations: | Order | Price BTC/TH/Day | Total BTC | Unspent BTC | Limited TH/s | Expected Shares | Actual Shares (on pool) | | Nicehash | | #252158 | 0.0103 | 0.205702 | 0 | 100 | 401749338.9 | | #250693 | 0.0104 | 0.156702 | 0 | 250 | 303106382.5 | | Total nicehash | | | | | 704855721.4 | 560946737 | | WestHash | | #250694 | 0.0104 | 0.303702 | 0 | 250 | 587446328.5 | | #252159 | 0.0103 | 0.156702 | 0.05561814 | 100 | 197423330.5 | | Total Westhash | | | | | 784869659 | 668995673 |
Has anyone any idea what happened? Can i get my missing shares refunded? Thanks, girino. Let me know: 1. which coin you mined? was there a lot of job switching? 2. what diff did your pool set for NH and WH connections? |
|
|
|
|
I can confirm that bitcoinqt or bitcoind is not something you may want to use in any larger project. After it has several thousands addresses and running for few months, this official client slows down to the point when it takes few minutes to process every block. In the mean time, it blocks all RPC calls, including ones that wouldn't have to be blocked (such as getdiff or get new address). This slowing down has nothing to do with its internal accounting system (that one works fine, but due to long time blocked RPC calls, it is much less useful than your own accounting system). Why official client slows down so considerably - doing 2 threaded processing for several minutes when new block arrives - that is something devs can explain and maybe even fix in future versions. It is a shame, I would personally trust this client the most, but due to these slow downs, it is useless for us and we will be soon switching over to BitGo.
|
|
|
|
Buyers of hashing power at NiceHash/WestHash are not only mining Bitcoin, they are also (sometimes) mining various other coins. Some of them are still at very low difficulty, switching jobs very fast, etc. Unfortunately manufacturers of ASIC miners are putting very weak controllers in their miners (saving a few $ in a machine, worth hundreds even thousands of $  ) with non-optimized software and are thus unable to process large number of shares/jobs/work-restarts. A typical example was KnC Titan (not SHA256, but an Scrypt miner) which was only able to mine Litecoins until the controller software was properly optimized. Recent example of a SHA256 miner that is having a few issues with rejects is AntMiner S5, hopefully Bitmain will improve it soon. If manufacturers would put a multi-core Raspberry Pie 2 in their miners (with a good controller software - I'm not talking only about cgminer/bfgminer, but also drivers, etc. handling of low difficulty coins, switching jobs very fast, proper handling of flushwork, etc.) there would be no issues. For example, there are no issues with sgminer mining any GPU based coin, running on PC (which always has a decent CPU). Probably there is also room for improvement in cgminer itself for these issues. Scrypt miners have nothing to do with this, and I object to you blaming cgminer or the hardware for these issues. 3 second restarts will cause a loss of 10-15% of hashrate no matter how powerful the controller. You are mining shitcoins and miners are losing income as a result, thinking the bonuses will make up for it somehow. Being aware of the issues and planning to tackle them is good but please choose your scapegoats wisely. ckolivas, we respect you as a cgminer developer and overall contributor to Bitcoin community and we are not looking for any scapegoats here ... we're just trying to run a service where both - owners of the mining devices and those who are seeking for hashing power to rent - can benefit. We'll continue to work with hardware and software providers to make sure that various crypto coins (not all of them are shitcoins) will be mineable by various mining devices. Your wording was clearly choosing a scapegoat ... since you claimed the hardware and miner were at fault but provided no details of why the hardware or the miner were at fault. Mining just BTC works fine. As soon as you add merged mining that prioritises the merged mined coin above the BTC mining, to either make "extra profit" for you, or "extra payout" for your clients, of those merge mined coins, the result is loss of shares on BTC. 3 second restarts means that the merged mined coins are getting priority over the BTC restarts and miners are losing BTC. Sounds like a REALLY bad idea to me ... That is why we reward miners for often job switches. On some orders, that purely perform constant job switching, miners are rewarded very good. Example:  This miner was getting paid more than what kind of speed it has. Of course, we are trying to set these rewards to be equal to full miners speed, but this is long process and a lot of testing will have to be done before we find optimal formula. Currently miners are paid a bit more than what they should be in events of massive job switching. No matter if your miner gets rapped by massive amounts of new jobs, our system will reward it with extra virtual shares. |
|
|
|
@Nicehash What is up with the ridiculous difficulty today. It just started today my miners are still running but I am getting stuff like this.
Worker4 0.0003 0.0000 (0.00%) 131072.0000 1159
Worker5 1902.5628 0.0000 (0.00%) 32768.0000
Worker2 482.6852 0.0000 (0.00%) 8192.0000 848
This is on Westhash.
Thanks in advance
That is fixed now. Extra rewards that we are giving to miners when job switch happens were counted as shares. If many such extra rewards are given, then vardiff kicked in. Now these extra reward do not increase share counter and vardiff should work normally. I placed an order a while ago now and it is not showing up in "my orders". Order #251863. How long until it shows up. I may need to edit it.
Thanks.
It is on main NiceHash SHA256 page. You cannot see it? |
|
|
|
|
Show Posts
