• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

What is the mean watchdog_expired?

S

Solaso

Member
Hello. In the new windows version Dash Core version v0.12.1.0 (64-bit) What is the mean watchdog_expired? But active field is 29 days seen.
 
It means that the DASH developers are incompetent and they are unable to put the budget system into the blockchain. So they put the budget system into a normal database, and then they created this watchdog thing in order to fix the multiple databases synchronization problem.

And of course it also means that the masternode owners are stupids, and they vote in the budget system proposals only to feed the marketeers, the advertisers and the youtube channels, instead of voting in order to pay decent developers to do the job that is required.
 
Last edited:
Solaso said:
Oh :confused: inactives Total Masternodes: 4229 = 1104 actives + 3125 inactives [4196 unique IPs] (Last refresh: Wed Feb 08 2017 6:02:33 PM)

https://dashpay.atlassian.net/wiki/display/DOC/Updating+to+12.1+-+Masternodes
I have a 10gb, but upgrade servers to 20 gb it will increase a cost 20%-25% for me :(

Oh, and 1GB RAM will increase a cost 60%. It about 80%-85% increase cost for one server
Click to expand...
"Inactives": 70103 MNs do not have Sentinel, so the are not "active" for 70206 nodes (but still paid during migration).

Even though requirements are listed as "minimum" I would consider them as "minimum estimated", so update dashd and if it's not enough to keep up - upgrade hardware. If node is running fine, keep it.

But even with 1GB ram, 40GB ssd:

+ $134.09/mo https://dash-news.de/dashtv/#value=1000
- $10/mo 1GB ram, 30GB ssd https://www.digitalocean.com/pricing/#droplet
- $1/mo +10GB ssd https://www.digitalocean.com/pricing/#storage
= +$123/mo
 
UdjinM6 said:
"Inactives": 70103 MNs do not have Sentinel, so the are not "active" for 70206 nodes (but still paid during migration).
Click to expand...

Can I compile the dashd and make it report that it is version 0.12.1 although it is not? Is that possible?

Beware.

This is one of those types of questions, that if you choose not answer it (and as long as you are the main dashd developer) then I will report you here.
 
Last edited:
demo said:
Can I compile the dashd and make it report that it is version 0.12.1 although it is not? Is that possible?

Beware.

This is one of those types of questions, that if you choose not answer it (and as long as you are the main dashd developer) then I will report you here.
Click to expand...
Sure you can, dim-o. You can also watch your custom-built daemon get kicked off the network regularly for not communicating on new protocol standards afterwards.
 
Macrochip said:
Sure you can, dim-o. You can also watch your custom-built daemon get kicked off the network regularly for not communicating on new protocol standards afterwards.
Click to expand...

And what if I preserve the protocol standards, then add some other "features"? Like ignoring the /dev/random for example.... But still reporting that I am 12.1 version?
 
Last edited:
Macrochip said:
Sure you can, dim-o. You can also watch your custom-built daemon get kicked off the network regularly for not communicating on new protocol standards afterwards.
Click to expand...

You said that a custom-built deamon will get kicked off the network for not communicating on new protocol standards.

Are you sure about it? What are those protocol standards that will result the ex-communication of the custom-built deamon, especially if this custom-built deamon reports as 12.1? Can you name those protocol standards?

And what about this masternode? It reports as version "Unknown", but it is considered as active and nobody has kicked it off the network until now.
 
Last edited:
You must log in or register to reply here.
Back
Top