Not working with another SHA256 coin

[pool2mine]

Hi, i am trying to start the pool with Digibyte, which is also sha256, but i get a lot error when starting...........

EDIT: Digibyte wallet changed some RPC calls, so coin is not supported right now

[pool2mine]

i get this error when trying to run:

2023-07-13 00:51:07 Pool        [Digibyte] (Thread 2) Share processing setup with redis (127.0.0.1:6379)
2023-07-13 00:51:07 Pool        [Digibyte] (Thread 2) Could not start pool, error with init RPC getinfo - {"code":-32601,"message":"getinfo\n\nThis call was removed in version 6.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\ndigibyte-cli has the option -getinfo to collect and format these in the old format."}

seems like Bitcoin also changed the RPC call method as it gives a simillar error.

can you please point me in the right direction? I can't find that RCP call on the code

[Canefis]

You should remove "getinfo rpc method"

[pool2mine]

when i set it "false" it also gives a lot of errors

[Canefis]

On yiimp dgb is ok with getinfo, but asic boost does not support. Miningcore same: does not support asic boost

[pool2mine]

if you need to work with asic boost after a lot of testing i finally found this nomp repo..... https://github.com/meterio/nomp/tree/master

it worked for me.

only problem with nomp is that it's very old and outdated, API is very simple and limited. i hope someday miningcore fixes asicboost support, but in the meantime, this one does the job.

[Canefis]

Are there any known restrictions or issues we should know? Since early 2018, DigiByte has been in the process of changing newly generated wallet addresses from the "D" prefix to "dgb1" as part of bech32 support, and from "3" to "S" for SegWit addresses. Legacy address formats will continue to be supported indefinitely, so please allow for both. As of 6.16.x, DigiByte has implemented upstream Bitcoin Core 0.17 RPC formats. Common calls that exchanges / pools need to know about is that getinfo has been replaced by:  getblockchaininfo  getnetworkinfo  getwalletinfo  getmininginfo In addition, signrawtransaction has been split in to two calls:  signrawtransactionwithkey  signrawtransactionwithwallet signrawtransactionwithkey requires private keys to be passed in and does not use the wallet for any signing. signrawtransactionwithwallet uses the wallet to sign a raw transaction and does not have any parameters to take private keys. We strongly advise also being aware of this where integrators are using the RPC calls directly, this call will no doubt be deprecated across other wallets going forward too as they bring themselves up to speed with the Bitcoin Core codebase. Where existing products and services are using signrawtransaction, you should simply use signrawtransactionwithwallet in its place. In addition, if you’ve been making use of the ismine value in validateaddress, you’ll want to instead call getaddressinfo, as the result is being returned there. The accounts RPC call is also being changed, we recommend viewing the release notes from Bitcoin Core: https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes0.17.0.md Do you have a sample digibyte.conf that you would recommend? Sure:

Place this config in the following path:

~/.digibyte/digibyte.conf

server=1 daemon=1 txindex=1 rpcallowip=127.0.0.1 maxconnections=300 addnode=seed1.digibyte.io addnode=seed2.digibyte.io addnode=seed3.digibyte.io addnode=seed.digibyte.io addnode=seed.digibyteprojects.com addnode=digihash.co addnode=digiexplorer.info addnode=seed.digibyteguide.com addnode=seed-1.us.digibyteservers.io

[pool2mine]

your pool should run with a legacy wallet with no label ("")

[Canefis]

if you need to work with asic boost after a lot of testing i finally found this nomp repo..... https://github.com/meterio/nomp/tree/master

it worked for me.

only problem with nomp is that it's very old and outdated, API is very simple and limited. i hope someday miningcore fixes asicboost support, but in the meantime, this one does the job.

Hi, thanks for suggesting to me this repo. I am gonna to install it and use for digibyte. So, you just follow instruction and everything works fine for dgb (sha256) asic boost, right? Can you share please digibyte.conf and command to get legacy pool address. Also what additional software did you use to make webUI interface if any and monitoring your pool, thanks a lot anyway. I am little nooby in programming, but somehow could install succesfully a zil node myself, sounds crazy, I spent 4 months for this, but did! So, I hope to make it too 😄 Yiimp also installed succesfully "firefox2014 repo" and minincore "xiaon1579 repo", but those 2 do not support asic boost.... ☹️

[pool2mine]

the repo includes a simple website you can use to monitor. it's simple because api endpoint is very limited. i installed it some months ago for bitcoin testing, but i remember it was updated and i had no issues.

regarding wallet, this is what i did with bitcoin (you should change command according to your coin binary:

bitcoin-cli createwallet "" then stop node, update your conf file, start node again so it load your wallet and... bitcoin-cli -testnet getnewaddress -addresstype legacy

after wallet loads again you should be able to connect to your pool... i can't find my config as this was just a test i was doing with BTC testnet, but if you have any issues running the pool you can share your config and i will help you in whatever i can

[Canefis]

the repo includes a simple website you can use to monitor. it's simple because api endpoint is very limited. i installed it some months ago for bitcoin testing, but i remember it was updated and i had no issues.

regarding wallet, this is what i did with bitcoin (you should change command according to your coin binary:

bitcoin-cli createwallet "" then stop node, update your conf file, start node again so it load your wallet and... bitcoin-cli -testnet getnewaddress -addresstype legacy

after wallet loads again you should be able to connect to your pool... i can't find my config as this was just a test i was doing with BTC testnet, but if you have any issues running the pool you can share your config and i will help you in whatever i can

Thanks.