Search results

Lol, I had the same problem, thought I'd just need to copy over files and change the IP and there was nothing configured in it, it was all still in dash.conf. The format should be explained in masternode.conf but if not: # Masternode config file # Format: alias IP:port masternodeprivkey...

Do a "masternode start-alias" with the name set in masternode.conf (ie. "masternode start-alias mn1"). The network will still see old starts from the 70103 client, that clears it up and issues a fresh start.

Can't remember if that 12.1 on 70103 is from a caching issue or from starting via Electrum, one or the other though :/ Asking around at the mo, your offline wallet is also running 12.1?

What block are you on, same as here? https://www.dashninja.pl/

What does "dash-cli getpeerinfo" give you, all version 70103 peers? Might be worth stopping, deleting peers.dat and restarting if so, could be it hasn't seen any 70206 peers yet. Could also be worth deleting mncache.dat at the same time, not sure if it's related to your problem but it's better...

Not sure but they might be following different sides of a fork, they're at the same block height? "dash-cli getchaintips" might also give some indication if that's happening, if it is they should sort themselves out and all get back on the longest chain but starting with "- reindex" might sort...

They're the ones that deserve it really but no problem at all :) I almost forgot to mention, server requirements have been raised for 12.1 so a server upgrade at the same time might make sense. 1GB RAM minimum and 40GB hard drive space, for now you might get away with less hard drive space (it...

That could be the simplest thing to do, it will take a few hours to get the blockchain up to date but at least you'll know everything is as it should be. This script is very useful for managing masternodes btw but it's not up to date with 12.1 yet, it should be up to date in the next few days...

Ah, that one. Ok, it's a little out of date for 12.1 and if you didn't copy or renamed any directories for the update the you've probably got a completely new installation, the old client installs in /home/USER/.dash and the new one installs in /home/USER/.dashcore Go to the home folder ("cd")...

No, the blockchain needs to be reindexed for 12.1 but it's fine otherwise. The all the *.dat files are safe to remove and mncache.dat may be causing your problem, peers.dat can cause some issues, etc. Simpler to remove them all and start fresh if there are any doubts but certainly try deleting...

You've tried restarting dashd? Something else maybe worth trying, stop the client (dash-cli stop) and delete all the files with a *.dat extension from the .dashcore folder except wallet.dat, restart the client and test sentinel again. The client will take some time to rebuild those files and...

I'm not sure, asked around and someone should be back before too long though. Try this command from inside the sentinel folder, it might give some more info: ./venv/bin/py.test ./test It runs some sentinel self-tests and should come up ok almost immediately.

Do you have rpcuser=<replace> and rpcpassword=<replace> in dash.conf? "<replace>" can be changed to anything but as far as I know they're needed to use the RPC interface. rpcallowip=127.0.0.1 should also be in there to only allow connections form the same machine. EDIT: A sample, might not need...

You've installed Sentinel? More updating instructions here: https://dashpay.atlassian.net/wiki/display/DOC/Updating+to+12.1+-+Masternodes

Delete mncache.dat. All the *.dat files can be deleted (other than wallet.dat of course), I had to delete peers.dat too.

It's splitting up parts of the network, something along the lines of one IPv4 network for PrivateSend and another for IPv6. There where only a small number of IPv6 nodes so simpler to disable it and spend some time on it rather than patch it up, quite a few tasty networking possibilities but...

12.1 isn't out yet but the testing release has been out for a while and does both mainnet and testnet, which is specified in the dash.conf file or with the launch command. There are a couple of threads about 12.1 testnet on the forum here and there are links to the client download it in the...

You can copy the original directory to the new location or just rename it (or tell it to use the original directory with "-datadir"). I had to delete both mncache.dat and peers.dat before it would start and it had to reindex but running fine now.

Transparency creates trust which in turn creates value and blockchains can be entirely self-auditing, can addresses be used for parts of the outlay? And could hiring be considered for tender? If the books are split up before fiat is involved then there can be competition for accounts.

I reckon he's either working for bitpay or up to his eyeballs in some other crypto. And I bet dash.org is the number one hit for "snowflake" before the month is over ;)