The Dual Asset Reality of Web3 Startups
In traditional technology startups, ownership is straightforward: you incorporate a Delaware C-Corp, issue shares to founders, set aside an option pool for employees, and sell preferred stock or SAFEs to investors. There is only one cap table, and every shareholder understands their exact percentage.
In Web3, almost every successful venture eventually operates across two distinct economic planes:
- The Operating Company (DevCo Equity): The corporate legal entity that hires engineers, leases offices, holds software copyrights, and pays payroll.
- The Protocol Network (Token Allocation): The decentralized network, autonomous foundation, and governance token supply that powers the protocol, incentivizes liquidity providers, and rewards community participants.
Investors want exposure to both. Early venture funds typically invest through a SAFE (Simple Agreement for Future Equity) paired with a Token Warrant or side letter. This gives the investor shares in the company if it raises a priced equity round, plus the contractual right to receive a percentage of tokens if a network launches.
Without careful mathematical alignment, managing these two assets simultaneously creates friction between founders, early employees, and incoming lead investors.
How Token Warrants Actually Work in Practice
A token warrant is not a token; it is a legal option. It grants the holder the right to receive a specified portion of future tokens issued by the protocol or an affiliated foundation, typically upon the occurrence of a Token Generation Event (TGE).
In the market today, token warrant clauses generally follow one of two legal formulas:
Formula A: Pro Rata Equity Matching
The investor receives a token percentage equal to their fully diluted equity ownership percentage in the DevCo at the time of token issuance.
Formula B: Fixed Percentage of Total Token Supply
The investor receives a fixed, predetermined percentage of the total initial token genesis supply (e.g., exactly 2.5% of 1,000,000,000 tokens), regardless of future equity dilution.
Choosing between these formulas has massive consequences for founders. Our Web3 Strategy & Cap Table Practice builds custom mathematical simulation models that show founders exactly how different term sheet clauses impact their personal net ownership under 50+ financing scenarios.
The Three Common Dilution Traps Founders Fall Into
1. The “Total Supply” Ambiguity Trap
If a token warrant states that an investor gets “5% of the token supply,” does that mean 5% of the tokens circulating at launch, 5% of the initial genesis mint, or 5% of an uncapped inflationary supply in perpetuity? Failing to define “Total Genesis Supply” in the legal contract can trigger lawsuits or forced renegotiations right before launch.
2. The Forgotten Foundation & Community Carve Out
In a successful decentralized network, between 40% and 60% of tokens must be allocated to public benefit causes: ecosystem grants, validator incentives, liquidity bootstrapping, and community rewards. If early investors and founders divide 80% of the token supply among themselves, the protocol lacks the community incentives needed to thrive. Always model the community pool first before dividing the remainder among insiders.
3. Employee Token Mismatch
Early engineers frequently receive offer letters promising “0.5% in tokens.” If their vesting schedule doesn’t align with investor lockups (e.g., a 1 year cliff followed by 36 month linear vesting), team members can end up with liquid tokens long before early investors or founders, creating severe morale and market stabilization issues.
Standard Web3 Token Allocation Benchmark
While every protocol is unique, institutional venture investors and top foundations expect token distributions to reflect healthy, decentralized governance. A standard baseline architecture looks as follows:
| Stakeholder Category | Target Allocation | Standard Lockup & Vesting |
|---|---|---|
| Community & Ecosystem Fund | 40% to 50% | Programmatic release over 4 to 6 years via on chain governance |
| Founding Core Contributors | 18% to 22% | 12 month initial cliff followed by 36 month monthly vesting |
| Early Investors (Pre Seed / Seed) | 12% to 16% | 12 month lockup, 24 month linear unlock schedule |
| Growth & Series A Investors | 8% to 12% | 12 month lockup, 24 month linear unlock schedule |
| Foundation Treasury Reserve | 8% to 12% | Governed by Cayman/BVI Foundation council under multisig |
Maintaining this balance requires strict coordination between your legal counsel and your fractional CFO team. If you haven’t finalized your legal entity structure yet, review our guide on Structuring Web3 Projects: DevCo and Offshore Foundations.
The Accounting Classification of Token Warrants
One critical element often overlooked until audit time is how token warrants appear on your balance sheet. Under modern accounting rules (specifically ASC 480 and ASC 815), token warrants must be evaluated to determine whether they qualify as equity instruments or derivative liabilities.
If a token warrant contains redemption clauses, settlement adjustments based on token price volatility, or obligations to deliver tokens that may never launch, auditors may classify the warrant as a balance sheet liability. This requires quarterly fair value recalculations, which can create huge non cash swings in your company’s net income.
Our partners work closely with leading crypto specialized audit firms (including Withum) to draft warrant language that avoids toxic liability treatment and maintains clean, predictable equity books. For more details on accounting reconciliations, consult our Digital Asset Accounting Guide.
Frequently Asked Questions
What is a dual asset cap table in Web3?
A dual asset cap table tracks two separate ownership layers simultaneously: traditional corporate shares (equity in the development operating company) and future rights to protocol tokens (governance or utility tokens distributed via warrants or token purchase agreements).
How does a Token Warrant differ from a SAFT?
A Simple Agreement for Future Tokens (SAFT) is an investment agreement strictly for tokens with no equity attached. A Token Warrant is an addendum or side letter typically attached to a traditional SAFE or preferred stock round, granting equity investors the contractual right to receive a pro rata share of protocol tokens if and when the protocol launches.
What is the biggest dilution mistake Web3 founders make in seed rounds?
The most common trap is promising token percentages based on fully diluted equity ownership without defining a maximum token supply or carving out separate pools for the foundation treasury, community incentives, and ecosystem grants. This often leaves founders with dangerously small token allocations at protocol launch.
Need Cap Table & Dilution Modeling for Your Next Round?
Overland builds dual asset cap tables, token warrant waterfalls, and investor data rooms to protect founder equity and ensure clean governance.