Token launches do not fail only on contracts. They stall when an exchange asks for incorporation papers, a market maker wants a counterparty, counsel asks who owns the IP, or a bank asks for an EIN you never applied for.
This is the token launch legal checklist we wish every founder had printed next to the deploy script: the legal and operational gates that turn a protocol into something banks, exchanges and counterparties can actually deal with.
It is the companion to our deeper guide on the LLC for a token launch. That post explains why the wrapper matters. This checklist is the sequence to tick before you go live.
Think of the token contracts as the vending machine: insert conditions, dispense outcomes. The company is the shop that owns the machine, pays the electricity, signs the lease and answers when someone asks for a receipt.
At OtoCo, we are bringing what was once reserved for the ultra-wealthy within everybody's reach — company formation that keeps pace with wallets, multisigs and launch calendars. Use this list early. Launch week is a terrible time to invent structure.
How to use this legal checklist for token launch
Work the sections in order. You do not need every box for every project, but you do need a written answer for each one you skip. "We'll figure it out after TGE" is not an answer — it is a future diligence email.
- Define what the company is for.
- Form the entity and lock ownership.
- Write an operating agreement that understands wallets.
- Get an EIN and prepare tax reporting.
- Open banking or fiat rails.
- Move IP, domains, accounts and treasury into the company.
- Align onchain permissions with offchain records.
- Prepare the diligence pack before anyone asks.
- Get advice on the token distribution itself.
If you want the broader formation playbook first, start with our 2026 crypto LLC guide.
1. Decide what the company owns — and does not own
Before Wyoming, Delaware or any filing fee, write one sentence: what is this company's job?
Is the LLC (Limited Liability Company — a legal wrapper with its own name, ownership rules and liability boundary):
- the operating company that builds software and signs vendor contracts?
- the IP holder for code, trademarks and domains?
- the treasury wrapper that holds or controls project wallets?
- a services company working for a DAO or foundation?
- a temporary bridge until a later structure appears?
If you cannot explain in one sentence what the LLC owns and what it does not own, you are not ready to form it yet.
Checklist:
- ☐ One-sentence company purpose written down
- ☐ Clear list of assets the company will own
- ☐ Clear list of assets that stay with a DAO, foundation or community
- ☐ Named people who can speak for the company
2. Form the right entity in the right place
For many US-facing crypto teams, the fork is still Wyoming vs Delaware.
- Wyoming — often the lean, crypto-aware default: lower ongoing cost, privacy-friendly formation, popular with remote teams.
- Delaware — often better when you expect US investors, enterprise counterparties or a later path toward a C-Corp (a corporation taxed separately from its owners, still the standard vehicle for many venture-backed startups).
You will also choose between a Series LLC and a standalone LLC. A Series LLC lets a master LLC host separate series — like compartments on a legal motherboard — each meant to keep its own assets and liabilities if maintained correctly. A standalone LLC is created by a filing event: the state registry receives and accepts formation documents. Instant series can be fast. Standalone filings may be easier for some banks and exchanges to verify.
Checklist:
- ☐ Jurisdiction chosen for the next counterparty you must impress
- ☐ Series/Instant vs standalone decision recorded
- ☐ Company formed and certificate stored
- ☐ Registered agent appointed
- ☐ Members / managers documented
3. Write an operating agreement that speaks wallet
The operating agreement is the LLC's private constitution. Generic templates almost never cover what token teams actually control.
Your agreement should answer:
- Who can control company wallets and Safe multisigs?
- Which addresses are company property?
- How are signers appointed and removed?
- Who owns code, domains, trademarks and social accounts?
- What approvals are required before minting, transferring or listing tokens?
- How are contributors compensated?
- What happens if a signer disappears the week before launch?
Onchain permissions and paperwork should reinforce each other. If the Safe says three of five and the agreement says two of three, you do not have a governance design — you have a future argument.
Checklist:
- ☐ Operating agreement signed by members
- ☐ Wallet / Safe control rules written explicitly
- ☐ Token approval thresholds defined
- ☐ IP and account ownership clauses included
- ☐ Signer change process documented
4. Get an EIN and prepare the tax layer
An EIN (Employer Identification Number) is the US tax ID for the company. You usually need it for banking, payment processors, hiring and tax forms.
Non-US founders can own US LLCs, but paperwork still exists. A foreign-owned single-member LLC may have information-reporting duties even when no US income tax is owed. One common requirement is Form 5472 — used to report certain transactions involving a foreign-owned US disregarded entity. "Disregarded" does not mean ignored; it means the IRS generally treats the company as not separate from its owner for income tax classification, whilst still requiring information reporting.
If you need an EIN without an SSN, follow our step-by-step guide: How to get an EIN for a US LLC without an SSN.
Checklist:
- ☐ EIN obtained and stored securely
- ☐ Tax classification understood (disregarded, partnership, election)
- ☐ Form 5472 relevance assessed for foreign owners
- ☐ Accounting method and recordkeeping started before launch revenue
- ☐ Counsel or tax advisor briefed on token timing questions
5. Open banking before the fiat questions arrive
Even a deeply onchain launch eventually meets invoices: legal fees, cloud bills, contractor payments, insurance, travel, or converting stables into dollars.
Banks and fintechs will ask for formation documents, EIN, operating agreement, beneficial ownership and a clear business description. Vague purpose statements ("Web3 stuff") and unexplained wallet stories are why onboarding stalls the week you need wires most.
For the remote stack, see How to get a US LLC bank account as a non-US founder.
Checklist:
- ☐ Banking or fintech application started early
- ☐ Formation docs, EIN and operating agreement ready for KYC
- ☐ Beneficial ownership answers match company records
- ☐ Business description that a compliance officer can understand
- ☐ Plan for contractor payments and legal invoices
6. Move assets into the company — especially the treasury
Forming the LLC does not automatically move anything into it.
If a founder wrote the contracts before formation, the IP may still sit with that founder unless assigned. If the treasury Safe was created personally, the company may not clearly own or control it. If the domain and X account were bought on a personal card, the company may not be the registered owner.
Checklist:
- ☐ IP assignment agreements from founders and key contributors
- ☐ Domain registrant updated to the company
- ☐ GitHub, app stores and social accounts under company control
- ☐ Treasury wallet / Safe ownership trail written down
- ☐ Vendor contracts novated where the company must be the counterparty
- ☐ Map of company-owned vs DAO/community-controlled assets
7. Align onchain permissions with offchain records
This is where token projects invent avoidable drama. The Safe, the admin keys, the mint role and the operating agreement should tell the same story.
Checklist:
- ☐ Multisig signers match authorised company actors
- ☐ Admin / upgrade / mint roles documented
- ☐ Key ceremony notes retained somewhere durable
- ☐ Emergency recovery path written (and tested once)
- ☐ Public claims about decentralisation match actual control
If your marketing says "community-owned" whilst three founders hold every admin key personally, the market is not the only party that may eventually care.
8. Build the diligence pack before listing week
Exchanges, market makers, auditors, grant programmes and counsel ask for a predictable stack. Assemble it before the clock starts.
Checklist — keep these in one folder:
- Certificate of Formation / Certificate of Organisation
- Operating agreement (current signed version)
- EIN confirmation letter
- Register of members / managers
- Beneficial ownership summary
- Registered agent details and company address
- Bank or fintech account confirmation (if available)
- IP assignment summary
- Wallet / Safe control summary
- Short plain-English description of what the company does
When someone asks "send entity docs," you should be able to reply in minutes — not start a scavenger hunt across Telegram DMs.
9. Get advice on the token itself
An LLC is not a securities-law force field. It does not make every token sale compliant, every airdrop consequence-free, or every jurisdiction comfortable with your distribution design.
Token launches can raise securities, commodities, money transmission, sanctions, tax and consumer-protection questions. The company wrapper helps you have a recognised actor, cleaner contracts and better operational hygiene. It does not replace counsel on whether, how and where you may offer a token.
Form the company so the project can operate. Get advice so the launch itself is not improvisation dressed up as decentralisation.
Checklist:
- ☐ Distribution design reviewed with counsel familiar with your markets
- ☐ Marketing claims checked against the actual legal structure
- ☐ Contributor / advisor token grants documented
- ☐ Sanctions and restricted-jurisdiction screening planned
- ☐ Tax timing questions logged before TGE, not after
Common misses we still see
Forming after the listing email arrives
Entity, EIN, banking and IP assignment take longer than a weekend. Start before the diligence clock starts.
Generic operating agreements
If the document never mentions wallets, signers or token permissions, it will not help when control is disputed.
Treasury still in personal names
If the company is supposed to own or control the assets, make that trail obvious in both documents and wallet permissions.
One LLC doing ten jobs
Operating company, IP holder, treasury and community vehicle are different roles. Force them into one box only when the documents and risk profile truly match.
Assuming formation equals compliance
Annual reports, registered agent fees, tax filings and signer updates keep the company alive. Legal entropy is real: do nothing and the offchain record drifts away from onchain reality.
Printable token launch legal checklist
- ☐ Company purpose defined in one sentence
- ☐ Jurisdiction and entity shape chosen
- ☐ Company formed; registered agent live
- ☐ Operating agreement covers wallets, signers and token approvals
- ☐ EIN obtained
- ☐ Tax reporting path understood (including Form 5472 where relevant)
- ☐ Banking / fiat rails started
- ☐ IP, domains and accounts assigned to the company
- ☐ Treasury control matches company records
- ☐ Onchain permissions aligned with offchain authority
- ☐ Diligence folder assembled
- ☐ Token distribution advice obtained
How OtoCo helps you clear the list
OtoCo exists because company formation should not be reserved for founders with expensive counsel, opaque agents and weeks of waiting.
With OtoCo, you can form a US LLC from your wallet, choose Instant or Standalone paths, request an EIN, and keep the company manageable as your project grows. The aim is not to make law disappear. The aim is to make the hard parts legible early enough that launch week is about the product — not a scramble for certificates.
When the wrapper is ready, form your company at otoco.io and join the community building the next version of the company onchain.
Disclaimer: This article is for general informational purposes only and does not constitute legal, tax or financial advice. OtoCo is not a law firm. Token launches can involve regulated activities. Consult your own advisors about your specific circumstances before forming an entity or launching a token.
