Desk process
Manual RFQ first. Marketplace mechanics later.
The correct first product is not a full exchange. It is a high-signal deal desk that captures real buy/sell demand, qualifies counterparties, and turns repeated patterns into software only after demand proves itself.
Phase 1: structured lead capture.
Every inbound request becomes structured data: side, size, timing, quote basis, entity type, jurisdiction, proof requirements, and settlement preference. Manual notes matter because early market structure is still forming. The desk should learn whether demand comes from buyers seeking allocation, miners needing liquidity, infrastructure operators recycling compute revenue, or holders seeking a private exit.
RFQ intake
Buyer, seller, and mining-supply forms are routed into the same desk queue with clear side, urgency, notional, and source labels.
Counterparty screen
Requests with no size, no settlement path, no jurisdiction context, or vague “best price?” language stay lower priority.
Document terms
Quotes need expiry, source, conditions, evidence rung, and settlement assumptions before they are treated as actionable.
Matching rules favor quote quality over speed.
The desk should not optimize for the fastest intro. It should optimize for clean intent, compatible settlement preferences, and enough evidence to avoid preventable disputes. That means refusing low-quality requests, labeling uncertainty, and avoiding claims that BTXOTC cannot verify.
- Do not introduce parties when either side refuses to define price basis or settlement route.
- Do not call a quote firm unless size, expiry, conditions, and counterparty requirements are explicit.
- Do not publish private deal details as market price without consent and enough context.
- Do escalate larger deals toward professional legal, tax, compliance, and escrow advice.
Automation comes after repeated manual patterns.
Once enough qualified RFQs repeat, the site can add authenticated dashboards, quote books, admin review tools, and analytics. Until then, a manual desk is safer and more honest than shipping fake liquidity. Software should encode proven workflow: intake validation, queue triage, quote labeling, counterparty notes, audit logs, and post-settlement evidence categories. For the exact search intent around pools and depth, the BTX liquidity pools guide explains how to label OTC pools, future AMMs, model prices, and executable depth without overstating market maturity.
Evidence base.
Protocol references come from btx.dev and official documentation: MatMul proof-of-work, post-quantum signature algorithms, mining RPCs, service challenges, shielded settlement, ASERT difficulty adjustment, 90-second target block time, and 21,000,000 max supply. OTC and marketplace commentary is independent BTXOTC analysis. The distinction is visible because liquidity claims should not be confused with protocol claims.
Disclosure: BTXOTC is independent lead intake and research. It is not the official BTX project, not an exchange, not a broker-dealer, not a custodian, and not an escrow service.