Promotion & Adoption Started Jun 25, 2026 1:52 AM

[P2P Exchange - Escrow platform] XMRMatters is officially open.

21 replies - 765 views - 0 thanks - 0 tippers - 3 watchers

Jun 25, 2026 1:52 AM Last edited Jun 25, 2026 7:20 PM
#1
P2P EXCHANGE PLATFORM ESCROW SECURE NO-KYC NO-EMAIL NO-VERIFICATION NO-METADATA ONION CLEARNET DEEPWEB MONERO XMR XMRP2P SELF-HOSTED OWNED-SERVERS 24/7 AVAILABLE PRIVACYFIRST

Let me tell you about the XMRMatters

I started coding this platform completely from scratch back in May 2024, right when LocalMonero shut down. After a massive grind building the entire codebase from absolute zero, the migration is finished, the maintenance screen is down, and the platform is fully live.

You can check out the network routing and the actual interface right now.

Clearnet: https://xmrmatters.space
Tor v3 Onion: fefbn4koy23q2f2kgmtm7k64x33rtiem6dfsbn4jiltdwnuclsbq7iqd.onion

I know people are going to ask how this compares to Bisq or Haveno.
Those are excellent projects, but let's be honest, running a heavy desktop client, setting up local daemons, and managing complex multi-sig workflows has a massive learning curve. When a regular, non-technical user faces that kind of technical barrier, they usually default back to centralized KYC exchanges out of frustration.

XMRMatters is built specifically for end users who aren't technical and just need a straightforward, simple entry point without the friction.

Stagenet Accounts & Live Inspection
We ran the platform on stagenet for a full month to thoroughly stress-test the pipeline and wallet mechanics under load. If you participated during that beta phase, your user profile has been fully transferred over to the mainnet. However, all stagenet offers and past trade histories have been completely wiped, since that operational data isn't stored together with your user account details.

If you didn't test it out and want to look at the interface without registering,
I’ve left a pre-configured test account active so anyone can verify the workflow:

Username: Test (Case-sensitive)
Password: T3st1ng.12345

Upcoming Maintenance Notice
Please note that tomorrow at 14:00 (CET+2 timezone), the server will be temporarily disabled for a quick scheduled update. To ensure no transactions are caught mid-flight during the restart, there will be a complete withdrawal and deposit halt starting exactly 1 hour prior (at 13:00 CET+2).
Plan your active trades accordingly everything will be back online shortly after the patch settles.

How the Interface Works
The defining mechanic of the interface is that buttons function as literal commands. There are no abstract menus or multi-layered workflows to navigate. Every primary action, like funding escrow, marking a payment as sent, or releasing the XMR, is a direct instruction executed straight against the backend state machine.

We don't store your data because what doesn't exist can't be leaked or compromised. Traditional platforms keep a permanent history linking your account to every IP address, login attempt, and device fingerprint. XMRMatters completely refuses to log or track your IP or device signatures.
Because of this, standard tracking features like "logged in from a new device" warnings are structurally impossible here. The moment a trade is finalized or cancelled, automated database triggers execute to clear out the active trade logs and temporary metadata from the disk.

Core Backend Safety
Behind the frontend, the focus is entirely on handling real operational risks:

Escrow Safety: To eliminate double-allocation or database race conditions when the server is under heavy matching load, the escrow pipeline utilizes strict PostgreSQL row-level locks and transaction isolation. If any part of a trade state update fails, the entire sequence rolls back instantly.

Direct RPC Integration: The backend talks directly to the official Monero daemon and wallet RPC endpoints. I didn't use any high-level, third-party payment processing wrappers or middleman APIs, which keeps the execution pipeline clear of upstream software supply chain vulnerabilities.

Tor Isolation: Frontend API calls strictly match the browser origin. If you access the site via the Onion address, your traffic stays entirely within the Tor network with no clearnet leakage.

Mobile-View and What's Next
The interface is currently English-only, but I have already added a fully responsive mobile-view for both clearnet and Tor browsers so you can manage trades smoothly on the go.

My immediate priorities right now are actively polishing the native Android application for release, setting up a completely script-free No-JS web mode next month, and integrating language packages for Dutch, German, French, Russian, and Bosnian/Serbian/Croatian.

Why XMRMatters Exists
Financial privacy is a structural necessity, not a supplementary feature.
Legacy financial systems are fundamentally engineered for absolute visibility, pervasive telemetry, and centralized control over individual economic choices. Without functional, independent alternatives designed to run counter to that setup, submission to total financial surveillance becomes the default state. XMRMatters exists to serve as a clean alternative, providing a practical gateway out of that loop without requiring specialized technical expertise to safely execute a peer-to-peer trade.

Drop the test credentials into the login screen and check it out. I am highly interested in your feedback, suggestions, and feature requests. Let me know your thoughts on the layout, or if there are specific adjustments or tools you need to make day-to-day trading easier for you.

The rollout version has some visual issues, the functionality is the priority.

Signature

— XMRMatters Development Team

0 thanks - 0 tippers - 3 watchers

Replies

Page 3 of 3 - 21 total
Jun 26, 2026 12:40 AM
#22

@avarice I'm not using LLM slop to write my thoughts.
I only use Grammarly to fix my broken English and typos so people can actually understand me.
The vision and the text are 100% mine, you're talking to a real human who spent two years building this.

About the chat, yeah you hit the nail on the head.
The risk of someone recording 24/7 or users leaking their own info is very real.
But for the dispute trap, we can actually solve that: during a dispute, the platform can display both users' public keys to each other, and include the platform’s own PGP key.
That way, the messages are encrypted for the disputing parties and the admin to read.

It’s still a double-edged sword for general opsec, but technically, that fixes the escrow issue.
Appreciate you keeping it real with me.

If you encounter anything else do suggest I appeciate it, all of this previously mentioned is added to the notepad of future plans/implementations.

Signature

— XMRMatters Development Team

1 thanks - avarice - 0 tippers

Post A Reply

You must be logged in to reply. Login or register.