MNO Console
Market Maker Console
Market making is an open role; the verified tier are Dash masternode operators. This page explains how the verification tier works and what the API exposes — it is documentation, not a live console, because verification is enforced by the client software, not by a web page.
market makers were returned at build time (2026-10-13T21:16Z); the list is frozen until the next build, not a live feed.
Verification
How the verification tier works
Three checkpoints, none of which is the relay.
1. Verified counterparties are masternodes
Market making is an open role. A verified offer carries a ProTxHash, resolved against the active masternode list from Dash Coreprotx list valid. Unverified offers are permitted but labeled, and a client can filter them out, whichever relay carried them.
2. Verified payment goes to a chain-derived address
A verified market maker never supplies a receiving address. The address is read from Dash Core's own record for the verified ProTxHash — no field exists in which a verified counterparty could redirect a payment.
3. Sanctions screening is committed
The protocol will screen counterparties against the OFAC SDN list before a settlement is broadcast. A basic name-screening utility ships in the SDK; enforcement wiring is unfinished work.
Status of checkpoint 1's wiring: in progress. The verification source exists and is public; what remains is wiring the check into the client. This page will state "wired" only when it is.
API
What the API exposes
Read endpoints, each independently queryable.
- GET /v1/solvers— known market makers, keyed by ProTxHash.
- GET /v1/solvers/:proTxHash/verify— resolve one ProTxHash against the masternode list.
- GET /v1/health— liveness.
Run the market maker daemon
evomm is a Rust daemon with a text menu, a terminal dashboard, and a read-only web UI on loopback. Signing keys come from the environment or a mode-600 file — never a command-line flag.