I’ve seen founders get excited about tokenized equity—its promise of liquidity, broader investor access, and programmable ownership is tempting. But enthusiasm without a checklist can lead to painful dilution and legal entanglements. Before you deploy an equity token on an EVM chain, here are the questions I always ask (and have my teams answer) to protect founders and investors alike.
Is this actually equity—or a security under law?
I start with this because it frames everything else. Calling something a “token” doesn’t change its legal nature. If your token grants ownership rights, dividends, voting, or expectations of profit, many regulators will treat it as a security. I always consult counsel early—ideally a lawyer experienced in securities and crypto (examples: firms like Perkins Coie, Cooley, or boutique shops that specialize in tokenized securities).
- How will local regulators (US SEC, UK FCA, EU ESMA) view these tokens?
- Do we need to register or qualify an exemption (Reg D, Reg S, UK private placement rules)?
- What disclosure documents are required?
Getting comfortable on the legal classification prevents nasty surprises like forced buybacks, rescission rights, or fines.
How does the token map to traditional equity rights?
One of the biggest traps is ambiguity between on-chain tokens and off-chain legal entities. I always ensure there's a clear legal wrapper: whether tokens represent shares, convertible notes, or options should be documented in the cap table and the company’s articles.
- Are tokens merely a bookkeeping layer, or do they legally substitute share certificates?
- How will voting, dividends, and liquidation preferences be honored off-chain?
- What happens if the smart contract fails—do we have an off-chain remedy?
If tokens are supposed to represent real equity, use a tokenization provider like Securitize, Tokeny, or Carta’s emerging offerings to integrate tokens with your cap table and KYC/AML workflows.
How will dilution be handled—and who approves future token issuance?
Dilution is often misunderstood with tokens. On-chain, anyone with minting rights can dilute holders if governance is not explicitly controlled. I always ask:
- Who holds mint/burn/upgrade privileges in the smart contract?
- Are there on-chain restrictions (timelocks, multi-sig, governance votes) preventing unilateral minting?
- Is there an anti-dilution mechanism or pre-emptive rights for existing holders?
For me, a multisig (Gnosis Safe) and a timelock for upgrades are non-negotiable minimums. If you’re planning future raises, codify pre-emptive rights and caps in both the legal docs and the contract logic to avoid founder-friendly or investor-hostile surprises.
What’s the KYC/AML and investor accreditation plan?
Tokenized equity opens the door to global investors—but that’s also a regulatory minefield. I always make a plan that answers:
- Which jurisdictions are we accepting investors from?
- Will we accept retail investors, accredited/professional only, or a mix?
- What KYC/AML provider will we integrate (e.g., Onfido, Sumsub, Civic, or Securitize’s stack)?
If you skip KYC/AML, you risk violating sanctions or offering to prohibited persons. I prefer using established tokenization platforms that manage compliance workflows and hold legal opinions for offerings.
What EVM chain should we use—and why?
Gas fees, ecosystem liquidity, developer tools, and custody support differ dramatically across EVM chains. I weigh several factors:
- Transaction cost and speed (Ethereum mainnet vs Layer 2s like Arbitrum/Optimism vs alternatives like Polygon, BSC).
- Custody & institutional support (Coinbase Custody, Fireblocks) on that chain.
- Interoperability and bridge risks—will tokens be bridged cross-chain?
For many tokenized securities, a Layer 2 that supports EVM compatibility (Arbitrum, Optimism) or a regulated-friendly chain with lower fees makes sense. But if you plan to list tokens on exchanges, ensure the chosen chain is supported by major custodians and regulated platforms.
Which token standard fits our rights model?
Not all token standards are created equal. ERC-20 is simple but limited. Standards like ERC-1400 or ERC-3643 are designed for security tokens with partitioning, compliance hooks, and document hashes. I typically map rights to standards like so:
| Feature | ERC-20 | ERC-1400 / ERC-3643 |
|---|---|---|
| Basic fungible tokens | Yes | Yes |
| Transfer restrictions & compliance hooks | No | Built-in |
| Document linking & identity | External | Native |
| Designed for securities | No | Yes |
I recommend ERC-1400/3643 or a professionally audited implementation if you need on-chain compliance enforced at transfer time.
How will investor rights (voting, dividends) be enforced?
Programmate everything you can, but remember off-chain enforcement will still be needed. I always make sure:
- Voting records are tied to token ownership snapshots and legal registrations.
- Dividend or profit distributions have a clear mechanism (on-chain distributions vs off-chain payments reconciled to on-chain holders).
- There are fallback procedures if a holder’s wallet is lost or keys compromised.
Practically, that means integrating snapshot tools (e.g., Snapshot), a robust governance process, and legal agreements confirming that on-chain token holdings reflect real-world rights.
What about custody, custody providers, and cold storage?
Institutional investors will demand custody options. Retail platforms will require UX-friendly wallets. I always check:
- Which custodians support the chosen chain and token standard (Fireblocks, Prime Trust, BitGo)?
- What wallet support will retail investors have—MetaMask, hardware wallets, or hosted wallets?
- Are there insurance options for custody?
Failing to plan custody can cripple adoption. If investors can’t custody tokens safely or the custodian doesn’t support necessary compliance, you’ll lose capital before you raise it.
How will we handle upgrades, audits, and bug bounties?
Smart contract risk equals legal and financial risk. I never launch without:
- Professional audits (OpenZeppelin, ConsenSys Diligence, CertiK).
- Immutable or controlled upgrade patterns documented in legal agreements.
- Bug bounty programs and clear incident response plans.
Even with audits, have an emergency governance plan and insurance where possible. You don’t want a critical bug to cause dilution or lost rights.
Tax, reporting, and secondary markets—what’s our plan?
Tax authorities are increasingly focused on crypto. I always outline:
- How token issuance is taxed for the company and investors (income, capital gains, withholding).
- Reporting obligations for transfers and distributions.
- Whether secondary trading will be allowed, and on which regulated platforms.
Working with accountants familiar with tokenized securities prevents nasty surprises during audits. Also, if you enable secondary markets, ensure the platforms are compliant (e.g., regulated ATSs or token exchanges that support security tokens).
What are the exit mechanics and liquidity expectations?
Finally, be realistic about liquidity. Tokenization can increase potential liquidity but doesn’t guarantee it. I advise founders to ask:
- What liquidity events are expected (buybacks, token redemption, IPO, token listing)?
- How will transfer restrictions and lock-ups be enforced?
- What signals will the market need to trade these tokens confidently?
Plan for staged liquidity: start with a controlled investor base, onboard custodians and platforms, and consider market-making relationships if you want tradability sooner.
Launching a tokenized equity round can be transformative, but it demands rigorous legal, technical, and operational planning. Ask these questions early, involve the right advisors (legal, audit, custody), and map on-chain designs to off-chain legal realities. Do that, and you’ll minimize dilution risk and steer clear of legal traps that have tripped too many well-intentioned founders.