Token Liquidity Event Planning

Token liquidity event planning is the work of sequencing five separate legs so they meet: custody releases, a venue executes, a bank receives, a CPA has the liability modeled, and counsel confirms who is authorized to sign. My view is that founders solve all five and test none of the joins, so the sequence breaks on the day it has to hold.

Part of our guide: Family Office.

The short version

• Each party owns one leg and nobody owns the handoffs. Every schedule you are quoted is measured inside one process and stops at its edge.
• Authority to act for an entity is documented separately from ownership. In Wyoming, a member is not an agent of the company by virtue of membership (W.S. 17-29-301).
• The last hop runs on a clock nobody at your table controls. Fedwire’s deadline for third-party transfers is 6:45 p.m. ET each business day, and processed transfers are final (Federal Reserve).
• The tax date lands before the return does. Estimated installments fall on April 15, June 15, September 15, and January 15 (26 U.S.C. 6654(c)(2)).
• A rehearsal is the only thing that tests a join. Walk a small amount down the whole path, same accounts, same signers, before anything material moves.

Five legs, five separate clocks

List who is on the path and you get the same five: whoever holds the keys, whoever executes, whoever receives dollars, whoever computes what is owed, and whoever confirms the signer may sign. Each timeline you collect starts when work enters that party’s queue and ends when it leaves, so none covers the gaps on either side.

Custody is the leg people underestimate, because it feels like their own property. It carries address whitelisting, approval quorums, and cooling-off intervals on new destinations. Where a registered adviser is involved, the rules define the account itself: the adviser must notify the client in writing of “the qualified custodian’s name, address, and the manner in which the funds or securities are maintained” (17 CFR 275.206(4)-2(a)(2)). That paperwork sets the name that travels.

The banking leg has a door that closes daily. The Fedwire Funds Service business day ends at 7:00 p.m. ET, and a processed transfer is “immediate, final, and irrevocable” (Federal Reserve). A settlement finishing at 4:00 p.m. and a bank needing two hours of review are one day on paper and two in fact.

Transmittal orders of $3,000 or more carry the transmittor’s name, address, and account number to the recipient’s institution (31 CFR 1010.410(f)), so names chosen at the start get read by strangers at the end. The tax leg wants the record either way, since digital asset transactions get reported whether or not they produce a gain (IRS, Digital assets).

Authority is the join nobody is assigned

Hold tokens in a personal wallet and sell into a personal account, and authority never comes up. The moment an entity or a trust enters the chain, three institutions independently want proof of the same thing, and the default rule supplies none of it:

A member is not an agent of a limited liability company solely by reason of being a member.

W.S. 17-29-301, Wyoming Limited Liability Company Act

Owning the Wyoming LLC that owns the tokens tells a venue nothing about whether you may trade them. The operating agreement does, a resolution does, and Wyoming also lets a company file a statement of authority with the secretary of state naming a person’s authority to “enter into other transactions on behalf of, or otherwise act for or bind, the company.” I have watched exactly one founder file one ahead of an event. It closed a bank question in a morning.

Trusts run the same trap on different rails, where the trustee’s power of sale and the governing instrument do the work the LLC documents do. Either way, one name has to appear in four places at once: the governing document, the venue’s authorized-trader record, the custody approval set, and the bank’s signature card. Upstream of it all, the lock-up terms decide whether the transfer is permitted, on a slower clock than anyone expects.

Running the whole path once, small

The fix costs almost nothing. Take an amount small enough that losing track of it is an annoyance, and walk it from the key holder to the bank account and into the books as one continuous transaction, in the identical accounts, with the identical people.

Each hop pays for itself. The custody release proves the destination address survived whitelisting and the approvers are reachable on a workday. The venue deposit proves the entity account is funded and the trader is recognized. A small execution proves settlement produces dollars where you believe it does. The withdrawal proves the bank accepts that originator under that name. The step people skip: hand the record to the CPA and ask which installment date the liability lands on. Computation belongs to token sale tax planning; the rehearsal produces the date.

A small transaction cannot test size, so it will not surface a review that triggers on amount or a venue limit tier. It tests the joins, where the failures cluster, and turns five estimates into one observed elapsed time.

