Search results

Would it make sense to still support DNS in the config file, i.e. do DNS lookup and use the IP thereafter when sending broadcasts etc? So, my use case is that I have a static IP on my server, however, that IP depend on what VPS I choose to fire it up on. A dynamic DNS is updated as the server...

Hi, I've tried using DNS names in masternode.conf, but with no luck. Seems to require IP:s. Is there any good reason for this? The -dns command line switch is only for -addnode, -seednode and -connect I guess it may be related to the static IP requirement for a masternode. I never understood...

Thanks! That worked! Also, man you are quick with updates. Noticed dashman trew an error as the Dash download page changed. Not many minutes before you fixed it. Thumbs up!

Hi, I just tried 'vote', but got the following error: KeyError: 'masternodeaddr' I'm using dash.conf for configuration. There's a dummy masternode.conf as well containing comments only. Removing masternode.cong changes the error to "cannot find masternode.conf". Do I need to specify...

Ah, I see. Cheers!

Great work! One question though: In the Trezor firmware commit I see the string set to "DarkCoin Signed Message". Shouldn't it say Dash rather than DarkCoin? Cheers!

That makes sense. Thanks!

Hi, I remember reading that in order to for masternodes to get paid they need to run the latest version. This works well as an incentive to keep all nodes up to date. The official Dash client download page list the required version for MN operators. So, is there some slack here or is this...

It has no masternode capabilities, right?

I have not. I was quick with upgrading to v12 and running 'masternode status' sais 'successfully started'. I upgraded from .46 to .47 about an hour ago, but dashninja still list my node as .46. Anyone know if that is common? ::EDIT - Listed as .47 now :) Still awaiting payments though!