A SAFE is a short contract in which an investor funds a startup now in exchange for the right to receive shares later. It converts automatically into stock when the startup raises a priced round (c01, c02). Nothing in the instrument itself gives the investor tokens, warrants, yield, or blockchain exposure. A crypto company issuing a SAFE is issuing ordinary deferred equity. Token design may be relevant to investors, but it does not change the legal nature of the instrument.
That framing matters most for founders who conflate a token launch with a financing event. A SAFE sale is not a token pre-sale. The contract says when ownership arrives, not whether a token exists or what it is worth. The source material describes the tool and the paperwork, not token economics.
Why founders use it
The SAFE is the default instrument investors expect (c03). It is one short document, and the term founders usually negotiate is the valuation cap (c04). It has been used across thousands of startups and billions raised over more than a decade (c06). Y Combinator describes itself as the place the SAFE was invented, and says its version is the original and most current one (c09, c10).
YC also says the SAFE is the same instrument it uses to fund its startups, and that founders can send one in about two minutes for free through its own tool (c11, c12). The send tool is described as programmatic and agent-friendly, with a prompt that can install a CLI, log the user in, and walk through the commands (c14, c15, c17).
The ownership clause to watch
YC frames the central benefit of the post-money SAFE as transparency: the amount of ownership sold is immediately calculable for both founder and investor (c18). In practice, that means the valuation cap fixes the percentage an investor will own after conversion, rather than leaving final dilution to a formula the founder cannot see.
For a crypto startup with a token plan, the practical question is whether the cap reflects only equity or whether it also accounts for token supply, vesting, and future issuance. The SAFE text itself does not resolve that. Founders who want token economics to sit outside the SAFE should say so in a separate agreement. Otherwise, investors will reasonably assume the cap covers the whole business, token included.
Worked example (Hypothetical)
Assume a crypto startup raises a SAFE with a valuation cap of 4,000,000 and an investor puts in 400,000. On a post-money basis, the investor's implied ownership is 400,000 divided by 4,000,000, which equals 10 percent. That figure then applies after the later priced round, alongside other SAFEs and the new money, which is the transparency point YC makes (c18).
If a founder instead assumed the cap applied to equity only and planned a token pool of 20 percent of supply, the effective dilution of the founders' stake would be larger than the 10 percent headline suggests. The cap does not automatically carve out token allocations. Founders must check the cap against the entire cap table they plan to build, not just the equity line.
Comparison: SAFE versus a priced round
| Feature | SAFE | Priced round |
|---|---|---|
| What the investor gets now | The right to shares later (c01) | Shares at a stated price |
| When ownership is fixed | At the later priced round (c02) | At closing |
| Main negotiable term | Usually the valuation cap (c04) | Price, plus a wider set of terms |
| Ownership visibility | Calculable immediately, per YC (c18) | Fixed at closing |
The table shows why the instrument suits fast raises and why it defers the real conversation. A crypto startup raising a SAFE has not priced a round. It has promised a future conversion on terms set by a cap.
What the source does not say
- Nothing about tokens, token supply, or token allocation.
- Nothing about how a post-money SAFE should treat a token launch, if one occurs.
- Nothing on whether a SAFE can be sold, transferred, or used in crypto fundraising structures.
- Nothing on how the cap interacts with a future priced round in a jurisdiction that regulates token sales.
- Nothing on valuation, expected returns, or the likelihood of a priced round closing.
- Nothing on whether the send tool is suitable for regulated offerings.
Checklist before signing
- Confirm the document is the post-money version, so ownership is calculable up front (c18).
- Ask whether the valuation cap assumes equity only or a broader cap table.
- Decide in writing how tokens, if any, relate to the SAFE. The source does not cover this.
- Note that the investor's shares arrive at the next priced round, not at signing (c02).
- Keep a schedule of caps and amounts, since each SAFE's implied percentage depends on its own cap.
- Do not treat a signed SAFE as a token valuation or a guarantee of a future round.
The SAFE solves a paperwork problem: a short, standard contract investors recognize (c03, c04). It does not solve the crypto company's harder problem, which is explaining how equity and token ownership fit together. Founders should treat the post-money cap as a statement about the whole business, and negotiate any token carve-out explicitly rather than assuming the document covers it.