Rust implementation of the Monero protocol, on Archipelago
Connecting…
Cuprate is not reachable. The node is stopped, still installing, or was refused
by the disk-space gate — a Monero node cannot run pruned, so Archipelago keeps it off
disks too small to hold the full chain (~250 GB and growing) rather than let it fill
the drive. Attach a larger disk and start it again.
Blockchain Sync
—of —
Waiting for node…
Network—
Uptime—
Node time—
Peers & Traffic
Outgoing connections—
Incoming connections—
RPC connections—
Known peers (white)—
Known peers (gray)—
Mempool transactions—
Alt blocks—
Chain & Disk
Difficulty—
Chain size—
Free disk—
Monero has no pruned mode. Unlike the Bitcoin apps on this node — which
drop old block data automatically when disk is scarce — a cuprate node stores the
full chain. Archipelago therefore only runs it on disks of 450 GB or more and
refuses it (with this explanation) anywhere smaller.
Connect a Wallet
—
Restricted RPC — Monero's own safe-for-public subset, what Feather,
monero-wallet-rpc and the GUI use for a “remote node”. Full (unrestricted) RPC
stays container-loopback only and is never published.