Crypto Masternode MonitorMasternode monitoring

Support

Last updated: September 7, 2026

One contact address, no ticket system, no account to create. Write to guitapp.dev@proton.me and you will get an answer from the person who wrote the app.

User guide →

Adding a node, reading the dashboard, alerts, backup and restore.

RPC endpoints →

Configuring a data source, running your own node, TLS, troubleshooting.

FAQ →

The questions that come up most often, answered in a paragraph each.

Networks →

Which source each network uses, and what the app can show for it.

Before you write

Three checks answer most messages faster than we can:

  1. Is the network configured? Settings → Networks shows each network's current source, or tells you it has none.
  2. What does "Test connection" say? It reports the exact error from the endpoint, which is usually the whole answer.
  3. Is it a background delay? Open the app: if everything refreshes correctly, the data source is fine and the delay came from the operating system.

Reporting a problem

Include what you can of the following. Each line saves a round trip:

Never send us a private key, an RPC password or a seed phrase. We never need them, and no legitimate support request requires one. Public identifiers, error messages and version numbers are enough. If you have already sent a secret to anyone, treat it as compromised and rotate it.

Asking for a network

A missing network is a request, not a limit: the app was built to take any masternode blockchain. Tell us which one, and — this is the part that decides the effort — whether it has a public API listing its masternodes, or whether users would supply their own node.

Suggestions

Feature requests are welcome at the same address. So is the opposite: if something in the app is confusing, saying so is useful. The screens are deliberately sparse, and that only works if the right things are on them.

Legal documents