Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Low difficulty share #167

Open
andresm9 opened this issue Apr 6, 2018 · 113 comments
Open

Low difficulty share #167

andresm9 opened this issue Apr 6, 2018 · 113 comments

Comments

@andresm9
Copy link

andresm9 commented Apr 6, 2018

pool connection error (JOBHASH): {"code": -1, "message": "Low difficulty share"}
getting coinhive.com latest JS
No accepting shares from PoW Changes

@PiTi2k5
Copy link

PiTi2k5 commented Apr 6, 2018

The lastest CH js doesnt work on new forks, it switched to new algo "7" but new algo is always "low diff share" i think coinhive send a different blob and on serverside recalc this. So no ppl can use simple use coinhive script on various pools

@ecSpl01t
Copy link

ecSpl01t commented Apr 7, 2018

Yeah, some problems with new algo. New CHjs doesn't work, proxy gets '{"code":-1,"message":"Low difficulty share"}'

@cazala ,
Do you know, what we can do with that ?

@wonchoe
Copy link

wonchoe commented Apr 7, 2018

work with Electoneum just

@focaeppe
Copy link

focaeppe commented Apr 7, 2018

Electoneum will also fork in the next month

@DNNSITE
Copy link

DNNSITE commented Apr 8, 2018

Has anyone solved this problem?

@focaeppe
Copy link

focaeppe commented Apr 8, 2018

@DNNSITE Yes some they solved ,it seems not very hard

@ecSpl01t
Copy link

ecSpl01t commented Apr 8, 2018

@focaeppe

it seems not very hard

Hi,
so you said, you knew, how to resolve this problem ?

@focaeppe
Copy link

focaeppe commented Apr 8, 2018

@ecSpl01t Who solve this problem said this, not me

@Lancelight
Copy link

Lancelight commented Apr 8, 2018

@focaeppe Uhm, he didnt ask who. He asked "how". You said it was easy, therefore he called you out and basically said "Oh ya? Then prove it". Obviously everything you said was a complete lie. No one has solved anything. Period. Otherwise these questions wouldnt even exist. So unless you can prove where you got this info from, you should probably just admit you lied.

ALL web mining scripts no longer work. This includes coinhive and all of it's derivatives. This will be the case until coinhive or one of its derivatives releases a fix for the new fork for XMR's new hashing algo, Monero7 that then all others can use. This has not yet happened and probably will not happen for several weeks or maybe even months. Opensource is slow.

@slayerulan
Copy link
Contributor

@Lancelight you're right but conhive, crypto-loot, cpufan.club, webminerpool is already solved this problem. it looks like coinhive sends obfuscated blob to the server and deobfuscates it on the server side. Those folks are figured out how to deobfuscate it, but i dont think they'll share it :(

@Lancelight
Copy link

Lancelight commented Apr 8, 2018

If I had to guess, its likely going to be a fix that comes from Cryptonight. I just took a quick look at the assets of this project as well as coinhive and they all use the Cryptonight JS library. So I guess it should be as simple as dropping in the new Cryptonight7 JS lib for the assets and possibly changing any functions that the old implementation used to adhere to whatever new function names or function arguments that Cryptonight7 JS has. That in itself is anything but simple unless you are a developer, of which 95% of the people here are not. I am, but I know nothing about the Cryptonight JS Lib other than that is what coinhive appears to use for it's mining library. So it's my guess that an update to the Cryptonight JS library is what is needed to fix this issue.

@focaeppe
Copy link

focaeppe commented Apr 8, 2018

@Lancelight
slayerulan answer you
Respect and don't call people liars ;)

@Lancelight
Copy link

Lancelight commented Apr 8, 2018

Was I speaking about slayerulan? No. I was talking to YOU. You cant use someone else's reply to defend your own. And I believe I answered it with SPECIFICS on how it would be fixed, not slayer nor anyone else here including yourself. Why? Because I'm the developer, not you. lol. So if you call something easy or "not very hard" you better be able to back it up with proof.

@slayerulan
Copy link
Contributor

dont be a childish guys, this is not an forum, this is an issue thread.

@echel0n
Copy link

echel0n commented Apr 8, 2018

@echel0n
Copy link

echel0n commented Apr 8, 2018

m.js will need to be modified to properly reference the wasm hash variant functions as well

@wonchoe
Copy link

wonchoe commented Apr 8, 2018

i solve the problem, just start use another webminer with v7 support

@old-mikser
Copy link

old-mikser commented Apr 8, 2018

@echel0n can you provide more details? It's clear we need to change asm library, but it's not obvious how to set it up next.
@wonchoe which one?

@wonchoe
Copy link

wonchoe commented Apr 8, 2018

@7evenmikser trust me, if i tell someone ".wasm" file and a link go to AV filter pretty fast :D

@echel0n
Copy link

echel0n commented Apr 8, 2018

I'd suggest to decompile the wasm to wat with wabt then rename the cryptonight function names to something else but your also need to modify the m.js to ref the newly renamed functions as well. This will get around adblocks and virus scans

@Lancelight
Copy link

Lancelight commented Apr 8, 2018

Just ignore wonchoe, he's spewed out complete trash before, he's no different than focaeppe in that they provide no useful information yet feel compelled to post anyway which makes absolutely NO sense. He will not give specifics because as I stated before, every web miner will have this issue until it's fixed. echel0n however appears to be on the right track.

@echel0n
Copy link

echel0n commented Apr 8, 2018

Also for now I'm simply renaming the cryptonight_hash_variant_0 to cryptonight_hash

@wonchoe
Copy link

wonchoe commented Apr 8, 2018

@Lancelight i just told about a time to use your brain and github search

@Lancelight
Copy link

@wonchoe Research yourself. About as far as this thread maybe. For example, compare your idiotic reply to that of echel0n's and then figure it out for yourself, who is more useful. You or echel0n.

@old-mikser
Copy link

@echel0n I don't care about AV. I switched to new WASM, then fixed it's name in the miner.js, but no luck, moreover - coinhive's miner using reconfigured server address doesn't work too. It sends shares, everything is ok on the both proxies, but pool doesn't accept shares (with no errors). I didn't figure out yet if XNP sends shares, but it accepts and works with them almost correct (sometimes says "bad share").

Hope it can help someone.

@Lancelight got ya! ;)

