Digital Asset ICO Investment Framework

1. Decision scope. Define the permitted sectors, instrument type, holding period, and required evidence. For this framework, eligible sectors include infrastructure, artificial intelligence, tokenization, decentralized finance (DeFi), payments, and real-world assets (RWA). The fund should specify whether it may buy presale tokens, tokens subject to vesting, or only liquid tokens after launch. This prevents a presale opportunity from entering a mandate designed for liquid public markets.

2. Risk budget. Set the maximum capital at risk at both the portfolio and position level. A fund might authorize a 0.25% portfolio allocation to a presale, with a hard loss limit of the full invested amount. If the fund manages $400 million, that allocation equals $1 million. The risk budget must also account for token unlocks, gas fees, custody costs, legal expenses, and the possibility that a listed token cannot support meaningful trade size.

3. Liquidity and timeline gates. Define the latest acceptable date for a DEX or centralized exchange (CEX) listing, the minimum expected trading depth, and the conditions that allow the fund to hold beyond launch. A listing alone does not create usable liquidity. The CDC should require a documented market-maker plan, a published token unlock schedule, and evidence that the fund can transfer and sell the asset through approved infrastructure.

4. Approval and exit authority. Name the people who can approve, reduce, pause, or exit the position. The investment committee may approve the initial allocation, while the CIO or portfolio manager may cut exposure if a launch condition fails. This matters because presale agreements often contain deadlines that arrive before the next committee meeting. Authority must exist before the deadline, not after the problem appears.

The CDC should also classify each proposed token as Approve, Conditional Approve, or Reject. “Conditional Approve” means the fund may reserve an allocation but cannot release capital until specified evidence arrives. For example, a project may pass its technology review but remain conditional until it confirms a DEX pool, a custody route, and a launch date within the fund’s permitted window.

A practical timeline begins at presale commitment and ends only after the fund confirms tradable liquidity. The following planning range gives the investment team a working control schedule rather than a promise about project performance.

| Stage | Working window | Required decision | |---|---:|---| | Presale review and legal terms | Days 0-10 | Confirm eligibility, ownership rights, restrictions, and wallet controls | | Technical and token-economics review | Days 5-20 | Verify contract status, supply, vesting, utility, and allocation | | Presale close and token generation event | Days 15-45 | Confirm delivery date, claim process, and unlock terms | | DEX launch | Days 30-60 | Verify pool creation, initial liquidity, contract address, and trading controls | | CEX review or listing | Days 60-180 | Treat as a separate milestone; require written evidence rather than marketing claims | | Post-launch monitoring | First 30-90 days | Review volume, liquidity, unlock pressure, treasury actions, and execution |

The CDC should use the shortest credible path, not the most optimistic announcement. If a project claims a CEX listing in 21 days but has no signed exchange confirmation, the fund should plan around the verified DEX route and treat the CEX claim as unconfirmed.

Putting the Charter Into Practice

Dr. Park reviews a tokenized-credit infrastructure project seeking $8 million in presale funding. The project targets a DEX launch in 35 days and states that a CEX listing may follow within 90 days. The fund’s mandate permits RWA and infrastructure exposure, but it limits any single presale allocation to 0.20% of assets. With a $500 million portfolio, the maximum commitment equals $1 million.

She applies the CDC in the following order:

1. Set the mandate test. The project qualifies because its product supports tokenized credit records and settlement infrastructure. The team must still show a working product, a clear token function, and a legal structure that permits the fund to receive and hold the token.

2. Set the loss boundary. Dr. Park approves a $750,000 maximum commitment, below the $1 million ceiling. She assumes the entire amount could become unrecoverable. The fund does not count a projected CEX listing as protection against loss.

3. Set the release schedule. The fund releases 60% at presale close and holds 40% until the project provides the final contract address, independent contract review, wallet allocation report, and confirmed DEX liquidity plan. This staged funding reduces the amount exposed to a failed delivery.

4. Set the liquidity gate. The project must launch on a named DEX within 45 days of presale close, publish the token unlock schedule, and establish a liquidity pool with enough depth for the fund’s planned first reduction. The fund does not require immediate disposal, but it needs a credible path to reduce risk.

5. Set the review dates. The operations team checks the contract and claim process on day 30. The investment team checks the DEX pool on launch day and again after seven days. Dr. Park reviews the position at days 30, 60, and 90 after launch. If the project misses the DEX deadline by more than 15 days without a documented reason and revised evidence, the fund may cancel the undrawn balance or reduce exposure.

6. Record the expected outcome. If the project meets the gates, the fund holds the token through the first 90-day monitoring period with no automatic increase. If the DEX launch fails, the fund retains only the released amount and marks the remaining commitment as cancelled. If trading begins but liquidity remains too thin for the intended position, the fund does not add capital and may seek an orderly reduction.

This process gives the committee a decision it can audit. It also prevents a common error: treating token delivery as investment success. Delivery proves that the token arrived. It does not prove that the market can absorb institutional selling, that the project will execute, or that the token serves a necessary function.

Quick checklist

• Confirm that the token fits an approved sector and instrument mandate. - Calculate the maximum loss using total committed capital, not expected listing value. - Separate presale, DEX, and CEX milestones. - Require a verified contract address before claiming launch readiness. - Record token unlocks, treasury allocations, team vesting, and investor restrictions. - Set a latest acceptable DEX date and a separate CEX evidence standard. - Define who can pause funding or reduce exposure. - Confirm custody, wallet approval, transfer testing, and transaction monitoring. - Schedule reviews for launch day, seven days after launch, and 30, 60, and 90 days. - Mark every unverified project claim as an assumption, not a fact.

What to Watch For Before Approval

Mistaking a listing announcement for liquidity

A project may announce an exchange partnership without naming the trading pair, launch time, market maker, or available pool depth. A token can appear on an exchange while supporting only small trades, creating a misleading exit signal.

Do this: Require the named venue, trading pair, contract address, liquidity source, and launch confirmation. Test a small transfer and sale through approved controls when practical.

Not this: Count a social-media announcement as evidence that the fund can exit.

Allowing the risk budget to expand after presale commitment

A token may decline before launch, prompting the team to average down or purchase additional allocations at a discount. That changes the original risk decision and can turn a controlled position into an unapproved concentration.

Do this: Treat every additional purchase as a new CDC decision. Keep the original maximum loss visible and require fresh approval for any increase.

Not this: Increase the position because the token now looks cheaper or because the project offers a bonus allocation.

Accepting an optimistic launch timeline

Projects often describe a DEX launch as imminent while contract deployment, audits, liquidity funding, and exchange review remain incomplete. Delays also extend the period during which capital remains locked and market conditions can change.

Do this: Build the timeline from verified deliverables: signed presale terms, completed contract review, final token address, liquidity commitment, claim instructions, and a confirmed launch window. Add a delay rule, such as cancelling undrawn capital after 15 days beyond the approved deadline unless the committee renews the approval.

Not this: Use the project’s shortest advertised timeline as the fund’s base case.

The CDC works when it produces a clear answer before capital moves: what the fund may buy, how much it may lose, when it expects usable liquidity, and who can act when conditions change. That discipline gives the investment team room to pursue early-stage digital assets without confusing access with control. The next analytical task is to test whether the token’s fundamentals and economics justify the risk budget in the first place.

End of chapter one. 4 more chapters and about 9,725 words in the full book.