mnr.network

A remote node that proves it isn't lying to you. mnr.network is a *verified RPC network*: you point a wallet, explorer, or app at it, and instead of trusting one anonymous remote node, mnr fans your call out across many public Monero nodes, recomputes the hashes, links the headers, and compares consensus state, then marks each answer verified or not. A wrong answer gets the offending upstream *ejected for 24h and logged publicly*. That closes the oldest trust hole in using someone else's node — you no longer take the response on faith.

Privacy posture is unusually clean. *"A token is the whole relationship — free, or paid in XMR. No email, no KYC, and no request logs."* The token rides in the URL path and they state they never log the path or your address. Tor is first-class (Orbot/NetCipher, SOCKS5, port-443 auto-SSL). The usual remote-node caveat still applies — you are routing your view of the chain through a third party, and no-log is a policy claim you can't cryptographically prove — but the verification layer plus XMR-payable, no-KYC access put it well ahead of a bare public node.

A good citizen toward the node network. mnr rate-limits *itself* against the public nodes it uses (≤5 req/s, ≤2 wallet-sync streams each), identifies every request, sends overflow to its own node, and lets any operator opt out via a `/.well-known/mnr-optout` file with removal in 24h. Every upstream and every caught wrong answer is listed publicly. That ethic is rare in this corner.

Full disclosure — this is first-party. We built and operate mnr, so we flag it plainly rather than dress it up as independent, and grade it by the same rubric as everything else. Our own block explorer (explorer.xmr.club) runs on it in production — reliable, sub-second-to-1.5s calls, 60 parallel requests without throttling — which is where the reliability read comes from. It lands at B, not A, purely on maturity: it's brand-new and still in beta (no track record, protocol at 'Stage 2'). A clean GA exit plus tenure moves it up.