What I actually see

Three failures repeat, and none of them is a party doing its job badly.

Five green lights and no calendar. A founder shows me confirmations from the custodian, the venue, the banker, the CPA, and counsel. Every one is accurate. Not one references another party’s date, and no document anywhere states the elapsed time from instruction to spendable funds.

The name that changes between hops. The keys sit with an entity, the venue account was opened years earlier in a personal name, the bank account is titled to a newer holding company, and the return will be filed by someone else again. Each account is correct on its own terms. Read end to end, the path describes four persons moving one asset.

The rehearsal that skipped the middle. Someone tests a custody withdrawal in March, tests an inbound wire in June, and concludes the path works. The untested segment is reliably the one that fails, because it was never a segment anyone owned.

Here is the exercise. Draw the path as a row of boxes with an arrow between each pair. Above every box write the exact legal name on that account and the human who can act on it. Below every arrow write business days from instruction to confirmed arrival, and the person you call when it stalls. Then look only at the arrows. The blank ones are your real schedule, and where the money will sit.

Where this goes wrong

Almost every bad liquidity event is a set of correct decisions taken in an order that does not work.

The tokens release into a venue account the entity cannot legally control. The bank account is three weeks old, so an unfamiliar inbound payment reaches an institution with no history to weigh it against. The custody approver is on a plane on release day. Settlement completes after the wire cutoff and the payment waits a night nobody budgeted. The liability is modeled in March for an August disposition, so the September installment passed unfunded. And the documentation that would have answered all of it existed, in five places, held by five people who never compared copies.

The decision rule

1. Draw the path as one sequence before booking anything: keys, venue, bank, books, and the authority gating the first three.
2. Reconcile the legal name at every hop, so the custody, trading, and receiving accounts and the tax return describe one owner.
3. Prove authority in writing where an entity or trust holds the position: governing document, a resolution, and for a Wyoming LLC a filed statement of authority under W.S. 17-29-302.
4. Get each party’s own clock in writing: custody release window, venue onboarding, the bank’s notice expectations, the CPA’s turnaround.
5. Run the entire path once, small, in the same accounts, with the same approvers, on a normal business day.
6. Put the estimated-payment date on the transaction calendar, since installments are fixed by 26 U.S.C. 6654(c)(2) and do not wait for a filing.
7. Name one person who owns the joins, with standing to pause the sequence when a leg slips.
8. Keep tranche sizing away from the reporting question, since 31 U.S.C. 5324 makes it an offense to structure a transaction for the purpose of evading a reporting requirement.

Where this sits

This article covers the sequence. The window ahead of it belongs to planning before an unlock, the computation to token sale tax planning, and how a large position reaches a counterparty to OTC block trade liquidity.

The professional-boundary problem has a specific cause: every engagement letter on the path describes one leg. The attorney confirms authority, the CPA computes and files, the custodian safeguards, the venue executes. Those four scopes cover the whole path and leave every arrow between them unassigned, unbilled, and therefore unowned. No professional is failing when a handoff drops, because none was engaged for handoffs. The holder is the only party whose interest spans all four, which makes owning the sequence a job for the person least likely to have done it before.

Sources

• 17 CFR 275.206(4)-2, Custody of funds or securities of clients by investment advisers
• Wyoming Statutes Title 17, Wyoming Limited Liability Company Act (W.S. 17-29-301, 17-29-302)
• 26 U.S.C. 6654, Failure by individual to pay estimated income tax
• 31 CFR 1010.410, Records to be made and retained by financial institutions
• 31 U.S.C. 5324, Structuring transactions to evade reporting requirement prohibited
• Federal Reserve, About the Fedwire Funds Service
• IRS, Digital assets

Related

• How should a founder plan before a token unlock?
• Token sale tax planning
• OTC block trade liquidity for large token positions
• Can founder tokens be transferred to a trust?
• How do founders diversify token wealth?
• Founder and token holder wealth

Last updated: 3 August 2026.

This article is general education, not legal, tax, or investment advice. Sequencing and rehearsal reduce certain execution and settlement risks but do not eliminate them, and no institution is obligated to accept a transfer or meet a stated timeline. Talk to a qualified attorney and CPA about your own situation.