-
I spun up three masternodes Dec 19 around 4pm. The following morning, all masternodes were running as expected but the status in my wallet was `WATCHDOG_EXPIRED` for all three masternodes. All three n…
-
I updated all my nodes today, including my wallet for 12.1 testnet.
I have 9 entries in my masternode.conf file. 4 of those entries were EXPIRED because I took those nodes offline. The other are st…
-
Our current heuristics for determining if a masternode is up, running, and ready to perform all tasks is really very crude. See below. I.e., At this time, apparently only a masternode ping(?) is requi…
taw00 updated
7 years ago
-
It looks like someone is attacking the network as I just saw 42,104 "nm winner" inv announcements (the hashes were in numerical order also) from a node, which is considerably more than the number of m…
-
In 12.1 masternode vin's in masternode.conf are not locked in the wallet if the local node is itself running as a masternode.
This makes it easy to accidentally spend collateral and hence lose master…
-
v0.12.1.0-c86439a
New empty wallet.
Masternodes tab -> **node count** is not right, and mn list is empty.
@UdjinM6
EDIT: This error was after new wallet created, but after restart node count is OK.
…
-
After filling all the data neccesary in the wallet/masternodes and after activation I get this info, check the attached file, and the masternode is not seen in the network. (the windows "Signing Maste…
-
### Describe the issue
Certain clients and operating systems have difficulty flushing to DB right after allocating a new block file.
### Actual behavior
2017-04-28 01:53:09 Leaving block file 2: …
-
if(service.GetPort() != 9999) {
notCapableReason = strprintf("Invalid port: %u - only 9999 is supported on mainnet."
else if(service.GetPort() == 9999) {
…
-
Sentinel, and in particular, the `python-bitcoinrpc` that it relies on, have hard-coded timeouts of 30 seconds to receive the results of dash rpc calls. This is probably fine. Maybe the timeouts shoul…