Crypto market-making firms may provide contracted trading and related operational services, but an organization must establish the exact scope, controls, incentives, and measures in the specific engagement. Before signing, document responsibilities and asset access, verify commercial and operational terms, define how delivery will be measured, and obtain qualified review of jurisdiction-specific questions. A service description alone does not establish liquidity, execution quality, or commercial outcomes.

What organizations engage market-making firms to do

Engaging an external firm means assigning defined responsibilities to a service provider rather than relying only on an internal team. The phrase “market-making firm” does not specify what a particular firm will do for a given organization. The engagement’s scope needs to identify the covered venues, instruments, operating periods, and tasks, as well as the responsibilities that remain with the organization.

That distinction matters because similar labels can refer to different arrangements. A firm might describe a service broadly, while the actual contract limits it to particular assets or venues. The organization should translate the description into specific duties: what the provider is expected to do, what decisions it may make, what information it must report, and what the organization must supply or approve. Do not treat an informal description or a proposal summary as a substitute for written scope.

A documented service is also different from a guaranteed result. Research on automated market makers describes a particular onchain arrangement in which a liquidity provider contributes assets to a pool and can receive a share of trading fees while bearing inventory and adverse-selection risk. This is an example of a liquidity-provider model, not a universal description of offchain firm engagements or evidence that a particular provider offers that arrangement. It does not establish the likely results of hiring a firm.

For organizations evaluating proposals, the practical question is whether the provider’s specific obligations fit the organization’s needs and can be checked. Claims about liquidity, execution, or commercial outcomes should be treated as matters to define and evaluate, not conclusions that follow automatically from the provider’s title.

How a market-making engagement can be structured

Compare proposals by the responsibilities they assign, rather than by labels alone. Record which venues and instruments are in scope, when the service is expected to operate, who directs or approves trading decisions, and which operational tasks belong to each party. Specify how the parties will handle changes in venue access, asset scope, or operating responsibilities. An agreed process for changes helps keep expectations tied to the actual arrangement.

Account, asset, and credential control require separate attention. State who owns each account, who can access it, which permissions the provider receives, and who can authorize transfers or other actions. Distinguish the ability to act through an account from ownership or custody of the assets. In general, a crypto wallet stores private keys or passcodes used to access and authorize crypto assets, rather than storing the assets themselves. That technical distinction does not resolve contractual rights, custody, or operational responsibility in a particular engagement; those arrangements must be verified directly.

Compensation and incentives should be checked in the agreement, not inferred from the provider’s title or a high-level proposal. Confirm what each party supplies, how any obligations or payments are determined, and what applies if the scope changes or ends. If the arrangement involves inventory, document who supplies it, who controls it, and how it is accounted for. The available evidence does not establish standard prices, compensation structures, or inventory terms across firms.

The operating model should also describe routine coordination. Identify each party’s contact and approval responsibilities, the information that will be exchanged, and how the organization will know whether an action falls within the agreed scope. If work is performed across more than one venue or operational system, the agreement should make the relevant responsibility boundaries clear. Do not assume that a provider controls every element of the trading environment merely because it provides a service connected to it.

Set measurable expectations before comparing proposals

Before work begins, translate the proposed scope into service expectations and reporting duties. For each metric, agree on its definition, calculation method, measurement period, and data source. Specify who produces the report, what underlying records can be reviewed, and how the parties will record exceptions or periods when a measure does not apply. Without those definitions, two figures with the same label may not describe the same thing.

Choose measures that correspond to the responsibilities being purchased. A metric should have a clear connection to an agreed task, a stated observation period, and a source that the parties can identify. When comparing proposals, avoid treating figures as equivalent if they use different definitions, venues, time windows, or data sources. Agree in advance how missing data, unusual operating periods, or changes in scope will be disclosed, rather than silently excluding them from a report.

Separate proposed targets from measured outcomes. A target in a proposal states an expectation; it is not proof that the provider achieved it. Reporting should show what was measured and how, identify any limitations, and avoid presenting a result as independently verified if it was not. If the provider supplies the data, clarify what evidence the organization can use to review the calculation and how disagreements about measurement will be handled.

The measurement context also matters. Research on public-blockchain automated market-maker swaps identifies public transaction visibility, execution ordering, pool depth, and price impact before block inclusion as factors that can affect a swap. That finding concerns a specific onchain execution context; it is not a performance claim about every firm, venue, or engagement. Where a proposal includes onchain activity, distinguish the provider’s responsibilities from factors that depend on the protocol or transaction environment. Do not treat results from one operating context as directly transferable to another without a defined basis for comparison.

A useful reporting arrangement makes both the measure and its limits visible. The agreement can specify reporting frequency, required fields, data sources, and how corrections or exceptions are handled. It should also clarify whether reports describe activity, process completion, or outcomes, since those are not interchangeable. The goal is not to presume that a metric proves service quality, but to ensure that the parties understand what the evidence does and does not show.

Operational, counterparty, and conflict-of-interest diligence

Request provider-specific evidence for operational controls, access permissions, incident handling, and continuity arrangements. Establish who can authorize actions, how access is granted and removed, how incidents are communicated, and what process applies if the service is interrupted. A general statement about controls does not establish that a particular control exists, is implemented as described, or is effective. Ask for documentation that matches the proposed operating setup.

Review asset and account processes directly. Identify where assets are held, who can initiate transfers, how records are reconciled between the parties, and how access or assets are returned or transitioned at exit. Define the steps for ending the engagement, including responsibilities for outstanding instructions, records, and credentials. The organization should retain clear internal approval and oversight responsibilities rather than assuming that a provider’s operational role replaces them.

Ask how the firm identifies and handles conflicts, including related-party activity, venue relationships, and access to organizational information. Determine whether the provider’s documented policies and the proposed contract address the relevant issues. Avoid relying solely on informal assurances, and do not assume that arrangements at one provider apply to another. The available evidence does not establish universal conflict-management practices among market-making firms, so assess the prospective provider individually.

Also examine dependencies that could affect the organization’s ability to oversee the work. Clarify which systems, accounts, data, or third parties the provider relies on and which responsibilities remain outside its control. These are questions for the proposed arrangement, not claims that every firm uses the same operating model. Record open points and request evidence or contract language before treating them as resolved.

Contract, compliance, and jurisdiction-specific review

Review the actual contract for scope, reporting, data use, termination, liability, and dispute-handling provisions. Check whether the terms match the intended workflow: who acts, who approves, what records are kept, and what happens when either party cannot perform. Make sure the agreement describes how changes to scope are approved and how unresolved operational issues are escalated. Resolve ambiguous terms before signing rather than relying on a sales description or a generic template.

Legal, tax, licensing, and compliance questions depend on the parties, activities, and jurisdictions involved. Do not assume a firm’s availability, legal status, or obligations are the same across locations, or that a provider’s own compliance statements determine the organization’s responsibilities. This explainer does not decide which rules apply. Qualified advisers should review the actual arrangement and relevant jurisdictions.

A practical decision record can bring the diligence together: agreed service scope; account, asset, and credential controls; documented commercial terms; metric definitions and reporting sources; operational evidence; conflict questions; contract provisions; and unresolved legal or compliance issues. Keep assumptions visibly separate from verified terms. If a material point cannot be confirmed, mark it as open rather than treating the engagement description as an answer. That approach gives decision-makers a basis for evaluating the actual service without assuming that any particular firm, arrangement, or outcome is universal.

Sources and references