A crypto asset manager helps an institution oversee crypto assets within an agreed mandate, but the title alone does not establish who sets treasury policy, holds assets, executes trades, or has regulatory permissions. The institution should define those responsibilities explicitly: asset oversight is distinct from treasury decisions, custody, and trading access, even when one provider performs more than one function.

What a crypto asset manager does in an institutional setting

“Crypto asset manager” is a role label, not a complete description of an organization’s authority or services. The work an institution assigns depends on its mandate and operating model. A manager might be asked to oversee assets against stated objectives and report on activity, while the institution retains policy decisions and operational approvals. The specific scope must be established in the arrangement rather than inferred from the title.

A useful starting distinction is between advice or oversight and authority to act. An institution can specify whether a manager may make recommendations, propose transactions, or carry out approved actions. These are different permissions. A mandate should identify which assets and activities it covers, who can authorize changes, and what reporting the institution expects. It can also establish the conditions under which proposed actions must be reviewed or escalated. Those details belong in the institution’s governance and service arrangements, not in assumptions about a job title.

The label also does not prove that the manager is a custodian, exchange, broker, or regulated financial provider. A centralized crypto exchange operator may combine trading, proprietary activity, lending, token issuance, and custody, but not every exchange performs every function. Combining roles can create operational dependencies and conflicts, so an institution should identify which legal entity and service is responsible for each activity rather than treating a provider’s broad offering as one undifferentiated role. source

For practical assessment, ask what work is actually assigned: monitoring assets, preparing reports, making recommendations, or acting under delegated authority. These categories can overlap in a particular arrangement, but they should not be treated as interchangeable. The institution needs to understand both the services provided and the limits placed on them.

How asset management differs from treasury, custody, and execution

Treasury is the institution’s function for setting policy and managing its own liquidity and balance-sheet needs. An asset manager may be engaged to oversee assets within those boundaries, but the title does not itself transfer the institution’s policy authority. The institution should decide which objectives and constraints apply, then document whether the manager can recommend or act within them.

Custody concerns access to assets and the keys or accounts used to control them; it is not the same as deciding how assets should be managed. In a third-party custody model, a custodian manages access to private keys on behalf of customers. The institution’s custody arrangement, customer rights, segregation, insurance, regulation, and insolvency treatment can vary by provider and jurisdiction. source

Execution is another distinct function: it is the process of carrying out a transaction, potentially through a trading venue or other market-access provider. A centralized exchange customer typically transfers assets into the exchange’s custody before using its internal trading system, although some venues and products use different custody, brokerage, or settlement arrangements. This example shows why “manager,” “custodian,” and “execution venue” should not be used interchangeably. source

One organization may provide more than one of these services, but that does not make the responsibilities identical. For example, a provider might oversee assets and also offer custody or trading. The institution still needs to know which service is being used, what authority applies to it, and which contractual terms govern it. A tokenized security can also illustrate why asset oversight and recordkeeping are separate questions: issuer-sponsored arrangements may use the crypto network as part of the master ownership record, or use onchain transfers to trigger updates to an authoritative offchain record. Which record is legally effective depends on governing documents, applicable law, and transfer mechanics. source

Mandates, authority, and operational controls

A mandate is the documented scope of work and authority assigned to a manager. To make that scope usable, an institution should map the decision path before delegating activity. Separate who may propose an action, approve it, execute it, and reconcile or report on it. Avoid assuming that one person or provider should automatically perform every step.

The mandate can identify covered assets and activities, decision limits, approval requirements, reporting expectations, and escalation routes. For example, an institution can specify which events require prior approval and which require notification. This is an illustrative governance choice, not a universal rule for institutional arrangements. The specific terms depend on the institution’s operating model and the mandate it grants.

Operational controls should be described separately from investment objectives. An objective states what the institution wants the arrangement to achieve; a control states how authority, approvals, and oversight are managed. A contract or operating procedure can make the division of responsibilities legible to the institution and the service providers involved. Where a provider offers multiple functions, the institution should verify whether the described controls apply to each function and which entity is accountable for the relevant service.

The institution can also document how decisions and activity are recorded, who receives reports, and what happens when an issue falls outside the manager’s delegated scope. These procedures help distinguish the authority to recommend from authority to approve or execute. They also make it easier to compare what a provider says it does with the responsibilities actually assigned in the arrangement.

Risks and due diligence an institution should assess

Assess risks in relation to the actual mandate, not a generic image of what an asset manager does. Governance questions include who has decision rights and how conflicts are handled. Counterparty and asset-control questions include which entity holds assets or controls access, and what rights the institution has under the arrangement. Operational and technology questions include which systems support activity and how responsibilities are divided when a service depends on another provider.

Request evidence for specific claims rather than treating broad assurances as proof. If a provider describes security controls, recovery processes, fees, service availability, yield, or performance, the institution should ask for documentation that supports the particular claim and its scope. No such feature follows simply from the title “crypto asset manager.” This explainer does not establish provider-specific fees, recovery capabilities, availability, or returns.

Disclosure about rights and backing is especially important where an arrangement involves an asset-backed token. The Financial Stability Board recommends that global stablecoin arrangements provide transparent information about governance, stabilization, reserves and custody, legal claims, redemption rights, operations, risk management, and financial condition. That recommendation is not evidence that a particular arrangement meets those expectations; institutions must examine the actual arrangement and its documentation. source

A useful review keeps three questions distinct: what the manager is authorized to decide, which entity controls access to assets, and which party carries out transactions. If one provider performs multiple functions, the institution should examine each role and its associated terms rather than assume that responsibility in one area proves responsibility in another. The available evidence here does not establish any provider’s particular controls, recovery process, or service terms.

Regulatory and jurisdictional limits on the role

Do not infer licensing, registration, permitted activities, or compliance duties from the title alone. The evidence here does not establish which rules apply to a particular manager or institution. Those questions depend on the jurisdiction and the specific services, parties, and contractual arrangement involved, so they require current, authoritative evidence for the relevant case.

The same caution applies to tax treatment. No jurisdiction-specific tax conclusion follows from the role description, and this explainer does not provide tax guidance. An institution should keep legal, compliance, and tax determinations separate from its operational definition of the manager’s mandate.

The practical boundary is straightforward: define what the manager oversees, preserve the institution’s explicit policy and approval decisions, identify who controls custody and execution, and document how work is reported and escalated. A clear division of responsibilities makes the role assessable without assuming that one provider, title, or operating model covers every institutional need.

Sources and references