Search results

Any changes in masternode from hardware-wallet problem? ;)

Any new info about Ledger or Trezor and starting masternodes?

Yeah, I did it already. I hoped that this is cause of our problem but it is not. I change it to correct and masternodes go to ENABLED but minute later some of them go WATCHDOG state again... PS. It seems that for me problem is solved. If not I let You know.

Maybe only I'm so stupid but... do You modify this below or just copy paste into cron like I do? */5 * * * * cd /home/YOURUSERNAME/.dashcore/sentinel && ./venv/bin/python bin/sentinel.py 2&>1 >sentinel-cron.log */5 * * * * cd /home/---------HERE---------/.dashcore/sentinel && ./venv/bin/python...

Do not have special chars in rpcuser and rpcpassword and WATCHDOG_EXPIRED problem.

So I started it by start-alias. Should I stop it and start by start-missing? Do I understand it corectly: remote dash.conf - only two lines? (masternode=1 and privkey?)

It might be that problem is solved. Thank You! Solution: dash.conf file is not needed again. Later I must start local DASH normal or in masternode-ready mode (with especially prepared dash.conf file). Now I create masternode.conf (I do not have it at all earlier). I run DASH normally, without...

Yeah, I know masternode.conf, but something changed in dash.conf. For example: masternodeaddr=xxx.xxx.xxx.xxx does not work... rpcuser=..................................................... rpcpassword=........................................................... rpcallowip=127.0.0.1 listen=0...

Do not have any alias in masternode.conf... I do not modify this file from about two years. Can You give me link to a proper .conf file for a today times? ;) https://www.dash.org/forum/threads/taos-masternode-setup-guide-for-dummies-updated.2680/

Offline wallet is running 12.1 as a first instance and it is core. 18:49:49 masternode start-missing 18:49:49{ "overall": "Successfully started 0 masternodes, failed to start 0, total 0", "detail": { }} 18:49:58 masternode list-conf 18:49:58{}

YES dash-cli getblockcount 616547

Done already. "dash-cli getpeerinfo" show 70103 peers and one 70206... But DASHninja is showing: v0.12.1 p70103 ???

dash-cli getinfo: "version": 120100, "protocolversion": 70206, "walletversion": 61000, "balance": 0.00000000, "privatesend_balance": 0.00000000, "blocks": 616511, "timeoffset": 0, "connections": 8, "proxy": "", "difficulty": 77817.46919843456, "testnet": false, "keypoololdest": 1415488991...

Two updates in 5 minutes... ;)

Done. ;)

drk.mn - there is no mn with v11.1.19? Why? I upload v11.1.19 and is presented as v11.0.14...

Muszą być nieruszane. Nie muszą i nie powinny być na VPN-ie tylko na jakimś bezpiecznym wallecie rzadko podłączanym do sieci. Walleta będziesz używał raz na ruski rok aby uruchomić masternoda. Zazwyczaj przy zmianie nr protokołu co odbywa się o wiele wiele rzadziej niż upgrady klienta darkcoina.

Do it thousand times with bitcoin, hundread with darkcoin and do mistake. Maybe is because of too much whiskey. ;) Now everything is OK with all my masternodes. Only this one I does it harder way. But it works too. ;)

F**k. I just erase everything except blockchain so do -reindex HARDER way. ;)

Darkcoin server stopping xxx@install:~$ ./darkcoind -rescan Darkcoin server starting xxx@install:~$ ./darkcoind getinfo { "version" : 110007, "protocolversion" : 70052, "walletversion" : 60001, "balance" : 0.00000000, "darksend_balance" : 0.00000000, "blocks" : 204572, "timeoffset"...