Search results

The problem is: I used the same masternodeprivkey on several masternodes. I experienced the same problem as described after 3 months when I hit "start-disabled" once more after one mn had crashed. The interesting thing that mns can work properly even with the same masternodeprivkey - and they...

What I have: Two masternodes (lets A and B) and configured start-many to start them. Local: Windows 7 x64, wallet.dat with keys for A and B, masternode.conf, remote: ubuntu x86_64, dash.conf with mnprivkey, ufw with opened 9999, no iptables, dashwhale v4 script for monitoring. Last versions of...

Got it, thanks.

And why precisely someone needs to alter it? Because of sigtime (expiration period?)? IP (I believe it's hot wallet's ip) and the protocol number are constant for every starting message.

When one hit "masternode start" some message is forming and propagating through the network. For now masternode gets to the end of payment queue after "masternode start". Is it possible to save someone's valid "masternode start" message and rebroadcast it later (to kick other masternodes down...

v49 MN crashed tonight: Now: .dash/dashd ..waiting .dash/dash-cli getinfo > *** Error in `.dash/dashd': free(): invalid pointer: 0x00007f10dc0240c0 *** > error: no response from server and > error: couldn't connect to server Deleting all except daemon and blocks didn't solve the problem, the...

For now, when we got rid of reference node, will Evan turn off the enforcement on every update (here goes fud about centralization blah blah blah)? Are there ways to avoid that?

Same for me. After restarting they appear in ./dash-cli masternodelist full as ENABLED, then as EXPIRED and then dissapear. ./dash-cli masternode status on both hot and cold wallets at all the moments shows smth like { "vin" ...

What do you want? This one? ./dash-cli masternodelist full | grep "SERVER_IP"

But there's no "status" in such output (it can be ENABLED or EXPIRED - don't know what does it mean but EXPIRED looks more negative than ENABLED). I wonder how to combine mastenodelist "addr" with masternodelist "status". One can use ./masternodelist | grep "txid" instead. Txid is a txid of...

There're txids now. Try ./dash-cli masternodelist "addr"

Looks like it is. My mn became "EXPIRED" after a while so I've restarted.

Why not to pay multiple masternodes in one block to smooth rewards? (block size?) I know we are testing new technology but there are someone always disappointed with all that enforcement off, reference node restarts, forks and stucks. Generally speaking I don't remember any month among last six...

Mn payment=37.5% at 209840 and annual reward reduction at 210240, right? It'll compensate each other: (13/14)*5*0.375 =~ 5*0.35 ^^

The same, tons of it. Log is 270mb after an hour.

My win64 client, synced and with 8 conns, fills its mn list unbelievable slow.

http://explorer.darkcoin.io/chain/Darkcoin is stucked on 205418 with different hash.

I'm on 204718 as explorers are and have the same hash.

What will happen if there're a lot of masternodes which are capable (:1 in list) but stucked on the wrong chain\blockheight? Surely they aren't able to process darksend txs. Looks like that result in ds completely broken for a while. I can compare with some kind of attack when a lot of...

I am no longer able to panic after observing btc\usd on 13th Jan. :grin: