Monero public node
Nodely runs public Monero nodes for wallets, apps and developers. No account, no keys.
Endpoints
Section titled “Endpoints”| Network | Host | Ports | Mode |
|---|---|---|---|
| Monero mainnet | xmr.nodely.dev |
18089, 18081 |
restricted RPC |
| Monero stagenet | xmr.nodely.dev |
38089, 38081 |
restricted RPC |
monero.nodely.devis an alias ofxmr.nodely.dev.- TLS is optional: every port accepts both HTTPS and plain HTTP. Wallets detect TLS automatically.
- Requests are routed to the closest region (Europe or US West).
- The node runs in restricted mode, so admin methods are disabled. Wallet sync,
/json_rpcand the other daemon endpoints (/get_info,/get_transactions,/send_raw_transaction, …) work as on any public node. - CORS is open, so browser apps can call the node directly.
Connect a wallet
Section titled “Connect a wallet”monero-wallet-cli --daemon-address xmr.nodely.dev:18089For stagenet add --stagenet and use port 38089.
- Go to Settings → Network → Node.
- Uncheck Let Feather manage this list.
- Click Add custom node(s) and enter
xmr.nodely.dev:18089.
For stagenet, start Feather with feather --stagenet and use port 38089.
Go to Settings → Node → Remote node, click Add remote node and enter address xmr.nodely.dev, port 18089.
monero-wallet-rpc --daemon-address xmr.nodely.dev:18089 \ --rpc-bind-port 18083 --wallet-dir ./wallets \ --rpc-login user:change-meDaemon RPC
Section titled “Daemon RPC”curl https://xmr.nodely.dev:18089/get_info
curl https://xmr.nodely.dev:18089/json_rpc \ -d '{"jsonrpc":"2.0","id":0,"method":"get_block_count"}'Libraries such as monero-ts and monero-python take the same URL: https://xmr.nodely.dev:18089.
Related services
Section titled “Related services”- Block explorer for mainnet and stagenet
- Stagenet faucet to get test coins
Privacy & fair use
Section titled “Privacy & fair use”- Request logs keep a truncated, hashed client IP, the ASN, the user agent and the RPC method, for capacity planning and abuse handling.
- Please do not hammer the node. Heavy or commercial workloads should talk to us about dedicated or whitelabel endpoints.