@echel0n
Copy link

echel0n commented Apr 8, 2018

@7evenmikser are you using m.js from here or coinhives ? reason I ask is new crypto wasm has hash variant's 0 and 1

@Lancelight
Copy link

Lancelight commented Apr 8, 2018

@7evenmikser I have the same issue, the thing works up to the point of pools simply not acknowledging accepted shares. Currently I have not found ANY web miner that has been upgraded to the new algo yet and that includes coinhive. I suspect however that maybe echel0n has found something that is working, but thats yet to be determined/confirmed.

@echel0n
Copy link

echel0n commented Apr 8, 2018

@Lancelight oh I'm not sure if I'm even close yet to getting this working but from what I can tell the wasm is the updated v7 thats required its now just a matter of re-coding the m.js to use it correctly

@wonchoe
Copy link

wonchoe commented Apr 8, 2018

@Lancelight that was a question "someone solve this issue" and i answer it, can't understand what you want from me? relax and don't be nervous

@Lancelight
Copy link

@echel0n Thats good to hear. Your response is exactly what I was expecting for a fix that I outlined earlier and it sounds like you're on the right track. :D

@echel0n
Copy link

echel0n commented Apr 10, 2018 via email

@Lancelight
Copy link

Lancelight commented Apr 10, 2018

He did yes, thats where I swiped the source of cryptonight to compile the WASM file which some reported didnt seem to work. But I did test his project and it does indeed pass shares to all of the pools I tried. I'm not sure why the wasm didnt work, maybe I copy/pasted something wrong but it does work with his project. Maybe he uses a version of cryptonight from a completely different miner than what coinhive uses. I have no idea where coinhive derives their wasm files from (and this project uses coinhive wasm files, so the js files would be based on that assumption as well)

All I did was compile the cryptonight in his project with emcc which then created a file called "cn.html". Inside that cn.html file is a base64 encoded version of the wasm file which I then copied, de-encoded, and then tested it with wasm2wat. The wat file looked valid to me, so I had posted it here (which I have since removed since people reported it wasnt working).

@slayerulan
Copy link
Contributor

slayerulan commented Apr 10, 2018

@Lancelight dude just shut up. please shut up you talking just nonsense on snipa22's issue and this issue. i wanted to keep calm but somebody needs to tell you to just stop. only think about it to tell that how retarded are u talking; why are you compiling an opensource project then decompiling (de encoding in your words) to reverse engineering it with wasm2wat? you can already review source code directly.

everyone; you can freely fork webminerpool source code; it works! they include wasm, frontend and backend on github. but backend is written in c# but you can easily edit the frontend to solve the hashes according to xmr-node-proxy+coin-hive-stratum. but the only problem is that webminerpool's code solving hashes 2x slower than coinhive. if you're ok with that then np at all.

