Liquidity Lifecycle Brief

01 /

Start with usable liquidity

A token generation event (TGE) creates a starting point for market access. It does not settle the harder question: can participants trade a meaningful amount, within an acceptable cost range, when they need to? A market can show a recent price and substantial turnover while offering very little capacity for the next order.

This brief sets out Vantage’s approach to that question. We connect three decisions that are often handled by separate teams: how supply enters circulation, how market quality is monitored, and how later transfers are authorised and executed. Each decision changes the conditions inherited by the next stage.

Usable liquidity is specific to an asset, venue, order size, direction, and moment. The distinction matters in practice: Coinbase’s trading rules explain that a market order may execute across several prices and at a worse price than the last trade. A displayed price is therefore an incomplete description of an execution opportunity. [1]

02 /

Before issuance: make the supply map explicit

A launch plan should begin with a common inventory of circulating supply, release conditions, holder categories, and the practical ability to transfer tokens. A vesting schedule describes contractual availability. It does not, by itself, establish a holder’s intention to sell or the timing of an exchange deposit.

The supply map should identify what is known, what is estimated, and what remains conditional. Teams should distinguish treasury inventory, investor allocations, ecosystem incentives, and any inventory provided under a market-making arrangement. Combining them into one number conceals different permissions and incentives.

Venue readiness belongs in this same discussion. Confirm deposit and withdrawal status, supported networks, trading pairs, access requirements, and the sequence of opening events. A token available on two venues is not necessarily movable between them at the moment a participant needs to rebalance.

The output is a decision record: the assumptions behind launch readiness, the people responsible for checking them, and the conditions that would justify changing the sequence. It should be usable by the launch, operations, and communications teams without requiring each to reconstruct the plan.

03 /

After listing: observe the market that actually exists

After trading opens, replace launch assumptions with observations. Track both sides of the order book, depth at agreed distances from the mid-price, quote continuity, and the execution cost of representative order sizes. Keep raw observations available so that summary metrics can be checked.

Each measurement needs a definition. Depth measured within a narrow price band answers a different question from depth measured much further away. A daily average can also hide a short but serious interruption. Report typical conditions alongside adverse periods, missing data, and operational exceptions.

Market-maker oversight should separate market outcomes from contractual performance. A token’s price can fall even when quoting obligations are met. Conversely, rising prices do not prove that a mandate was fulfilled. Review what the provider agreed to do, what was observable, and how deviations were handled.

Agree who can change a parameter, who must approve an exception, and when an issue escalates. A dashboard becomes useful when an observation leads to an accountable decision. Targets should relate to genuine market quality, with no requirement to manufacture turnover or defend a promised price.

04 /

Transfers: match the route to the constraint

An unlock, treasury rebalance, or strategic transfer brings a new set of questions. What must move, who has authority, which restrictions apply, and what amount can the available market realistically accommodate? Resolve these before choosing an execution route.

Public-market execution, an agreed block transaction, and a request-for-quote process have different exposure, pricing, and settlement considerations. Compare total expected cost, completion uncertainty, counterparty risk, information leakage, and operational requirements. A route that looks cheaper at quotation may be unsuitable once those constraints are included.

Phasing an instruction can create opportunities to reassess conditions, but it also extends exposure to price changes and may leave part of an instruction unfilled. A schedule should include limits, expiry, and a review process. It should not be described as a way to eliminate market impact or guarantee an outcome.

The same inventory must not be counted as independently available across several accounts or routes. Reconcile funding, permissions, and outstanding orders before making a commitment, and reconcile executions and settlement afterwards.

05 /

Build one shared decision record

Fragmented infrastructure adds another layer to coordination. The BIS’s 2023 review identifies fragmentation and substantial operational and structural risks in the crypto ecosystem. Our inference is that a lifecycle plan needs to record dependencies between venues and service providers, rather than assuming all observed liquidity can be accessed as one pool. [2]

This record should explain why a decision was taken with the information available at the time. Later outcomes can then inform the next decision without rewriting the original assumptions. Relevant records remain subject to access controls, confidentiality, and applicable retention requirements.

06 /

A useful first review

Begin by asking the teams responsible for issuance, secondary-market operations, and treasury activity to describe the same upcoming milestone. Differences in their answers reveal the handoffs that need attention.

• Which supply figures and dates are confirmed, and who owns the remaining assumptions?
• What trading conditions are being measured, on which venues, and at what order sizes?
• Who is authorised to act when a limit or assumption changes?
• How will a transfer affect available inventory and settlement obligations?
• What can be communicated publicly without overstating access, capacity, or certainty?

A workable liquidity strategy leaves those answers connected. Launch design sets the initial conditions; oversight makes changing conditions visible; transfer planning adapts action to the capacity and authority available.