Digital asset strategy for a board: the decisions in order

Who decides this

The board owns the sequence and signs off each decision; management proposes, and named executives carry each one out. The board is accountable for three things. The strategy has a purpose it can measure. Every part has an owner who can execute it. The board receives information that would let it see failure early. A board that delegates the whole programme to one executive, or to an outside firm, still owns the oversight.

The order below is the one we would use. It is not the only defensible order, but each step needs the answers from the step before it.

Decision 1: what is the digital asset programme for?

The programme exists to change one or two business numbers, and the board should write those numbers down before anything else is designed. Examples are active users, fee revenue, the number of independent validators or the share of supply held outside insiders. A token without a measurable job will be judged on its price, which the board does not control.

This is also the moment to decide whether a token is needed at all. If the purpose can be met with equity, points or a partner programme, that is a simpler path. The decision belongs in the minutes, with the reasoning.

Ask management for a one-page paper that answers three questions. What does the token let a user, validator or partner do that they could not do without it? Which two numbers should move, and by how much, within a year? What would make the board stop or change course? If management cannot answer the third question, the first two are not yet firm.

Decision 2: which entity issues, holds and governs?

The issuing entity should be chosen after the purpose is fixed and before any token terms are drafted, because the jurisdiction decides which disclosures apply and who carries liability. Counsel leads this decision. One structure we see separates a foundation that holds the treasury and oversees governance from a development company that builds under contract.

Disclosure follows the entity. In the EU, a MiCA white paper must include a statement from the management body of the offeror confirming, to its best knowledge, that the information is fair, clear and not misleading. That statement comes from the people who run the offeror. The board should know before launch who they will be, and what evidence they will rely on.

The board should also settle who controls what between the entities. Which entity owns the brand, the code and the treasury? Which one employs the team? Who can sign a market-maker or exchange agreement? These answers decide whether decision 4 can be executed at all, so they belong here, not later.

Decision 3: what does the treasury hold, and how is it accounted for?

The treasury policy should set what the organization holds, in what proportions, with which custodians, and how each holding is valued, before tokens are sold or unlocked. It is the CFO’s proposal and the board’s approval.

Accounting rules shape this decision directly. Under US GAAP, ASU 2023-08 requires qualifying crypto assets to be measured at fair value through net income, for fiscal years beginning after 15 December 2024. Tokens an entity or its related parties created are outside that scope. A company holding both third-party assets and its own token may report them on different bases. The board should see how both will look in the accounts before it approves the policy.

Custody is part of the same decision. Name the custodian, the signers, the approval thresholds and who can change them. A treasury policy that does not name people is a draft.

Runway is the other half. The board should know how many months of operating costs the treasury covers in stable assets alone, without selling the organization’s own token. A runway that depends on token sales ties the budget to the market price, and forces sales at the worst time. Set a floor for stable holdings, and a rule for what happens if the floor is breached.

Decision 4: how does the token reach the market?

Market access should be designed from the float backwards: how many tokens will trade, on which venues, supported by whom, and on what contract terms. The CEO and head of markets propose this. The board approves the float, the unlock schedule and any market-maker agreement.

The market-maker agreement deserves the board’s direct attention. In October 2024 US prosecutors in Massachusetts charged 18 individuals and entities in a case alleging that token companies paid market makers to wash trade their tokens. Those are allegations. They still show why a board should read the terms itself, ask what volume and price commitments it is buying, and confirm that nothing in the contract rewards activity rather than real liquidity.

The unlock schedule belongs in the same paper. The board should see, month by month for the first two years, how many tokens become transferable, who holds them and how that compares with expected trading depth. Venues come last. A listing on a venue the float cannot support is a cost, not a milestone.

Decision 5: how will the board know it is working?

The board should receive a short, regular report that tracks the numbers from decision 1, the treasury position from decision 3 and the market metrics from decision 4, with set thresholds that force a board discussion. Monthly in the first quarter after launch, then quarterly, is a reasonable starting cadence.

There is a legal reason for this as well as a practical one. In Delaware, the Supreme Court’s 2019 decision in Marchand v. Barnhill let an oversight claim proceed against directors alleged to have made no good-faith effort to oversee a mission-critical compliance risk. For a company whose business is a token, the token programme is mission-critical. Foundations in other jurisdictions face different rules, but the expectation of real oversight travels well.

Keep the report short enough that directors read it. One page of numbers against targets, one page of decisions needed, and an appendix. If a threshold is breached, the report should say what management proposes, not only what happened.

What goes wrong: the strategy nobody could execute

The common failure is a strategy the board approved and nobody could carry out. The deck was right. The sequence was missing, and the owners were never named.

It looks like this. The board approves a token with a strong purpose statement. Counsel is engaged after the token terms are agreed, and the chosen entity cannot sign the market-maker contract on the terms negotiated. The CFO learns how the treasury will be reported a month before the year-end audit. The launch date holds, so the gaps are closed by whoever is closest, under deadline. Six months later the board asks why the float, the unlocks and the treasury policy contradict each other. There is no single person to ask.

The fix is the order itself, plus a named owner for every line in the table above, approved by the board before work starts. If a decision has no owner, it is not yet a decision.

Test the plan before approving it. Ask each owner to explain, in five minutes, what they will deliver, by when, and what they need from the others. Where two owners give different answers about the same dependency, the plan is not ready. That meeting costs an afternoon; the alternative costs a launch.

How Alcyone approaches it

Alcyone, TrustSwap’s advisory practice, builds the plan in this order and names an owner for every part before launch work begins. A strategy engagement with Alcyone starts with a thirty-minute call with a senior partner. A fixed-scope, fixed-fee assessment follows in week two. The plan is built over three to six weeks, with partners on the line through the launch window and a post-launch report within the week. Quarterly reports follow, by the same partners. In one published case, Alcyone supported the first token launch on a major Layer-1, which brought in more than 5,000 new holders.