Summary: Haveno is worth cataloging not as just another Monero marketplace or Bisq-style desktop app, but as a reference implementation for publisher-run peer-to-peer exchange networks built around Monero multisig escrow and human arbitration. The official materials make a useful architectural split explicit: the core team maintains open-source repositories, but live trading happens only on separately deployed networks whose publishers choose seed nodes, trade-fee policy, arbitrators, and binary distribution. That decomposition makes Haveno analytically useful because it separates software maintenance, network bootstrapping, dispute authority, and actual off-platform settlement into distinct control surfaces instead of flattening the whole system into a generic decentralized exchange label.
What it does:
Lets peers create offers to exchange XMR for fiat currencies or other supported crypto assets, with XMR as the base currency of the platform
Routes network communication over Tor and keeps wallet custody local to the user rather than with a central operator
Uses Monero 2-of-3 multisignature escrow so maker, taker, and arbitrator each hold one key while only two signatures are needed to settle funds
Keeps the non-XMR leg of the trade outside Haveno itself, such as bank transfer, face-to-face cash exchange, or other external payment methods
Resolves failed trades through human arbitrators who can award escrowed funds and security deposits when one party misbehaves or when the trade cannot complete normally
Exposes a distinct publisher role that releases binaries, sets initial seed nodes, provides Monero nodes, determines trade-fee collection, and appoints arbitrators for a live network
Supports a limited passphrase-protected no-deposit flow for first-time XMR buyers who do not yet have Monero for a security deposit
Key claims:
Haveno clears the corpus bar because its strongest reusable insight is not merely peer-to-peer Monero trading; it is the split between an open-source reference project and publisher-operated live networks. The core team maintains repositories, but public trading depends on third-party networks, installers, seed nodes, and operator choices.
The trade protocol is best understood as escrow and dispute-coordination middleware, not as a generalized settlement layer. Haveno handles peer discovery, Tor-routed communication, chat, and Monero-based collateral escrow, while the fiat or non-XMR payment itself happens outside the protocol.
The 2-of-3 Monero multisig design gives Haveno a different control surface from both direct atomic-swap systems and validator-custody exchanges. Traders can normally finish without the arbitrator, but the arbitrator’s third key remains the human override path when a trade breaks down.
The publisher role is a major governance and trust surface. Haveno’s own docs say publishers release public binaries, choose initial seed nodes, provide Monero nodes, determine trade fees, and appoint arbitrators. That means the practical network operator is not the same thing as the repository maintainer.
The network-creation docs make this control plane unusually concrete. Starting a public network requires hard-coding privileged public keys for alerts, arbitrators, filters, and private notifications; setting seed nodes; choosing network version and app-name namespaces; configuring trade-fee routing; and optionally standing up price nodes. That makes Haveno a good comparison point for exchange systems where decentralization still depends on a curated launch stack.
Haveno’s own repository and website stress that the official project does not itself endorse or run a live mainnet network. To trade for real, users must choose or build a third-party network. That is analytically important because it moves real authority into the publisher / network-fork layer rather than the canonical repo alone.
The no-token and no-DAO stance is also meaningful. Haveno explicitly avoids a platform token and treats Bisq’s DAO as both a privacy and complexity liability. That makes Haveno a useful contrast case for exchange systems whose governance, fee routing, or contributor incentives are entangled with a protocol token.
Haveno therefore belongs in the active corpus as a middle design point between BasicSwap’s direct atomic-swap coordination and Serai’s validator-operated foreign-asset custody. It keeps settlement peer-to-peer and non-custodial, but still recenters practical authority in seed-node operators, publishers, arbitrator appointment, and hard-coded network privileges.
Whitepaper: No canonical standalone Haveno whitepaper surfaced in this pass. The strongest primary materials were the official site, FAQ, documentation pages, repository README, trade-protocol docs, and network-deployment guides collected in ../whitepapers/haveno-primary-sources-2026-05-14.md.