Ask HN: Why did Coinhive, the in-browser crypto miner, fail?
31–40 of 52 posts
Re: Ask HN: Why did Coinhive, the in-browser crypto miner, fail?
#32Re: Ask HN: Why did Coinhive, the in-browser crypto miner, fail?
#33This is a big question for me too! Especially since they didn't seem to have any major reason to burn a lot of cash or to run out of money! Was it maybe a lawsuit, fraud or regulatory issue? I would LOVE to know.
https://coinhive.com/blog/en/discontinuation-of-coinhive (you probably need to whitelist that in your adblocker to read it)
Sounds like "lots of work to do soon and not making all that much money, not worth it". (surely being known as "malware" didn't help either...)
Re: Ask HN: Why did Coinhive, the in-browser crypto miner, fail?
#34A million CPUs would not be as efficient mining Bitcoin as a single ASIC. There are no coins where CPU mining is as good as GPU. JavaScript is also inefficient compared to native programs. Overall, it probably didn't generate very much money. Mining is a commodity. An ad click is worth orders of magnitude more.
So why didn't they use GPU? Could you build something like that for WebGL?
Re: Ask HN: Why did Coinhive, the in-browser crypto miner, fail?
#35Well, for one, AV software started to classify any website with its code as 'infected' with malware. Then adblockers blocked their script, and even today their website doesn't load properly with uBlock activated.
These are definitely important issues but they don't sound like show-stoppers. Many people use anti virus software and adblockers but then again many don't! Additionally they (or some alternative) may have been able to improve the software and create a simple consent process to avoid being blacklisted.
Re: Ask HN: Why did Coinhive, the in-browser crypto miner, fail?
#36Spamming the adblockers to whitelist them (and their authedmine alternative) definitely didn't help https://github.com/easylist/easylist/issues/712
I think a miner like this could provide an interesting way for people to monetize their content, as long as it's opt-in, but blocking a non-ad like this just totally deflates the argument that ad-blockers are about privacy or intrusiveness, and their really about people having their cake and eating it too.
Re: Ask HN: Why did Coinhive, the in-browser crypto miner, fail?
#37You're stuck between running this miner covertly (scummy) or asking for permission (who is going to click yes?).
How much of Coinhive's income comes from users who are unknowingly running the code? It seems like a move towards more user-hostility, not less.
The one time I saw an actual fit for the end user was an online game that would let you turn on the miner to win in-game coins. Who else can pull off an opt-in?
Re: Ask HN: Why did Coinhive, the in-browser crypto miner, fail?
#38IMHO there still is quite an opportunity to find substitutes for ads that provide revenue for websites and aren’t as annoying as ads whether it is mining or something like SETI or something like re-captcha.
Would love to see more in this direction.
Re: Ask HN: Why did Coinhive, the in-browser crypto miner, fail?
#39Earlier quoted context omitted.
I thought Monero was designed to be resistant to ASICs? Please correct me if I'm wrong, I don't have that much knowledge about crypto₹.
There is no such thing as ASIC-proof. You can make an ASIC for any deterministic algorithm. "ASIC-resistance", in this context, only means that ASICs can be held to a low multiple of CPU/GPU efficiency. So ASICs can be 10x as efficient as a CPU/GPU, but not 10k-1m times as efficient like they can on something like SHA. Unfortunately, profit trends towards zero (towards cost of production) until prices change, so havi…
True. Although you could probably design an algorithm which requires so many of the capabilities of a CPU, like a fast 64-bit FPU and a lot of cache, that the transistor count of an ASIC would approach that of a general-purpose CPU produced in much greater volume. This would make special-purpose hardware not cost effective.