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

How to update UNOMP RPC call for altcoin with core v0.17+ #300

Open
wes45 opened this issue Nov 19, 2018 · 7 comments
Open

How to update UNOMP RPC call for altcoin with core v0.17+ #300

wes45 opened this issue Nov 19, 2018 · 7 comments

Comments

@wes45
Copy link

wes45 commented Nov 19, 2018

After updating wallet core to v0.17 UNOMP reports this error below concerning getinfo needing to be replaced by getnetworkinfo. Could someone please advice what files to edit to fix this?

Pool Thread 1 Could not start pool, error with init RPC getinfo - {"code":-32601,"message":"getinfo\n\nThis call was removed in version 0.16.0. Use the appropriate fields from:\n- getblockchaininfo: blocks, difficulty, chain\n- getnetworkinfo: version, protocolversion, timeoffset, connections, proxy, relayfee, warnings\n- getwalletinfo: balance, keypoololdest, keypoolsize, paytxfee, unlocked_until, walletversion\n."}

@ahmedbodi
Copy link
Member

Help with this can be bought here:
https://www.fiverr.com/ahmedbodi/setup-a-cryptocurrency-mining-pool

@mooleshacat
Copy link

mooleshacat commented Dec 2, 2018

@ahmedbodi stop spamming issues with spam to make you money. Any idiot with half a brain can set up a pool, and I would do it for less than 50$ forget the 500 or so you charge on fiverr

@wes45 what coin is this for? Can you please post your coins/coinname.json and pool_configs/coinname.json?

========

I will be working on this compatability issue with EASYNOMP but this is a per-coin issue, it affects multiple coins.

Thanks

@ahmedbodi
Copy link
Member

ahmedbodi commented Dec 2, 2018

I'm welcome to post as i wish. This is far from a per-coin issue. I've fixed this issue in the NOMP Codebase. UNOMP is so far outdated it makes 0 sense to continue working on this codebase. If an idiot with half a brain could setup a pool securely i dont think there would be a repository filled with such issues. You're welcome to do it for whatever price you like. I'm not stopping you. I've been doing this stuff before NOMP even existed. Experience says a lot.

@ScriptProdigy
Copy link

ScriptProdigy commented Dec 28, 2018

Also experiencing this issue, was hoping it was already fixed. Will post my fixes here once complete free of charge.

EDIT:
Following https://github.com/zone117x/node-stratum-pool/pull/133/files
in node_modules/merged-pooler/
does the trick. No need to charge people for something already public and working.

@Teejayare
Copy link

is there a way to support both getnetworkinfo and getinfo for 2 different algos on the 1 pool

@ScriptProdigy
Copy link

is there a way to support both getnetworkinfo and getinfo for 2 different algos on the 1 pool

Its sloppy but you could integrate retrying on error of getnetworkinfo with getinfo. Quickest way I can think of, try getnetworkinfo, if there is an error try getinfo and return that

@Teejayare
Copy link

I tested the method here... https://github.com/zone117x/node-stratum-pool/tree/master/lib

Looks to have both yet still does not work. Would you have another way / example please?

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

5 participants