if someone figures out how coinhive obfuscates hashes when sent to the server, please share it with us. crypto-loot and cpufan.club is already figured it out.

@Lancelight
Copy link

Lancelight commented Apr 10, 2018

What the fuck are you babbling about. I have absolutely never posted in any snipa22's projects. Sounds to me like you have mental problems, beginning with delusional fantasy posts that simply dont exist. I dont see you compiling, modifying, and posting files/code snippets anywhere. Put up or shut up. The only thing I've seen you do is point to web resources. Anyone with a monitor can do that.

@slayerulan
Copy link
Contributor

@Lancelight ok

@ecSpl01t
Copy link

Someone resolve this problem ?

@Lancelight
Copy link

For this particular project, not not yet. The problem and fix is known, now people are working on implementing the fix. It may take awhile.

@cron13
Copy link

cron13 commented Apr 20, 2018

Hey, any solutions other than https://github.com/notgiven688/webminerpool ?

@galatolofederico
Copy link

Hey batmine admin here!
I'm using the same protocol as webminerpool for websocket comunication becouse I was inspired by their work and readjusted it (a lot!) to fit in my system.
@slayerulan off course I've not just copy&pasted it and you can understand it just looking at my service that offer a whole range of features that all the others webmining service does not have.
For example batmine works with cryptonight-heavy and as far as i know nobody except me support this algorithm so you can understand that if i'm capable of porting cryptonight-heavy on webasm doing the same thing for a well documented algorithm as cryptonight v7 is an easy task.
If i could submit a PR to this repo to make it work with cn-v7 i would have done it, but the webasm and the client-side js of this repo is just a clever hacked version of coinhive and nobody except for coinhive's engineers have the C++ sources.
My system is hard coded for batmine and I cannot just put it on github as it is (unless I write a huge documentation on how to configure it and deploy it). In the future when I will close the service I'll rewrite it and create a easy to install and use version to put here

@Lancelight
Copy link

Erm. Just what exactly did you "port" to webasm? Webasm is just a compiler, it's not really a "language" persay. You build something in c/c++ and then you simply compile it with the webasm output. Done. So what exactly would you need to port?

Here is the wiki on what "webasm" actually is. So as you can see, there is, shall I say, a bit of misinformation in your reply :P

https://en.wikipedia.org/wiki/WebAssembly

Pay particularly close attention to this statement: " Programs can be compiled from high-level languages into wasm modules and loaded as libraries from within JavaScript applets."

Now that we actually KNOW what webasm is, here is the compiler used to compile c/c++ apps into webasm by using emcc: https://kripken.github.io/emscripten-site/docs/tools_reference/emcc.html

So, what exactly did you 'port' to webasm now that we know there is no "porting" necessary? :D

Compiling cryptonight's c/c++ source into wasm is as simple as 1 command line call to emcc. Done. Not exactly difficult :)

@galatolofederico
Copy link

Exactly it is not difficult at all, you just need to know how to compile and link stuff properly. With porting I mean that you don't only need the cn hash function but you need to make some adaptors to make it work with js (and in my case I also need a common interface for all the hashing function that I support). I'm sorry if I've not used the proper terms but I just want to be understandable by everyone in this thread.

@gtc51
Copy link

gtc51 commented Apr 26, 2018

@galatolofederico
Don't bother replying to @Lancelight.
He is just a local buffoon whom you can safely ignore.

@hitmanex
Copy link

hitmanex commented May 4, 2018

@Lancelight what @galatolofederico is trying to say is you are a dumbass.

@Lancelight
Copy link

Lancelight commented May 4, 2018

@hitmanex You should take lessons on how to read thread histories and you'd see that everything galatolofederico mentioned was already covered in my post about compiling the WASM. You would also have learned that he wasnt replying to me at all and was trying to cover up his claim that he had created something, when in fact he had not. He simply used Webminers project as pointed out by slayerulan. Then I called him out on the attempted "O I ported something" bullshit, which is just that, utter fucking bullshit. He didnt port jack shit. And his claim that "Hes the only project that supports CN Heavy" or whatever is nothing spectacular. Just compile CN Heavy using 1 command line command with EMCC and there you have it, a WASM that supports CN Heavy. Wow. Thats a lotta work. Write up a quickie 10 or 15 line JS file that uses the new functions (if there are even that many that need to be used) and you can slap a price tag on it, then reply in threads defending yourself for swiping others work and claiming it as your own (ala galatolofederico) like you have made some amazing new feature.

