Closed Coinomatron closed 4 years ago
Hardfork coming with 6.0.0
Yea, I knew about the hardfork. So what client works best with mining? Last nomp error was this one. Wallet was unlocked.
Daemon returned unexpected return code 500, data = "{\"result\":null,\"error\":{\"code\":-22,\"message\":\"Block signatures couldn't be created\"},\"id\":1572131121324}\n"
Do you have at least one output as a P2PK, because this is required within the coinbase transaction template to sign the block with it
Hm, that's not anywhere in the debug file, so maybe this error doesn't pertain to submitted blocks?
It even says: "Block signatures couldn't be created"
There are two reasons for this either your not using a publickey output within your coinbase transaction or your wallet isn't locked.
CoinbaseTx {
outputs {
PubKey -> 0 XVG
PubKeyHash -> 730 XVG
}
}
that's how your transaction could look like, maybe you can just activate the POS mode for verge and it will work eventually
Uhm, pos 'mode' ? Does that mean in the coin.conf I should add "Reward": "POS" ?
is there a hybrid option?
Yea, I guess I can put that in the coin conf. I'll fiddle some more with it, or just use a pool. On a side note, the 4.0.2 client, after I created a new wallet.dat for mining, keeps rescanning the blockchain, which takes ages on a restart. Any idea how to fix that?
doesn't it have a hybrid option?
ah, POS if using ver 4, but you should use 6
Version 4 does submit blocks (algo lyra2rev2), but they're all orphaned (10 in a row). Haven't seen any block submission on 6, just the above error about not being able to sign blocks. Had that too with the 'hybrid' option in the coin.conf. Not really sure what to do about it anymore.
@Coinomatron are you on v6 and ready to go?
Thanks for the heads up, I upgraded a few days ago. Closing this, might re-open if I feel like experimenting with mining again and run into things.
Hello there, I've got the same Problem with my nomp solo pool. I'm using the newest version of the coin daemon but everytime when there's a block found this error occures in nomp:
rpc error with daemon instance 0 when submitting block with submitblock {"code":-22,"message":"Block signatures couldn't be created"}
This is my VERGE.conf
rpcuser=vergerpc rpcpassword=test12345 rpcport=20102 port=21102 daemon=1 server=1 listen=1 listenonion=0 maxconnections=38 rpcallowip=127.0.0.1 algo=scrypt
Idk how changing reward type in nomp's coin.conf can fix the problem. When I do that nomp still tells me after startup:
Detected Reward Type: POW
Or do you mean that I should somehow set in my qt.conf reward type to pos? If yes, I don't know how to do that.
is there a hybrid option? are u signing the block? whats ur debug on the verge dameon say?
I don't know if there is a hybrid option. As far as I know Verge is only pow right now. I even don't know how to sign a block, so I guess not. Time code of nomp error compared with timecode of debug.log doesn't show any suspicious error message. Error occured at 13:35:14
2020-04-07T13:34:20Z FindStealthTransactions() tx: 7707f398e5a3b9e5302fce951f124b16aa98ce11980eb47bb6a6133c60f4e280 2020-04-07T13:34:20Z CreateNewBlock(): block weight: 796 txs: 0 fees: 0 sigops 400 2020-04-07T13:34:53Z connect() to 94.130.90.213:50002 failed after select(): Connection refused (111) 2020-04-07T13:34:54Z connect() to 91.250.119.239:50002 failed after select(): Connection refused (111) 2020-04-07T13:34:54Z connect() to 94.130.90.213:50001 failed after select(): Connection refused (111) 2020-04-07T13:35:09Z UpdateTip: new best=6928704acd3955edeebbf64bb7ea512b799a1108cfd3deb06107953afe0f1905 height=3962317 version=0x00001004 log2_work=86.267974 tx=8362707 date='2020-04-07T13:34:22Z' progress=1.000000 cache=1.0MiB(6859txo) 2020-04-07T13:35:09Z FindStealthTransactions() tx: 8b5e45c571dc63e564e5b00e150b9a502a8c24c3571a9a11fa05e00dbf616d17 2020-04-07T13:35:09Z CreateNewBlock(): block weight: 796 txs: 0 fees: 0 sigops 400 2020-04-07T13:35:43Z UpdateTip: new best=1a605a81740cb8ade34b67bda8128a154adf7d3d14287a9821d52f09fb8fceb9 height=3962318 version=0x00001804 log2_work=86.267976 tx=8362708 date='2020-04-07T13:35:09Z' progress=1.000000 cache=1.0MiB(6861txo) 2020-04-07T13:35:43Z FindStealthTransactions() tx: 92ac7d1142e02a377c12da51827d6297c7a4ab2ed6a9e0269f7ef980e40e1f39 2020-04-07T13:35:43Z CreateNewBlock(): block weight: 796 txs: 0 fees: 0 sigops 400 2020-04-07T13:36:16Z UpdateTip: new best=16ff30881de85dae616187605b421ff4ed58b02f1ad258914865e35133bccc4f height=3962319 version=0x00001804 log2_work=86.267978 tx=8362711 date='2020-04-07T13:35:42Z' progress=1.000000 cache=1.0MiB(6870txo) 2020-04-07T13:36:16Z FindStealthTransactions() tx: 8f03d0d2cd3414435dfe750b378986bd5633dff38b90316e41e6ff678ac22da6
what version of the xvg daemon are you running? @Widi92
I'm using v6.0.2
try switching nomp conf to pos.
Already tried that before, still not working.
@justinvforvendetta Thanks a lot, it's working now!
hellz yeah
Hi, I tried solo mining on the 4.0.2 client as well as the 5.3.0, but all I got was errors in nomp when submitting a block. Is nomp working at all with verge or is there some special software required? Also, what verge version should be used for mining? Thanks.