Allocator Discovery: Risk, Liquidity, Custody, and Decision Criteria

Good discovery is not a product pitch disguised as a questionnaire. Its purpose is to establish whether a particular entity–sleeve–mandate can take a defined on-chain position within its risk, liquidity, custody, and governance constraints.

In the previous lesson, you segmented prospects by mandate, portfolio composition, return target, liquidity horizon, and operational sophistication. This lesson converts that profile into a practical discovery-question set for an institutional conversation. The aim is to leave a meeting with evidence, named owners, and clear next steps—not a vague statement that the client is “interested in DeFi.”

For Exponent, this discipline matters especially because a fixed-maturity yield position can sound simpler than it is. A client may like a stated maturity and an implied fixed rate, yet still be unable to accept the underlying-asset exposure, sell before maturity, custody Solana assets, or obtain approval to interact with a smart contract.

---

Discovery has four outputs

A productive discovery process should answer four questions:

1. Risk: What losses, exposures, concentrations, and operational failures are unacceptable?
2. Liquidity: When might the capital be needed, and what does an acceptable exit look like under normal and stressed conditions?
3. Custody and operations: Can the institution safely authorize, execute, settle, monitor, reconcile, and report this specific transaction on Solana?
4. Decision process: Who must approve the idea, what evidence do they require, and what sequence of gates determines whether capital can actually be deployed?

The operative word is specific. “We use a qualified custodian” does not establish that the custodian supports the relevant Solana assets, wallet policy, transaction type, and contract interaction. “We have a long horizon” does not establish that the sleeve can tolerate a stressed secondary-market exit. “The CIO likes the opportunity” does not establish an investment-committee decision.

Before asking detailed questions, frame the discussion clearly:

“To avoid proposing something that conflicts with your policy or operations, I’d like to understand the mandate, loss and liquidity constraints, custody workflow, and approval path for this sleeve. If there is a fit, we can then define the diligence and implementation work.”

This makes the conversation consultative rather than interrogative, while setting the expectation that a yield number alone is not the decision.

The CFA Institute’s IPS framework gives a useful institutional standard: risk, liquidity, governance, and reporting are components of an investment policy, not separate administrative details.

---

Start with the sleeve and its economic purpose

First establish what capital is actually under discussion. This prevents a common institutional-sales error: treating the firm’s entire balance sheet or AUM as deployable.

Use a short opening set:

• “Which legal entity, fund, strategy, or treasury sleeve would own a potential position?”
• “What job must that capital perform: reserve management, income generation, yield enhancement, rate trading, inventory management, or a strategic Solana allocation?”
• “What is the portfolio’s reporting and liability currency?”
• “What assets are already held in that sleeve, and what yield sources are currently used?”
• “Is the initial conversation about a research exercise, a pilot, or a potentially scalable allocation?”

These questions establish the denominator for every later answer. A firm may report in USD but hold SOL or a liquid-staking token. In that case, an underlying-denominated maturity payoff may be economically useful, but it is not equivalent to a USD-fixed cash flow. Similarly, a market maker evaluating rate liquidity has different limits and monitoring needs from a treasury considering a hold-to-maturity allocation.

Record the answer as a one-sentence mandate:

Example: “USD-reporting digital-asset fund evaluating a limited SOL-denominated income sleeve; quarterly liquidity is preferred, but no known cash liability exists before the next two maturities.”

This is a hypothesis, not a recommendation.

---

Uncover risk limits: turn “conservative” into operational boundaries

Risk discovery should identify both the loss the client can bear and the risks it is permitted to take. Neither can be inferred reliably from target return.

For a fixed-maturity yield-market conversation, distinguish at least these exposures:

Risk category	What the allocator may be exposed to	Discovery objective
Underlying-asset price risk	Change in SOL or liquid-staking-token value in reporting currency	Establish whether the client thinks in USD, SOL, or another denomination
Yield and rate risk	Realized yield differs from expectations; market-implied rates change before maturity	Identify whether the client seeks predictable yield or wants variable-yield exposure
Protocol and smart-contract risk	Failure or exploit at the yield source, exchange, or connected protocol	Determine eligibility, due-diligence standard, and concentration limits
Liquidity and early-exit risk	Position may need to be sold before maturity at an unfavorable rate or price	Determine whether hold-to-maturity is genuinely feasible
Depeg or validator risk	A liquid staking token may deviate from its reference asset; validator and staking risks remain	Determine allowed underlying assets and issuer/provider concentration
Operational and governance risk	Signing, settlement, monitoring, or approval failure	Identify control owners and escalation thresholds

Core risk questions

Ask the questions in a sequence that moves from policy to measurable limits.

1. “Is exposure to digital assets, Solana, DeFi protocols, liquid-staking tokens, or tokenized yield instruments permitted under this mandate?”
   Follow with: “Is the restriction formal, such as an IPS or offering document, or a current committee preference?”

2. “What is the relevant unit of risk: a maximum dollar loss, percentage drawdown, value-at-risk limit, concentration limit, tracking-error budget, or some combination?”
   A client may use several measures. The important point is to identify which one controls the decision.

3. “What maximum allocation is permitted to a single chain, protocol, asset, validator set, custodian, or DeFi strategy?”
   Ask whether these are hard limits, monitored thresholds, or informal guidelines.

4. “Which risks are explicitly unacceptable even at a small position size?”
   Useful prompts include smart-contract exposure, variable yield, leverage, stablecoin exposure, self-custody, noncustodial contract interaction, and early-exit uncertainty.

5. “How is a position assessed after entry: daily mark-to-market, monthly NAV, maturity payoff, or a combination?”
   This matters because an instrument that converges to a defined maturity payoff can still create interim marks and risk reporting questions.

6. “What event would require risk escalation, reduced exposure, or a forced exit?”
   Examples include a depeg, protocol incident, downgrade of a custody arrangement, liquidity deterioration, governance change, or breach of an allocation limit.

7. “Who owns ongoing risk monitoring, and who can require de-risking?”
   A portfolio manager, risk officer, investment committee, and operations function may hold different responsibilities.

A useful follow-up discipline is to ask for the document, metric, or owner behind each answer. “We are cautious on smart-contract risk” is a preference. “DeFi exposure is capped at 2% of NAV, with protocol approval required from risk and legal” is an actionable constraint.

The SBAI guide is particularly useful for converting broad operational due diligence into precise questions about mandate, custody, valuation, conflicts, and verification.

---

Uncover liquidity needs: maturity is not liquidity

A maturity date is useful only if the client can hold the position until that date. Institutional liquidity discovery must separate:

• the client’s intended holding period;
• its contractual or expected cash needs;
• the practical ability to sell, unwind, or transfer a position; and
• its ability to withstand a stressed exit.

The maturity-selection interface below is a helpful visual reminder: choosing a dated market is a capital-allocation decision. It is not merely selecting a yield quote.

Core liquidity questions

1. “What liabilities, redemptions, operating expenses, collateral needs, or expected capital calls could draw on this sleeve?”
   Ask for timing, size, and whether these needs are contractual or merely possible.

2. “What is the minimum holding period this capital can support without creating a governance problem?”
   This is more revealing than asking only for an “investment horizon.”

3. “Would the client be willing and able to hold the position until the stated maturity if secondary liquidity became thin?”
   A clear “yes” can support a maturity-aligned analysis. An uncertain answer requires more conservative sizing and exit planning.

4. “If you needed to exit before maturity, what matters most: immediate execution, a minimum acceptable rate or price, or completing the exit within a specified number of days?”
   This identifies whether execution certainty, price protection, or patience dominates.

5. “What position size could be deployed or exited without creating unacceptable market impact?”
   The answer should be tied to expected market liquidity, not just total AUM.

6. “What stress scenario should the position survive?”
   Ask the client to specify a scenario such as a sharp SOL decline, liquid-staking-token depeg, spread widening, protocol incident, or client-redemption cycle.

7. “How often must the position be valued and reported, and can the valuation approach accommodate an instrument with limited observable secondary trading?”

8. “Are lockups, notice periods, or settlement delays allowed within the mandate?”
   This includes constraints created by the client’s own fund terms, not only protocol withdrawal mechanics.

A strong discovery note captures liquidity coverage, not just a horizon. For instance:

“The fund offers monthly liquidity to investors but maintains a separate strategic sleeve with a six-month evaluation horizon. Any position must remain independently valued weekly and be reducible within five business days under a defined stress assumption.”

This tells you far more than “long-term investor.”

---

Map custody and operational reality

Institutions often use the word custody to describe several different things:

• legal safeguarding and asset segregation;
• key-management technology;
• wallet-policy and multi-party approval controls;
• a trading or DeFi access layer;
• transaction monitoring and compliance controls; and
• accounting and reconciliation workflows.

Do not assume these functions are provided by one firm, or that a recognized provider supports every Solana asset and transaction type a client may need. A custody arrangement may be strong in safeguarding assets yet still lack the approval workflow or protocol connectivity needed for an on-chain yield-market transaction.

The following Bankless interview gives useful context for why institutional workflows go beyond an individual holding a hardware wallet: approval policies, compliance, availability, and controlled protocol access all shape feasibility.

Core custody and operations questions

Use the following questions as a structured checklist, but do not ask them all mechanically. Start with the client’s current model, then investigate the points that affect the proposed workflow.

Area	Discovery question	Why it matters
Custody model	“Are the relevant assets held with a third-party custodian, self-custodied, or managed through a hybrid structure?”	Establishes the basic control and responsibility model
Asset support	“Does the current setup support SOL, the relevant liquid-staking token, and receipt or yield tokens?”	Support for major crypto assets does not prove support for the actual assets required
DeFi capability	“Can authorized wallets interact directly with approved Solana programs, or are transactions limited to transfers and centralized venues?”	Determines whether the position is operationally possible
Signing authority	“Who can create, approve, and sign a transaction? What thresholds, dual controls, and time windows apply?”	Identifies segregation of duties and operational delay
Policy controls	“Can the wallet policy allowlist recipient addresses, token mints, and smart-contract interactions?”	Reveals whether a protocol transaction can pass internal controls
Segregation and title	“How are assets segregated, recorded, and verified for this legal entity?”	Connects custody architecture to auditability and insolvency considerations
Transfer readiness	“What is the normal and emergency turnaround time for moving assets from custody into an execution wallet and back?”	Determines whether timing assumptions are realistic
Reconciliation	“Who reconciles on-chain transactions, positions, fees, and valuation into the fund administrator or accounting system?”	A position that cannot be reconciled reliably is not institutionally deployable
Incident response	“If a transaction is disputed, a wallet policy blocks an action, or a protocol incident occurs, who has authority to pause, investigate, and communicate?”	Clarifies operational ownership under stress
Compliance	“What internal legal, compliance, sanctions-screening, transaction-monitoring, and recordkeeping review is required?”	Identifies noninvestment gates before capital can move

Two details deserve special attention in an Exponent-oriented conversation.

First, distinguish custody of assets from permission to interact with a protocol. A custodian may safely hold SOL but require a separate approval path, policy configuration, or connected wallet for DeFi interaction.

Second, distinguish wallet authorization from investment authorization. A wallet may technically be able to sign a transaction while the investment team lacks delegated authority to initiate it. Both authorizations are required.

Avoid making legal or regulatory assurances on the basis of a provider label. Ask instead:

“What does your counsel, compliance team, and custody documentation permit for this entity in this jurisdiction?”

That question is specific, verifiable, and appropriate to the client’s own control framework.

---

Reveal the real decision process

The decision process is not a final administrative question. It determines what discovery evidence you need, how long the process may take, and whether a pilot is possible before a full allocation.

A useful model is to map six roles:

Role	Typical responsibility
Economic sponsor	Owns the portfolio problem and benefits from solving it
Investment decision-maker	Determines whether the return and risk case fits the mandate
Risk owner	Assesses limits, concentration, liquidity, and scenario exposure
Operations and custody owner	Validates wallet controls, execution, settlement, accounting, and monitoring
Legal and compliance owner	Determines permissibility, regulatory treatment, documentation, and controls
Final approver	Investment committee, board, CIO, treasury committee, or delegated authority

At a smaller family office, several roles may sit with one person. At a large asset manager, each can be a separate team with its own evidence standards. The key is not the number of stakeholders; it is whether responsibilities and gates are explicit.

Core decision-process questions

1. “Who owns the investment problem, and who is accountable for the final allocation decision?”

2. “Which groups must review this before capital can be deployed: portfolio management, risk, legal, compliance, operations, custody, tax, fund administration, or procurement?”

3. “What can the portfolio manager approve under delegated authority, and what requires committee or board approval?”

4. “What is the sequence of review? Which team must approve first, and which review can occur in parallel?”

5. “What documents or evidence are required for a new on-chain protocol, asset, custody workflow, or strategy?”
   Typical requests may include protocol architecture, audit materials, governance and admin controls, legal analysis, liquidity evidence, valuation treatment, and incident procedures.

6. “What is the investment-committee cadence, and what is the earliest realistic decision date?”

7. “Has the organization approved comparable exposures before? If so, what precedent can be reused, and what makes this different?”
   This is often the quickest way to identify hidden blockers.

8. “Would a constrained pilot be permissible? If yes, what position size, holding period, monitoring requirements, and exit conditions would define success?”

9. “What would cause the proposal to be rejected even if the expected return were attractive?”
   This surfaces hard disqualifiers early.

10. “Who will be responsible for the position after trade date, including monitoring, valuation challenges, reporting, and escalation?”

A decision map should identify names or functions, not merely departments. “Legal needs to look at it” is incomplete. A usable record is: “Digital-assets counsel must confirm authority for direct protocol interaction; review follows completion of the operations-control memo; investment committee meets monthly.”

---

Run discovery as a staged conversation

For an initial 30- to 45-minute conversation, use a staged approach rather than attempting a full due-diligence review.

1. Confirm the sleeve and mandate. Identify the legal entity, capital purpose, reporting currency, relevant current holdings, and whether the conversation concerns research, a pilot, or allocation.

2. Identify hard disqualifiers. Ask whether digital assets, Solana, DeFi, the relevant underlying asset, or direct smart-contract interaction are prohibited.

3. Establish risk and liquidity boundaries. Identify maximum exposure, unacceptable risks, redemption or liability needs, hold-to-maturity capacity, and stress-exit requirements.

4. Test operational feasibility. Confirm custody model, asset and transaction support, wallet policy, authorized signers, reconciliation, and incident ownership.

5. Map the approval path. Identify decision-makers, evidence requests, committee cadence, external dependencies, and pilot rules.

6. Summarize back to the client. State what you heard, distinguish confirmed facts from open items, and agree on the next diligence step.

The final summary is a control mechanism. It lets the client correct assumptions before a product discussion becomes too specific.

A concise post-call record can use four fields:

Field	Example
Confirmed	SOL and approved liquid-staking-token exposure permitted up to a stated sleeve limit
Client-reported, not yet verified	Custodian supports Solana and policy-controlled DeFi interactions
Open diligence item	Legal treatment of direct interaction with an on-chain yield-market program
Decision implication	No allocation proposal until custody workflow and legal approval are validated

This format protects against accidental overstatement. It also helps internal product, risk, and operations teams see exactly what they must answer.

---

Key takeaways

An effective Exponent discovery set does not begin with “Which yield product do you want?” It begins with the client’s ability to own and govern a position.

The essential questions uncover:

• Risk limits: permitted assets and strategies, loss and concentration boundaries, unacceptable exposures, monitoring metrics, and risk owners.
• Liquidity needs: liabilities, redemption terms, hold-to-maturity capacity, early-exit requirements, stress scenarios, and valuation frequency.
• Custody model: asset support, protocol-interaction capability, signing controls, allowlists, settlement timing, reconciliation, and incident response.
• Decision process: sponsor, approvers, review sequence, required evidence, committee cadence, precedents, and pilot conditions.

The desired output is a verified discovery record with clear blockers and named next steps—not a premature recommendation. In the next lesson, you will convert these answers into a requirements matrix covering return, risk, liquidity, execution, custody, and reporting.