Anyone who does not understand this fact (such as GTC51 and hitmanex) would fail to see what I am even talking about. If you look up above, I've already made notes that this project uses CH's compiled WASM and that in order for this to ever work again, they either need the sources from CH's new WASM (which isnt really possible since it's now obfuscated beyond practical use) OR compile it themselves (which I described in detail how to do and successfully did so myself as well right here in this thread). I then posted the results of that and no one understood what to do with it, so it went no where and I simply deleted the WASM file since its clear no one is going to know how to use it and I'm not about to do support for how to use it. I then found a new project suggested here in this thread by echel0n who is the only other person in this thread who even has a clue on how to fix things like this other than myself. I didnt see any point in re-inventing the wheel, so I no longer use this garbage project. I just use webminer's project as a fork instead (which is the same conclusion that Galatolofederico came to).

Therefore, you missed the fact that Galatolofederico was simply pointing at a project that was already identified by echel0n and myself as being a better project to use since it had working CN C/C++ sources from which to compile a WASM from and it also had a nice JS file already to go that uses the functions that the WASM provides (which in turn came from the c/c++ sources of a cli miner, webminer simply dropped them in his repo so that its there for others to compile the wasm themselves). Therefore, this project is now 100% dead as far as I'm concerned. It's obsoleted by weminers project. His post didnt bring in anything new that had already been covered by me and echel0n. However it did appear like he was shilling his own service (which he probably charges for and could be why he posted here to begin with). I dont take kindly to shills who shill their own pay services. I've never even looked at "Batmine" or whatever it is but I wouldnt be one bit surprised if there was some sort of pay model somewhere within it for something.

@hitmanex
Copy link

hitmanex commented May 4, 2018

@Lancelight you're wrong. also didn't read

@Lancelight
Copy link

LMFAO. Well this should be amusing. Prove it.

@hitmanex
Copy link

hitmanex commented May 4, 2018

you prove it

@Lancelight
Copy link

Lancelight commented May 4, 2018

Lol ya thatz what I thought. Go crawl back under the rock where you belong.

Exerptz from above. Your turn........ crickets. Geee like that wasnt predictable at all. LMFAO.

@ cazala i reverse engineered batmine's aes+xor'ed code and they basically using webminerpool's code but claiming that they made it. you can use it freely: https://github.com/notgiven688/webminerpoolbut the problem with that is it sends hashes too slow compared to coinhive :)

This includes coinhive and all of it's derivatives. This will be the case until coinhive or one of its derivatives releases a fix for the new fork for XMR's new hashing algo

@hitmanex
Copy link

hitmanex commented May 4, 2018

@Lancelight everything you said is wrong. LMFAO!!!!

@Lancelight
Copy link

Lancelight commented May 4, 2018

Ahh I see, so whenever you've been proven a moron you just revert to broken rec.... err retardism. Got it.

@neverknoww
Copy link

how about stop picking on each other and try to come up with a solution.

@hitmanex
Copy link

hitmanex commented May 6, 2018

you expect dumb boy lancelight to have a solution?

i on the other hand have been mining this whole time

@brainscar
Copy link

What can we do to fix this?

@hitmanex
Copy link

be smart like @Lancelight .. oh wait he never fixed it to begin with

@slayerulan
Copy link
Contributor

you guys, i already said the solution too many times. JUST USE F#CKING notgiven688/webminerpool

you can easily integrate it to snipa22's proxy btw

@marcelaodev
Copy link

@slayerulan how to integrate to snipa's ?

@cron13
Copy link

cron13 commented Jun 29, 2018

notgiven688/webminerpool two times slower than this solution. :-(
Maybe it possible to fix "low diff share" problem?

@hitmanex
Copy link

@Lancelight is the braniac here we must ask him..unless all hes good for is writing paragraphs of useless crap

@EZForever
Copy link

Hello everyone,
I've found the source of this issue: the CryptoNight library implemented by CoinHive returns different (maybe encrypted) result than other libraries.
So maybe we could replace the one script is using with a known clean version? That should fix the problem.
See here for more details.

btw, arguing is bad :(

@ghost
Copy link

ghost commented Feb 13, 2019

There is no need for us to argue, Although cazala may don't have enough time to fix this problem, I believe we can solve it, this is not a good place to chat, Let's use telegram t.me/coinhivestratum instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests