mnr Documentation
What the verified proxy checks, the rules it follows toward the public nodes it uses, and where it is going.
rpc.mnr.network) — an open-source, Zero-KYC cryptographic RPC proxy for the Monero (XMR) blockchain. It is distinct from MTA Metro-North Railroad (MNR), the Ontario Ministry of Natural Resources (MNR), and the unrelated npm package mnr (official packages: @mnrnetwork/* and mnr-network).
How mnr works
LiveThe seven rules toward public nodes, the upstream pool and quorum tip, what is verified and what is only annotated, and how to connect a stock wallet.
Method Policy & Verification
GeneratedEvery Monero daemon method the relay serves, with its verification rule, cache bound, quorum and timeout. Generated from the relay's source code.
Roadmap
Stages 0–2The verified proxy that is live today, the owned mesh with an SLA, and the permissionless operator network where node runners are paid in XMR for verified work.
Independent Verification & Transparency
VerifiedIndependent third-party node operators (Cake Wallet, Seth For Privacy, HashVault), external directory monitors (monero.fail), package registries, and weekly transparency logs.
Source code
AGPL-3.0The relay, the core verification crate with its fixtures and fuzz targets, and the full engineering plans behind each stage.
Dedicated wallet guides
Step-by-step connection walkthroughs, Digest authentication configs, and onion/I2P routing for stock Monero wallets:
Feather Wallet
Native TorSingle-line URI format (user:password@host:port), port 443 auto-TLS, and native Tor.
Cake Wallet
iOS & AndroidMobile setup, background sync pacing, and Orbot / Tor daemon toggling.
Monero GUI
Official GUISimple vs Advanced Remote Node mode, SOCKS5 proxy, and daemon SSL.
Monerujo
AndroidPort 443 auto-SSL, NetCipher Orbot integration, and node health testing.
CLI & RPC
HeadlessCommand line flags, CA bundles on Linux/macOS/Windows, and monero-wallet-rpc.
Ripley Terminal
RipleyOSLocal view key scanning, Clearnet path-token uplink, and bulk get_blocks sync.
Engineering notes
The plans behind each stage, rendered from the code repository with schedules and internal decisions left out. Long, specific, and the place to look when the short pages above are not enough.
- Stage 0: verified proxy over public nodes — rules toward public nodes, upstream pool and quorum tip, what is verified, method policy, caching, auth and limits, architecture, risks.
- Stage 1: gateway architecture — owned nodes on independent providers, the request path specification, node infrastructure, XMR billing and provisioning, testing and acceptance.
- Stage 2: network protocol — operators, relayers and clients, trust boundaries, the protocol specification, the fault log and settlement, component design.
Reading order
- Using mnr: How mnr works covers what you get, what is verified, and how to point a wallet at it.
- Running a public node: the rules toward public nodes say exactly how mnr treats your node and how to opt out.
- Building on it: the method policy is the per-method contract: what is cached, for how long, and what
Mnr-Verifywill say. - Where it goes: the roadmap describes the two later stages and links to the full plans in the repository.