Contract under which a purchaser funds a project in exchange for future token delivery, subject to offering, delivery, resale, and project risks.
A Simple Agreement for Future Tokens (SAFT) is a contract under which a purchaser provides capital now in exchange for the issuer’s promise to deliver crypto tokens later, usually after a network launch or another specified event. A SAFT does not automatically make a token financing legal or exempt: the agreement, the capital-raising transaction, the future token delivery, and any planned resale must be analyzed under the applicable law.
A SAFT separates the initial funding from the planned token delivery:
flowchart LR
A["Purchaser provides capital"] --> B["Issuer signs SAFT obligation"]
B --> C["Issuer develops network or product"]
C --> D{"Delivery condition met?"}
D -->|"Yes"| E["Tokens delivered under contract terms"]
D -->|"No"| F["Delay, termination, refund, or loss under stated remedies"]
E --> G["Use, custody, and resale rules analyzed separately"]
The issuer often uses the capital to develop software, hire staff, obtain licenses, market the network, or build operating infrastructure. In return, the purchaser receives a contractual claim whose value depends on the issuer performing over time.
The word “simple” should not be taken literally. SAFT economics and legal consequences can be complex, especially when the token does not yet exist, the delivery event is uncertain, or the issuer expects purchasers to resell into a broader market.
| Contract term | What it controls | Risk if unclear |
|---|---|---|
| Purchase amount | Capital paid at signing | Funding and refund disputes |
| Token calculation | Number of tokens, fixed price, discount, or valuation mechanism | Unexpected dilution or fewer tokens than modeled |
| Delivery event | Network launch, token generation, financing, or other milestone | Issuer may claim delivery is due before meaningful functionality exists |
| Long-stop date | Deadline for delivery or termination | Capital can remain tied up indefinitely |
| Failure remedy | Refund, conversion, termination payment, or no recovery | Purchaser may be an unsecured claimant after failure |
| Transfer restriction | Whether and when the SAFT or tokens can be transferred | Expected liquidity may be unavailable |
| Issuer representations | Statements about entity authority, code, rights, and compliance | Limited recourse if key claims are omitted |
| Token rights | Functionality, governance, supply, minting, and economic rights | Delivered asset may differ from marketing expectations |
| Governing law | Forum, dispute process, and applicable law | Enforcement may be expensive or impractical |
The contract should also address taxes, sanctions, purchaser representations, wallet instructions, lost-key events, forks, protocol changes, confidentiality, amendments, assignment, and priority after insolvency where relevant.
In the United States, a SAFT used to fund development will often require analysis as an investment contract under the Howey Test. The purchaser contributes capital to a project and commonly expects a return tied to the development team’s future work.
If the SAFT is a security, its offer and sale generally must be registered under the Securities Act of 1933 or qualify for an exemption. Some issuers use SEC Regulation D, but the specific rule matters:
Other federal or state exemptions may be possible. The label SAFT supplies no exemption on its own.
An Accredited Investor meets specified financial, professional, or entity criteria under securities rules. Status can affect eligibility for certain Regulation D offerings, but it does not establish that:
Issuer evidence should show which exemption was selected, why each purchaser qualified, what verification was performed, and how resale restrictions were communicated and enforced.
The SAFT and the delivered token are different instruments, but that does not mean regulators or courts must view each step in isolation. The complete scheme can include initial fundraising, project development, token delivery, promoter marketing, exchange access, and expected secondary distribution.
The Telegram litigation illustrated this risk. Telegram sold agreements for future Grams to initial purchasers and planned a later token delivery and wider distribution. The federal district court analyzed the planned sequence as one scheme for purposes of the preliminary injunction rather than accepting that the private first stage automatically insulated the later distribution.
The SEC’s March 2026 crypto-asset interpretation now explains that a non-security crypto asset can be subject to an associated investment contract and may separate from that contract in specified circumstances. Separation depends on whether purchasers continue reasonably to expect profits from the issuer’s promised essential managerial efforts. It is not guaranteed merely because tokens were delivered or a network launched.
Assume an investor pays $100,000 under a SAFT. If the network launches, the contract prices the tokens at 80% of the public launch price. At a $1.00 launch price, the contractual price would be $0.80 and the purchaser would receive 125,000 tokens, subject to the agreement’s caps, adjustments, and lockups.
This discount is not a guaranteed gain. At delivery:
If the project fails before launch, recovery depends on the SAFT’s termination terms, remaining issuer assets, claim priority, governing law, and enforcement costs. A stated refund right is only as valuable as the obligor’s ability and willingness to pay.
| Instrument | Purchaser initially receives | Future event | Main analytical focus |
|---|---|---|---|
| SAFT | Contractual right to future tokens | Token generation or other delivery condition | Token terms, delivery, offering exemption, and later distribution |
| SAFE | Contractual right designed to convert into future equity under stated terms | Equity financing or another conversion event | Conversion mechanics, capitalization, dilution, and equity rights |
| Direct token sale | Token delivered at or near purchase | Usually no separate delivery event | Current functionality, rights, offering structure, custody, and transfer |
| Token warrant | Option-like contractual right to acquire tokens | Exercise after stated conditions | Exercise price, term, eligibility, and relationship to other financing |
A SAFT is not simply a SAFE with a different noun. Tokens may have no ownership claim on the company, and their supply, functionality, governance, custody, and regulatory treatment differ from corporate equity.
The Telegram item describes an enforcement action and allegations at filing. It is included as transaction-structure history, not as a current rule or a conclusion about unrelated offerings.
This article is educational and is not individualized legal, securities, regulatory, tax, accounting, technology, or investment advice. SAFT terms and crypto-asset law are fact specific and can change; review current primary sources and obtain qualified advice for a particular transaction.