Key takeaways
– A SAFT (Simple Agreement for Future Tokens) is a written contract under which investors provide capital to a blockchain project in exchange for the right to receive tokens at a future date if/when the network and tokens become functional.
– SAFTs were developed to help projects raise funds from accredited investors while attempting to address U.S. securities-law concerns, but whether any particular SAFT or token is a “security” depends on facts and law (Howey test and SEC guidance).
– SAFTs typically target accredited investors and require careful drafting (token description, delivery triggers, transfer restrictions, representations, and securities-law compliance).
– Both issuers and investors should obtain experienced securities and blockchain counsel, perform thorough due diligence, and evaluate token economics, regulatory risk, and exit/liquidity prospects.
What is a SAFT?
A Simple Agreement for Future Tokens (SAFT) is an investment contract: investors give money to a token developer today in return for a contractual right to receive tokens later—usually when the network is sufficiently developed and the tokens are “functional.” SAFTs were created as a standardized, relatively simple framework for funding blockchain projects while attempting to conform to securities laws by limiting initial sales to accredited investors and postponing token delivery until after network launch or other milestones.
How SAFTs facilitate cryptocurrency funding
– Upfront capital: SAFTs let developers raise funds before a network or token is operational, using investor capital to build the protocol and ecosystem.
– Deferred token issuance: Tokens generally aren’t delivered at signing; delivery depends on the issuer meeting development milestones or achieving a functioning network, which proponents argue distinguishes the token sale from a direct public offering of a security.
– Standardized terms: SAFT templates set out common clauses (token quantity, price, delivery conditions, representations/warranties) that streamline negotiations and documentation.
– Use with securities exemptions: Issuers typically rely on private-offering exemptions (for example, Regulation D Rule 506) and often limit sales to accredited investors to reduce registration burdens.
Key elements of a SAFT agreement
A properly drafted SAFT will normally include:
– Parties and definitions: issuer, purchaser, tokens, “token generation event,” “functional” token definition.
– Purchase amount and token economics: number of tokens or token-equivalent allocation, pricing mechanism, discounts, caps.
– Token delivery conditions: objective milestones or “token generation events” that trigger issuance (mainnet launch, minimum viable product, audited smart contracts).
– Transfer restrictions and resale conditions: restrictions designed to comply with securities-law resale rules and limit public distribution until exemptions apply.
– Securities-law representations and investor qualifications: purchaser representations (e.g., accredited investor, experience, risk tolerance).
– Use of proceeds / escrow or escrow alternatives: how funds will be used, whether funds are held in escrow or released on milestones.
– Tax, governance, and protocol risks: allocation of risk and tax treatment disclaimers.
– Remedies and dispute resolution: remedies, limitations of liability, jurisdiction.
– Confidentiality, intellectual property, and compliance covenants.
Is an SAFT a security?
– No universal answer. Whether a SAFT or the future token is a “security” depends on U.S. securities law tests (notably the Howey test) and agency/court guidance.
– The SEC has repeatedly said many token offerings are securities offerings (Report of Investigation: The DAO, 2017; subsequent enforcement actions). In practice, how the token is marketed, the expectations of purchasers, how proceeds are used, and whether the token becomes functional all matter.
– Because SAFTs are investment contracts that promise future tokens and investors expect profit from the efforts of others, many SAFT-based offerings have been considered securities or at least carry substantial regulatory risk.
– Conclusion: treat SAFT transactions as likely implicating securities law and plan accordingly—register or rely on a valid exemption, and obtain specialized legal advice.
Comparing SAFTs and SAFEs (Simple Agreement for Future Equity)
– Purpose: SAFE converts into equity at a future event; SAFT converts into tokens (digital assets) when the network or token is functional.
– Asset type: SAFE grants rights to company equity; SAFT grants rights to a future token or intangible digital asset.
– Legal/regulatory issues: SAFEs are governed by corporate and securities law; SAFTs additionally implicate the unique regulatory questions around crypto tokens (Howey analysis, resale restrictions, exchange listing concerns).
– Risk profile: Both are non-debt, high-risk instruments—no guaranteed return and potential total loss—but SAFTs have additional technological, regulatory, and market-liquidity risks.
SAFTs vs. token warrants
– Token warrant: gives the holder the right (but not obligation) to purchase tokens at a specified price/time in the future—similar to an option on tokens.
– SAFT: is an agreement promising delivery of tokens (or token-equivalents) upon satisfaction of conditions; it’s not merely an option because it represents a contractual right to receive tokens in exchange for current investment.
– Key difference: warrants are optional and priced as an option; SAFTs typically are straightforward purchase-like commitments to future tokens.
Practical steps for issuers (recommended workflow)
1. Engage specialized counsel early
• Securities, corporate, tax, and crypto-experience lawyers should advise on structure, exemptions (e.g., Reg D Rule 506(b)/(c), Reg S for offshore), and filings (Form D).
2. Decide target investor pool and exemption
• Most SAFTs are limited to accredited investors. Decide whether to use Rule 506(b) (no general solicitation) or 506(c) (general solicitation allowed if verification of accredited status).
3. Draft the SAFT carefully
• Define tokens, token-generation events, delivery terms, transfer restrictions, escrow/usage of proceeds, and investor representations. Use precise mechanics for how token amounts are calculated and delivered.
4. Establish investor verification and KYC/AML
• Implement accredited investor verification and anti-money-laundering checks consistent with chosen exemption and applicable laws.
5. Consider escrow or milestone releases
• Use escrow arrangements or milestone-based releases to build investor confidence and reduce regulatory scrutiny.
6. Prepare and file required notices
• File Form D (if relying on Reg D) and any other required notices; maintain careful records and consider disclosing the SAFT as needed.
7. Plan for post-token governance and secondary markets
• Adopt transfer restrictions or lockups, and plan for exchange listings, broker-dealer engagement, or other secondary-market pathways that respect securities laws.
8. Maintain transparent communications and documentation
• Keep investors informed about development milestones, audits, code security, and changes in plans.
Practical steps for investors (due-diligence checklist)
1. Confirm investor status and documentation
• Ensure you qualify as an accredited investor (SEC thresholds: e.g., $1M net worth excluding primary residence, or $200k annual income individually / $300k with spouse—verify current SEC guidance).
2. Read the SAFT and related disclosures thoroughly
• Confirm token definitions, delivery triggers, timelines, rights, restrictions, and remedies.
3. Evaluate project fundamentals and team
• Technology, roadmap, development milestones, token economics (supply, inflation, utility), partner integrations, and audit reports.
4. Assess legal and regulatory risk
• Ask whether the issuer obtained legal opinions regarding securities-law treatment, what exemptions were relied upon, and whether the token is expected to be non-security at issuance.
5. Confirm escrow and use-of-proceeds terms
• Prefer escrow or milestone releases to reduce counterparty and misuse risk.
6. Understand liquidity and secondary-market options
• Expect potential limited liquidity and resale restrictions. Ask about planned centralized or decentralized exchange listings and transferability constraints.
7. Tax and accounting review
• Determine likely tax treatment (income vs. capital), reporting obligations, and accounting for purchased rights.
8. Consider counsel and independent experts
• Use securities counsel and technical auditors to vet code and legal structure.
9. Watch for red flags
• Vague delivery milestones, overly broad representations, missing investor rights, absent KYC/AML, or aggressive marketing to non-accredited investors.
Risks to watch
– Regulatory risk: SEC enforcement actions and shifting regulatory landscape can lead to rescission offers, penalties, or forced token delistings.
– Execution risk: protocol may never launch, tokens may not have utility, or supply/economic design may fail.
– Liquidity risk: tokens received later may have minimal or no secondary market.
– Counterparty risk: issuer insolvency, misuse of proceeds, or fraud.
– Tax and reporting uncertainties: tax treatment of SAFT proceeds and eventual token receipt can be complex.
– Valuation and dilution: unclear token allocation and future issuance can dilute value.
Filing and disclosure: what issuers typically do
– Many issuers rely on exemptions under Regulation D (and file Form D) or Reg S for offshore offerings. Filing a Form D notifies the SEC of a private placement—it is not the same as registering a security under the Securities Act.
– Some projects have included token purchase agreements or SAFTs as exhibits in SEC filings; others publish SAFT templates for transparency. Always consult counsel to determine the correct filing strategy.
Real-world context and enforcement
– The SEC’s DAO Report (2017) declared that many ICO token sales were securities offerings and applied the Howey test to token sales.
– Subsequent enforcement actions (e.g., SEC v. Telegram) have reinforced that tokens and related instruments can be securities depending on how they were sold and used. These cases underscore why careful legal structuring and compliance are essential.
Bottom line
A SAFT is a contractual mechanism to fund a blockchain project today in exchange for the right to receive tokens later. While intended to manage regulatory risk by deferring token issuance and limiting sales to accredited investors, SAFTs still commonly implicate securities laws and carry significant legal, technical, and market risks. Both issuers and investors should approach SAFT deals only after thorough legal and technical due diligence and with clear plans for compliance, governance, and liquidity.
Selected sources and further reading
– Investopedia, “Simple Agreement for Future Tokens (SAFT)”
– U.S. Securities and Exchange Commission, “Report of Investigation: The DAO” (July 25, 2017)
– U.S. Securities and Exchange Commission, “Investor Bulletin: Initial Coin Offerings”
– SEC guidance and case law such as SEC v. Telegram and other ICO enforcement releases (search SEC website for specifics)
– For accredited investor definitions and Form D filing information: U.S. SEC – Rules and Forms (Regulation D/Form D pages)
Editor’s note: The following topics are reserved for upcoming updates and will be expanded with detailed examples and datasets.