Crypto market making advisory: from liquidity goals to oversight.

The issuer's decision is not simply whether to hire a market maker. Execution alone doesn't define an effective liquidity arrangement. The project also needs to determine what it wants to achieve, which venues matter, who holds decision-making authority, and how performance will be reviewed. Advisory provides structure for those decisions by connecting the issuer's objectives to a suitable counterparty and a mandate that can be assessed over time.

The parties have distinct roles. The issuer sets project priorities, supplies relevant token and venue information, and retains decisions about its market objectives. The advisor aligns those objectives with the project context, supports counterparty matching, and supervises the liquidity arrangement and KPI framework. The market maker carries out the agreed quoting or trading activity under the mandate. The exchange provides the venue and its trading environment.

This division creates accountability, not control over the market. Advisory can help define objectives and establish how the arrangement will be monitored. It cannot dictate broader market conditions, guarantee trading demand, or assure a particular token price, volume, or liquidity outcome. The mandate should specify each party's responsibilities and what remains outside its control.

Execution is the market maker's activity, such as quoting bids and offers or trading within the agreed arrangement. Advisory is issuer-side coordination. These functions are related but not interchangeable, and because responsibilities depend on the written mandate and venue arrangements, the scope should be defined before activity begins.

Not every token project needs an external market maker. Advisory is most relevant when a project has a defined liquidity objective but needs structured support to match, establish, or supervise the arrangement — during launch planning, or once an arrangement is active and the KPIs need to provide useful evidence.

A mandate should start with the issuer's operating reality, not a generic promise of liquidity. The token's stage, intended venues, available supply, and internal capacity all affect what can be specified and reviewed. Advisory turns those inputs into a sequence of decisions, creating a clearer basis for selecting a counterparty and supervising the arrangement.

The sequence: establish objectives, separating market-quality aims such as defined spreads or visible depth from commercial ambitions such as visibility or adoption. Assess project context — development stage, availability, intended venues, existing market structure, operating constraints and reporting needs. Match counterparties based on project stage and listing venues rather than treating every counterparty as interchangeable. Define KPIs: what will be measured, how each metric is calculated, what data informs it, and who reviews it. Then set review points to assess reported performance against the mandate and decide whether objectives or arrangements need adjustment.

Objectives need enough precision to guide decisions. If an issuer wants to assess market quality, it can define the conditions to monitor at each venue, such as spread ranges or displayed depth at specified price levels. A project planning for one venue can define venue-specific measures and reporting before activity starts; a project with multiple venues may need separate thresholds because conditions differ between order books. In either case, objectives are evaluation criteria, not commitments that market conditions will conform to them.

Make ownership explicit. The issuer identifies objectives and assigns internal decision-makers. The market maker is responsible for the execution specified in its mandate. The venue provides the trading environment. The advisor coordinates alignment and supervises the agreed arrangement and KPI framework. Before launch, document the reporting cadence, KPI definitions, data sources, review owner, and the escalation route for missed obligations or material changes.

A useful KPI framework combines measures instead of treating one number as a verdict. Spread, displayed depth, execution quality, and venue coverage each describe a different part of the trading environment. Read together, they offer a more disciplined view of market quality. In isolation, each can mislead.

Spread is the gap between the best displayed buy and sell prices — a narrow spread describes the visible quote at that moment, not how much can trade near it or how long it will persist. Displayed depth is the quantity of orders available at specified price levels — it shows visible capacity, but orders may change or be withdrawn before execution. Execution quality measures how actual trades perform against an agreed reference, adding evidence beyond order-book snapshots. Venue coverage clarifies where activity is observed, but presence on a venue alone doesn't establish meaningful liquidity there.

Reported volume alone doesn't establish market quality. Turnover shows that trades were recorded; it doesn't show the cost of entering or exiting a position, the depth available at a given price, or whether activity reflects independent market participation. A volume target without supporting measures can reward activity while leaving the issuer unable to assess execution conditions.

Context changes how these measures should be read. During volatility, spreads and depth can shift quickly, and venue-specific rules produce different results for the same token. A brief burst of activity and consistent participation across a reporting period shouldn't be treated as equivalent. Advisory should therefore establish consistent definitions, reference periods, and venue-level reporting before performance is reviewed.

Volume totals alone don't establish organic participation either. The Gotbit case — where US prosecutors alleged wash trading between controlled accounts — is a reminder to assess evidence carefully, not a basis to accuse any project or provider without verified, specific support. KPI reports are signals for review, not proof of intent or durable liquidity.

A useful engagement starts with a clear project record, not a polished pitch deck. The issuer should be able to explain the token's current stage, intended venues, decision ownership, and the outcomes it wants to assess. These inputs help advisory match the mandate to the project's operating context and reduce ambiguity when leadership compares reports with agreed KPIs.

Prepare the information that defines the mandate. Project stage: whether the token is pre-launch, approaching a venue launch, or already trading, with milestones that may change priorities. Token design: issuance structure, circulating supply, and known changes to availability. Venue plans: intended venues, planned launch sequence, and operating constraints. Decision ownership: the issuer-side executive accountable for mandate decisions and who reviews reports. Objectives: the market conditions the project wants to assess, distinguished from wider ambitions such as visibility or adoption.

These are essential inputs for structuring the engagement. Ongoing operational reports, venue-level KPI results, and exception records are outputs to review after activity begins. Don't substitute a general ambition such as “improve liquidity” for a defined objective — clear objectives make it easier to determine whether an agreed KPI provides relevant evidence.

Before reporting starts, decide what leadership needs the reports to answer: are conditions consistent across intended venues? Do observed results align with the mandate's definitions? Has a venue-specific issue affected interpretation? Assign an owner for each review, define how proposed KPI changes and exceptions reach decision-makers, and record how material changes to project stage, token availability, or venue plans trigger reassessment. Keep the process workable: reports should support decisions, not create a parallel bureaucracy.

Xavion Capital provides the advisory layer between a token issuer's liquidity objectives, relevant venues, and a suitable market-making counterparty. We match issuers and venues with vetted market makers, taking account of the project's stage and listing venues. The work is structured around the project's context and agreed objectives, not a standard promise of trading activity or market outcomes.

That distinction defines the mandate. The market maker performs the agreed execution. The exchange provides the trading venue. The issuer sets project priorities and retains its decision-making role. Xavion coordinates the match and supervises the liquidity arrangement and KPI structures. Advisory can clarify responsibilities and review criteria, but cannot control token prices, trading demand, or broader market conditions.

Project stage shapes the matching discussion because a token preparing for a venue launch has a different context from one reviewing an active arrangement across several venues. We start from the issuer's stage, token design, venue plans, and decision ownership, which keeps the engagement focused on the project's actual requirements.

For cases we take on, the outcome is a written mandate with defined KPIs, a reporting cadence, and a review structure the issuer can actually use — a stronger foundation for informed decisions as the project develops.