node.community.rino.io

RINO has quietly run public Monero nodes for years, and because its own multisig product depends on them, its uptime incentives are unusually well-aligned with yours.

Background node.community.rino.io is operated by RINO, the team behind the RINO enterprise/multisig Monero wallet. Long-standing and restricted-RPC, it exposes clearnet, Tor, and I2P endpoints plus ZeroMQ — broader transport coverage than most public nodes offer.

What you trust A remote node can see your IP and the timing of your wallet's broadcasts/queries — never your keys, balances, or transaction details (Monero's privacy holds at the node level). RINO is among the more transparent operators, and critically its own multisig-coordination service runs on the same node, so the incentive to keep it up and honest is structural rather than mere goodwill. Route over Tor or I2P to blunt the IP/metadata exposure.

Operational specs Restricted-RPC; clearnet + Tor + I2P endpoints; ZeroMQ + RPC; standard wallet flows including multisig. The multi-transport reach makes it a flexible fit for privacy-routed clients.

Philosophy Dependable shared infrastructure from an operator whose business literally depends on it staying reliable — alignment by design, not by promise.

Grade rationale Grade A. Transparent, long-running, multi-transport (Tor + I2P), with structurally-aligned uptime. Graded as a remote node, with the standing caveat that any remote node is a metadata trade-off versus your own.

Useful when You want a long-proven public node reachable over Tor + I2P; you value an operator with genuine skin in the game; you run multisig; you need a reliable fallback node.

Caveats A remote node sees your IP + broadcast timing — connect over Tor/I2P, and treat your own node as the more-private end goal. You're trusting RINO's no-log posture, which is reputable but unverifiable from outside. Single operator: keep a backup node configured. For a privacy-first setup, point a Tor- or I2P-capable wallet at the matching endpoint rather than the clearnet one — the multi-transport coverage is the whole reason to prefer this node over a clearnet-only default.