Configuring RPC endpoints

Last updated: September 7, 2026

The app has no backend. It queries the networks directly, which means each network needs a data source: either an official public API, or the RPC address of a node you provide. This page explains how to set one up, and what to do when it does not answer.

Setting an endpoint

1. Settings (⚙ at the top of the home screen) → Networks.
2. Pick the network. Its subtitle already tells you which source it is using — or that it is not configured.
3. Tap Configure the RPC node / Change endpoint and enter the URL. It must start with http:// or https://.
4. If the node requires authentication, fill in the username and password in the same dialog.
5. Tap Test connection. The app fetches the chain height and shows either OK or the exact error.
6. Reset restores the default: the official URL for networks that have one, an empty field for the others.

Where credentials live

The RPC username and password are written to the Android Keystore / iOS Keychain, with one entry per network. They never appear in the app's settings, in the backup file, in the logs or in the app bundle.

• The password is never displayed again. Reopening the dialog and leaving the field empty keeps the stored credentials.
• Clear credentials removes them from secure storage.
• An exported backup contains RPC URLs only — never a password, never a username.

Running your own node

These networks are Bitcoin or Dash forks: RPC is configured in the daemon's configuration file. The useful keys are the same everywhere.

server=1
rpcuser=<username>
rpcpassword=<long random password>
rpcbind=0.0.0.0                  # listen on the network, not just localhost
rpcallowip=<trusted-ip>/32       # restrict who may call the RPC
# rpcport=...                    # keep the network default unless you must change it

Daemon, configuration file, default port and the method the app calls, per network:

Networks absent from this table — Cosanta, Neoxa and Flux — are read through a public explorer or API rather than an RPC node. There is no RPC port to open for them; you only ever change a URL.

HTTPS and reverse proxy

A daemon exposes plain HTTP, and the app accepts it on all fourteen networks: no masternode daemon serves TLS, and the node you watch is often reachable on your local network only, where a publicly trusted certificate makes no sense. Over HTTP, though, everything travels in the clear — the daemon's answers, and above all the RPC password if there is one. For anything but a trusted link, put a TLS reverse proxy in front of the RPC — Caddy, Nginx or Traefik — and give the app the proxy's URL. With Caddy the whole thing is two lines and the certificate is automatic:

rpc.example.com {
    reverse_proxy 127.0.0.1:9998
}

You can also let the proxy carry the Basic authentication instead of the daemon. Either way, the app sends the credentials over TLS, never in the clear.

Network specifics

Networks that work out of the box

Beldex, Firo, Cosanta and Neoxa ship with an official public source and need no configuration at all. Two things are still worth knowing:

• Beldex is the only network where you can stack several endpoints. They are tried in order, so a second URL is an automatic failover.
• Firo offers two modes. The public explorer works immediately but does not expose the numeric PoSe score, so a penalised node still looks healthy until it is banned. Your own firod exposes it — and falls back to the public explorer if your node goes down.

Networks that need your own node

PIVX, Dash, Syscoin, Divi, Raptoreum, SmartCash, SwiftCash, BitCore, Flux and Terracoin start out unconfigured. That is a deliberate choice, not an oversight, and there are two distinct reasons behind it. For the first eight, no official public endpoint exposes the masternode list, and we would rather leave the field empty than route your traffic through a commercial gateway you never picked. Flux and Terracoin are the other case: an official source exists and answers perfectly, but its operator does not allow an app to query it — both were removed from the defaults on 2026-08-25.

• Authentication is required on all of them but PIVX, where it is optional — a public node may not ask for it, your own pivxd will.
• Gateways that need an API key (NOWNodes, GetBlock and similar) will not work: the app sends no api-key header. Keyless public gateways may work, provided they allow the masternode listing methods — many only serve block queries.
• Their explorers are down or deliberately closed. If you know a trustworthy public endpoint, you can simply paste it in.
• Flux needs no credentials — its API is public and read-only — and every FluxNode serves that same API on port 16127, over plain HTTP: enter http://your-ip:16127. The two neighbouring ports are dead ends — 16126 is the web interface, 16128 the same API behind a self-signed certificate the phone refuses.

One network worth a warning

Security

• Never expose an unauthenticated RPC to the open internet. An open RPC is a node — and sometimes a wallet — at the mercy of whoever finds it. Use rpcallowip, a firewall, a VPN or an authenticated reverse proxy.
• Use a long random password. The RPC is a machine interface; nobody has to type it twice.
• Never enter a private key in the add-node field. Monitoring only needs public data. On several networks the app rejects a private key from its format alone, before any request leaves the device.
• Credentials stay on the device, in the system keystore — never in the settings, never in a backup file, never in a log.

Troubleshooting

Still stuck? Send us the network, the exact error shown by Test connection and the daemon version — see support. Never send credentials.