Dash Masternode Status Console

To anyone following, unfortunately, as expected, I did lose access to the Gitlab repo. Also, I missed any responses in the Discord dev chat. :( If anyone still has access to those, please post them here.

I've had almost no time to work on DMSC lately, but I do have some updates. I figure this is the best place to put them for a few reasons.

### DMSC is a Dash (Digital Cash) masternode/network status console with audible alerts.
##
# DMSC should work on pretty much any GNU based *nix system without installing anything.
# Requirements: awk, bash (v4.2+), bc, coreutils, Dash Core, grep, iproute2, jq
# Commands used: awk, bash, bc, dash-cli, grep, jq, sleep, ss, tr
#
# Usage: Modify dashConf variable. Dash Core must be configured for RPC. Main/test-net is detected automatically. ^C to exit.
#
# Logic:
# Every loopInterval we check for a new block, waiting up to 2 seconds for each RPC and ss to return.
# Alert if no RPC data in over loopInterval * noRpcCountMax.
# Alert if no new block discovered in over loopInterval * blockStallCountMax.
# Alert if any unknown masternode related error.
# Alert if PoSe score indicates a penalty or ban.
# PoSe score is green if the situation is the same or getting worse.
# PoSe score is blue with audible alert muted when conditions are improving.
# ICN is red with audible alert when masternode is active without inbound connecting nodes.
#
# Example mainnet output:
#
# blk: 2221740 diff: 109125713. MN: Not configured. DKG: 0 12 MNC: 2046 299 ICN: 9 pool: 3 7216/300000000 mem: 39232/262144 load: 0.08 0.07 0.08 2025-02-13 06:17:44
 

Attachments

  • dmsc-v0.91-beta.zip
    7.1 KB · Views: 246
How did you lose access to your gitlab? Forgotten password, or was it taken down? Can you still log in to Discord, there were some messages directed to you, but I noticed you did not respond. I suppose this is the location of the Repo? https://gitlab.com/dash2373007/dash-masternode-status-console


Domingo Screenshot 2025-04-22 163539.png
 
Okay I guess I was wrong. I was able to login to the Gitlab just now, but Discord says my location has changed (hasn't, but is VPN), and I definitely don't have access to that email anymore. Thanks for the response/interest! :)
 
I created the Discord account with a mainstream email provider, because that's what Github required. Unfortunately, I didn't setup 2fa on Github before the mainstream email provider decided I violated some unknown policy, so that's why I ended up on Gitlab. Not sure the policy of Discord, but if I'm not able to use a temporary email provider, etc, on there, then I don't see the point in creating another account. Should be safe to send a PM on here though.
 
I created the Discord account with a mainstream email provider, because that's what Github required. Unfortunately, I didn't setup 2fa on Github before the mainstream email provider decided I violated some unknown policy, so that's why I ended up on Gitlab. Not sure the policy of Discord, but if I'm not able to use a temporary email provider, etc, on there, then I don't see the point in creating another account. Should be safe to send a PM on here though.
Hey! I believe the experiment was turning off/on some sporks - if you DM me an email address I can add you to our Slack as a guest. Devnet is still up (but being used right now, maybe for the next day or two) but I can squeeze you in after that if you'd still like to run these experiments

This was from yourself on Discord back in Jan:

Any chance I could get someone to switch IS off for 2-3 blocks, then back on, then CL off for 2-3 blocks, then back on, then IS and CL off for 2-3 blocks and back on? They're the last things I could think to add to DMSC, so it'd be nice to know the code works without too much hassle.
 
Hey! I believe the experiment was turning off/on some sporks - if you DM me an email address I can add you to our Slack as a guest. Devnet is still up (but being used right now, maybe for the next day or two) but I can squeeze you in after that if you'd still like to run these experiments

This was from yourself on Discord back in Jan:
DMSC has devnets listed as a potential future feature. I don't see any reason why it can't make it into the v1 release, but would need to make sure of any differences for full compatibility.

Not really a fan of Slack/etc, but I'm sure we can figure out something.
 
I haven't had much time to work on the code, but I have had some time to think about several more advanced early warning logics. The trickiest is probably ICN with an active MN. The idea being to detect a connect() flood without false positives and minimal overhead. This is the sort of thing that PoSe should be to able detect, and automatically ban abusive peers, etc. Lots of room for proper decentralization. :)
 
Last edited:
Hey! I believe the experiment was turning off/on some sporks - if you DM me an email address I can add you to our Slack as a guest. Devnet is still up (but being used right now, maybe for the next day or two) but I can squeeze you in after that if you'd still like to run these experiments

This was from yourself on Discord back in Jan:
What do you think about a proper stress test on testnet? It would be very helpful to have DMSC running in verbose mode with screen logging as a backup while we actually do something serious. I have a coupon for a free month of a pretty high end VPS I'd like to make the best of when it makes sense for me in terms of time, etc. I'm pretty busy with unrelated technical projects right now, but I'd like to help out as much as I can!
 
Back
Top