mnr

Verified RPC proxy for Monero wallets.
One address, every block, tx and header checked against several nodes.

Free tokens, no account, no email. Public beta.

[mnr @mnr_network]

mnr is a verified rpc proxy over public monero nodes.

single endpoint. cryptographic verification on blocks, txs, and headers across multiple upstream nodes. no account, no tracking. oss.

web: https://t.co/rXsabCPefH
free token: https://t.co/NOOvKt98VT

[mnr @mnr_network]

they were right. we were behind.

rolled out relay 0.1.18: near the tip, a node naming a different block than our chain is served marked unverified (Mnr-Verify: none), not counted as a lie. ten blocks down it still is. the six faults are off the log.

https://t.co/umXAtEPKYj

[mnr @mnr_network]

on 11 sep a one-block reorg replaced block 3,760,020. our header chain held the losing block for at least 24 seconds after nodes moved on.

in that window three community nodes served the right block and we marked them faulty. two requests for it got an error instead.

[mnr @mnr_network]

daily mnr relay pulse (2026-09-12):
- 119,149 answers verified in 24h
- quorum height 3,760,487 (15 of 15 nodes on tip)
- all 15 nodes healthy on tip

https://t.co/RnEV0DGQqq

[mnr @mnr_network]

570,824 answers checked against consensus all-time.

the owned node took 31% of today's work units, keeping heavy sync streams off community nodes.

every response carries Mnr-Verify saying what was checked.

https://t.co/3xMPq8FWha

[mnr @mnr_network]

daily mnr relay pulse (2026-09-12):
- 119,149 answers verified in 24h
- quorum height 3,760,487 (15 of 15 nodes on tip)
- all 15 nodes healthy on tip

https://t.co/RnEV0DGQqq

[mnr @mnr_network]

tested and working on feather, cake wallet, and monero-wallet-cli. clearnet, tor (.onion), and i2p supported.

https://t.co/2fp1Qagxrq

[mnr @mnr_network]

mnr works with stock wallets using standard daemon rpc settings. no forks or plugins.

address: https://t.co/YLqs9aZFkP (ssl on)
username: <your-token>
password: x

https://t.co/2fp1Qagxrq

[mnr @mnr_network]

wallets authenticate using http digest, which normally requires the server to store passwords in plain text.

mnr stores only 256-bit token hashes. it reads the token from the username field and ignores the password.

[mnr @mnr_network]

451,675 answers checked against consensus all-time.

the owned node took 33% of today's work units, keeping heavy sync streams off community nodes.

every response carries Mnr-Verify saying what was checked.

https://t.co/3xMPq8FWha

[mnr @mnr_network]

daily mnr relay pulse (2026-09-11):
- 108,704 answers verified in 24h
- quorum height 3,759,787 (14 of 15 nodes on tip)
- 1 node held (cryptostorm: http 502)

https://t.co/RnEV0DGQqq

[mnr @mnr_network]

nothing within 10 blocks of the tip is ever cached, so a chain reorg costs you no stale data.

the method policy is generated directly from relay source code:

https://t.co/3xMPq8ForC

[mnr @mnr_network]

every response from https://t.co/xJQ6bkEWEY carries an Mnr-Verify header.

we promise no uptime. the promise is narrower: we tell you exactly what was verified before your wallet saw it.

https://t.co/3xMPq8ForC

[mnr @mnr_network]

what gets verified:
- block headers: hash recomputed from blob, matched to header chain
- /get_transactions: blobs hashed/matched to txids
- tip height & info: majority agreement of >= 3 independent upstreams

if quorum fails, it enters degraded mode and states it in the header.

[mnr @mnr_network]

342,971 answers checked against consensus all-time.

the owned node took 33% of today's work units, keeping heavy sync streams off community nodes.

every response carries Mnr-Verify saying what was checked.

https://t.co/3xMPq8FWha

[mnr @mnr_network]

daily mnr relay pulse (2026-09-10):
- 105,198 answers verified in 24h
- quorum height 3,759,107 (14 of 15 nodes on tip)
- 1 node held (own-1: request failed, wg down but the entire https://t.co/xJQ6bkFuuw keeps up and running exactly like designed)

https://t.co/RnEV0DGQqq

[mnr @mnr_network]

When setting up a remote node in wallets, users often assume "trusted daemon" as: "I know this operator," or "I want a reliable connection.", believing it enables optimal performance or unlocks features.

you're wrong, learn why and how.

https://t.co/K2jreq0yFf

[mnr @mnr_network]

mnr is verified working by running a from-scratch wallet sync on live https://t.co/xJQ6bkFuuw:
restore height 1 → tip (~3.76M blocks), Pro token, wallet cli.

done in ~28.7h wall time.

Full tip syncs → Pro (more streams).
Light RPC → free is fine.

[mnr @mnr_network]

237,773 answers checked against consensus all-time.

the owned node took 36% of today's work units, keeping heavy sync streams off community nodes.

every response carries Mnr-Verify saying what was checked.

https://t.co/3xMPq8FWha

[mnr @mnr_network]

daily mnr relay pulse:
- 83,787 answers verified in 24h
- quorum height 3,758,349 (14 of 15 nodes on tip)
- 1 node held (cryptostorm: http 502)

https://t.co/RnEV0DGQqq

[mnr @mnr_network]

Point monero-wallet-cli at mnr:

monero-wallet-cli \
--daemon-address https://t.co/YLqs9b0dan \
--daemon-login <token>:x \
--daemon-ssl enabled

Free token: https://t.co/dSiJVRp296

Also works with GUI / Feather / Cake / Monerujo (login = token, password = x).

[mnr @mnr_network]

upstream nodes never receive your ip, token, or headers. only the raw rpc body reaches them, from the relay's ip.

the honest advice: run your own full node if you can. if you can't, verify what you get:

https://t.co/3wkBH8q68g

[mnr @mnr_network]

when you point a monero wallet at a public remote node, it can record 3 things:

1. your ip
2. your sync pattern
3. the specific outputs and key images you request (like decoys via /get_outs)

here is how mnr handles that split in code:

https://t.co/y8iPX7IHXB

[mnr @mnr_network]

queries that reveal what a wallet is inspecting (/get_outs, /is_key_image_spent, /get_transactions) are routed to our own node first and always.

third-party public nodes in our pool do not see which outputs or key images you asked about.