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

Issue on bemicro #10

Open
chantpower opened this issue Jan 9, 2014 · 1 comment
Open

Issue on bemicro #10

chantpower opened this issue Jan 9, 2014 · 1 comment

Comments

@chantpower
Copy link

I set it up to test on my bemicro and the mine.bat runs fine, but theres an error "ERROR: Unable to getwork. Reason: key "result" not known in dictionary."

Would that be an error with the mining pools I'm member to, or did I miss a file or something?

I took all the files from "scripts" "source" and "bemicro" do I need a stratum proxy to mine?

@kramble
Copy link
Owner

kramble commented Jan 9, 2014

Its worth giving it a try. The getwork protocol is now very much depreciated by the pools and even if it is available, there is no guarantee its compatible with what the mining script is expecting (its very old code, based on the bitcoin fpga open source project). Be sure to use the litecoin proxy from https://github.com/CryptoManiac/stratum-mining-proxy as the original bitcoin proxy won't work properly.
Start it as follows (on linux, for windows omit the ./) ...
./mining_proxy.py -nm -pa scrypt -o litecoinpool.org -p 3333

Use your own pool instead of litecoinpool.org - NB it does not require a username as this is passed through from the mining script when it does the RPC. It also outputs useful logging information so you can see if shares are being submitted. Just be aware that a [0ms] ping time for the submission actually indicates that the share was rejected within the proxy stack (it does not report an error, which is a bug), usually because of a HW error (a bad hash, which does occur occasionally due to timing issues on the vitual_wires interface, but too many errors indicates that you're clocking too fast).

Good Luck!

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

2 participants