Run the whole stack yourself.
One community app store added to your Umbrel node, five Monero apps that run on your own hardware, and a beta chain you can join. Nothing here is a service; nothing here holds your keys.
An Umbrel community app store is a third-party catalogue pointed at from your own Umbrel node — not a hosted service, not a login, a directory of apps that install onto hardware you already own. Everything in it runs on your box, reads what your box can see, and stays up exactly as long as you keep it running.
The official Monero app is the one prerequisite every app here shares. MoneroSpace and SuperAtomic ask for more: both additionally need Bitcoin and Electrs installed first, since each reads chain state that neither the Monero node nor the store itself provides.
SuperAtomic's swap engine is a GPLv3 fork of eigenwallet/core, and the complete corresponding source is published at github.com/brainchainz/eigenwallet-core. That is real licence compliance, not a footnote, and it is worth naming in public.
P2Pool is a peer-to-peer mining pool: instead of a company running a server that collects everyone's work and pays out from its own wallet, the participants run the pool between them and the chain itself pays each miner directly. There is no operator to trust, no account, and no minimum payout held on your behalf.
XMRig is the miner that does the actual hashing. Pairing the two on one box gives you a pool and a miner you own, and the app opens a port so other machines on your LAN — or across a Tailscale network — can point their own miners at it.
Why it mattersPool centralisation is the standing critique of proof-of-work: a handful of operators end up choosing which transactions get mined. A pool you host, mining to a wallet you hold, removes you from that count entirely.
A view-only wallet holds the key that lets it RECOGNISE incoming payments and not the key that lets it move them. That is what makes a till safe to put on a counter: it can tell you a payment arrived and for how much, and it cannot spend a thing.
Running it yourself means the payment goes from the customer to your wallet with no processor in between — nobody to freeze it, take a percentage, or file a report about it.
Why it mattersEvery hosted payment processor is a party that can be compelled to hand over a record of who paid you and when. A till that only ever holds a view key produces no such record for anyone else to keep.
Where its interface design comes from is an open question we have put to its maintainer. Until that is answered this site names the project, links the repo, and claims nothing further either way.
This is the app the rest of this page is about: a node that joins the FCMP++ beta chain rather than mainnet, so the proof system due at the next hard fork can be run under load before anyone's real money depends on it.
The wallet lab is the other half — somewhere to build, send and inspect transactions against that chain, which is how a wallet author finds out their assumptions broke before their users do.
Why it mattersA beta chain is only as useful as the number of independent nodes on it. One node on somebody else's hardware measures one machine; a node on yours adds a data point nobody had, and Tor routing means adding it does not also publish where you are.
An atomic swap trades XMR for BTC directly between two people, with the protocol itself guaranteeing that either both halves happen or neither does. There is no exchange holding both sides mid-trade, which means there is no moment at which somebody else has your coins.
Its swap engine is a GPLv3 fork of eigenwallet/core, and the complete corresponding source is published at github.com/brainchainz/eigenwallet-core — real licence compliance, worth naming in public.
Why it mattersThe identity check happens at the exchange, not on the chain. A swap with no exchange in the middle is the one acquisition path that never creates a file linking your name to an amount.
Order matters. The store itself installs nothing on its own — it is a catalogue your node reads — so the Monero app goes on first, and the two apps that read Bitcoin chain state need Bitcoin and Electrs before they will start.
- Open your Umbrel dashboard
- App Store → Community App Stores
- Add → paste: https://github.com/brainchainz/Monero-Superbrain
- Install from the Brainchainz store
One specific app, and it is a mainnet node. Installing it does not put you on the beta chain — Superstress brings its own daemon for that. Getting this step wrong is the one mistake that costs you an afternoon.
xmrig -o umbrel.local:8888 -u "Rig Name" -p x“superstress is self-hosted, the monero node add[on] exposes 18081 p2p 18083 zmq-pub (for p2pool) 18089 (restricted) and is reachable from lan/tor/tailscale”
— the Superstress maintainer, asked directly
Those are the Monero node addon’s ports — the mainnet prerequisite above — and not Superstress’s own. Superstress runs its own monerod, and its ports are not documented anywhere this site can cite. Read yours off your own app’s configuration rather than copying them: upstream publishes them as variables rather than fixed numbers, and mainnet convention puts peer-to-peer traffic on 18080 with 18081 the unrestricted RPC — so treat the line above as one operator describing his own box, not as a config to paste.
The three routes he names are the three you would expect from hardware you own: the LAN for a machine in the same building, Tailscale for one that is not, and Tor for reaching it without either end publishing where it is. None of the three is a service, and all three terminate on your box — which is also the reason this page cannot show you what they return. See below.
A chain that exists to be broken.
A stressnet is a copy of the network that carries no real money and is deliberately abused. It runs the same software as the real chain and is fed traffic no ordinary day would produce — floods of transactions, blocks pushed to their size limits, proofs verified faster than any wallet would ask. The point is to find the breaking point somewhere it costs nothing.
It runs BEFORE a hard fork because a hard fork is not reversible. Once the network adopts new consensus rules, every node either follows them or leaves; there is no staging environment and no rollback. So the new rules get their punishment in advance, on a chain where a crash is a bug report rather than an outage.
What is being punished here is FCMP++ — full-chain membership proofs — which replaces the ring signature with a proof over the whole chain. It is scheduled for Q3 2026 · fork v17, and that figure is read from the protocol card on the roadmap rather than restated here, so the two can never disagree.
The wallet lab is the other half of the Superstress app. A consensus change breaks wallets as readily as nodes, and a wallet author needs somewhere to build a transaction under the new rules and watch what happens to it. Tor routing matters for the same reason it matters on mainnet: a node announces itself to its peers, and on a small beta network with few participants the set of addresses is small enough to be worth writing down. Routing through Tor means joining the experiment does not also publish where you are.
What this page does NOT tell you: this chain's own parameters — whether it is a separate network or a fork of an existing testnet, its genesis, its block target, its difficulty — are not documented anywhere we can cite. We have asked. Until there is an answer, the honest version is that the node software is public and the chain's specification is not.
What you have at the end.
An Umbrel node running the mainnet Monero app, and beside it a Superstress node with its own daemon on the FCMP++ beta chain — reachable from your LAN, over Tailscale, or through Tor, because it is yours. MoneroSpace points at that chain from the same app store. What you get is not a dashboard someone else operates: it is a participant on a small network that is worth more the more independent participants it has.
“superstress has its own monerod”
— the Superstress maintainer, asked directly
“Its the FCMP++ stressnet/testnet”
— the Superstress maintainer, asked directly
So the question this section used to hold space for has an answer, and the answer is no. There is no public endpoint for the beta chain, none is planned, and the chain is self-hosted by design rather than by delay. Nothing is being waited for here.
That is the better answer, not a smaller one. A public endpoint would have been one machine everybody reads — a party to trust and a single point of failure, on a chain whose entire purpose is to be attacked. Self-hosted-only means every participant reads their own node and no one operator can misreport the network to everyone at once. It is the argument this site makes about mainnet, applied to the chain that tests it.
Why this page will never show you a live beta-chain panel: its content-security policy is connect-src ‘self’, so the browser is not permitted to contact any origin but this one — which is what keeps the site safe to read over Tor, and is not a setting we would relax for a chart. And your node sits on your LAN, your Tailnet, or an onion address; none of those are ours to reach, and proxying them through this site would put us between you and your own machine. There is no path from here to your beta chain, by design rather than by omission.
And if beta-chain data ever does land on this site, it inherits a rule set down here before there was anything to apply it to: it ships behind a persistent BETANET · NOT MAINNET · TEST FUNDS ONLY banner, in an accent used nowhere else, carrying its own provenance badge — never sharing a colour, a badge or a panel with mainnet numbers.
A community FCMP++ stress-test chain running on Umbrel nodes, packaged as Umbrel apps in brainchainz/Monero-Superbrain alongside MoneroSpace, a visual mempool for the beta chain.