Search results

Ok, done it. Let's see if now they are more stable. Btw do you happen to work for vultr? #justasking ;-)

5$ more :eek:???? WTF I knew this masternode business had hidden costs! Btw, do you know if it is possible to upgrade on vultr without setting everything up from the beginning?

I think if you don't upgrade your masternode does not get paid any longer.

Thank you very much @UdjinM6 . Actually few hours later the masternode broke again. So I started again wondering if I were going to find a way to solve everything by myself this time. But this time I worked fine. Also the other node this morning needed a restart on my computer while the server...

Thanks. Now it works. Do you think you could explain me what happened, and how to get out of it another time?

no, no, my other one is working now. Sorry, I forgot to mention it.

I also added my other masternode as a connection with addnode. The reply was silent. Then I run again the getinfo and the getchaintips. Getchaintips did not change. Getinfo lowered the number of connection from 23 to 21 { "version": 120201, "protocolversion": 70208, "walletversion"...

So, getinfo now gives: { "version": 120201, "protocolversion": 70208, "walletversion": 61000, "balance": 0.00000000, "privatesend_balance": 0.00000000, "blocks": 769068, "timeoffset": 0, "connections": 23, "proxy": "", "difficulty": 35181684.73744042, "testnet": false...

Thank you very much. I investigated a bit more, First of all, I do have dash-cli!!! It's just that to call it I need to call ./dash-cli and not just dash-cli. Some things are so natural for some people that they forget to tell them :-) So I run the dash-cli and here is what I got: {...

Thanks @UdjinM6 I don't have dash-cli tool so I get an: dash-cli: command not found

so on dashcentral it says that the first one has the port open (but it is still not syncing and thus not working) while the second is now working (but it has the port closed). If this did anything it added to the confusion o_O So the first question would be, why is the first masternode not...

From when I upgraded to 12.2 I keep having problems with the masternodes. They keep not working. One is refusing to even start syncing. After 12 hours it still says: { "AssetID": 0, "AssetName": "MASTERNODE_SYNC_INITIAL", "AssetStartTime": 1510777732, "Attempt": 0...

Thanks @UdjinM6. Issue solved!

Hello, it is a few days that my masternode keep dropping off the list. The first time I had to restart it. The next ones the I could not understood what the problem was since it seemed to be running ok. It was synced, and sentinel did not show any problem. Eventually I discovered in the sentinel...

Hey, I got more than 1 MNO. And I'll lend one to @demo just for this time.

Make it one proposal per masternode a month and I will vote for it. As one proposal per day (with 4000+ masternodes) is absurdly high.

You know that asking a proposal costs too much when even the CEO requests back the 5 Dash for asking the proposal. I am tempted to vote no just to make him pay the 5 dash, and realise the cost to make a proposal must go down :-D

Hello. Surely it would be interesting to work together. I am not a social scientist. Merely a mathematician which, after a past in bioinformatics, has in the last decade specialised in eDemocracy and Computational Social Choice. As such my aim is to develop, and guide people in building...

I am not sure what happened, but I checked now and it has finished. IT's like it took more time for it to start. Not sure why.

Hello. I am trying to install a masternode. Unfortunately when I run ./dashd it says that it is starting. But anytime I then run ./dash-cli mnsync status I get: { "AssetID": 1, "AssetName": "MASTERNODE_SYNC_SPORKS", "Attempt": 0, "IsBlockchainSynced": false...