SAFT Agreement

A SAFT (Simple Agreement for Future Tokens) is a forward contract between a project and an investor, obligating the project to deliver tokens at a future date — typically when the network goes live — in exchange for current payment in fiat or crypto. The investor does not receive tokens immediately; instead, they hold a contractual claim that converts to tokens upon network launch or a specified milestone.

Why SAFTs emerged as an alternative to ICOs

Early Initial Coin Offerings were unstructured: investors bought tokens on a project’s website, received them instantly, and traded them the next day. This created a problem for regulators and cautious lawyers. If a token traded on secondary markets before the product existed, was it a security? The uncertainty made mainstream investors and institutional backers wary.

SAFTs, introduced around 2017, tried to sidestep this by legally severing the sale from the distribution. The SAFT itself — a contract promising future tokens — is not a security under most interpretations (it’s a forward contract). Tokens, once delivered post-launch, could be dismissed as functional goods rather than investment contracts. This structure offered cover to both project teams and investors who wanted a path that looked compliant.

The SAFT’s structure and mechanics

A SAFT is a simple document. The investor commits to pay a set amount (usually in USD or Ether). The project commits to deliver tokens at a future date, calculated one of two ways:

Fixed conversion: Investor buys 1,000 tokens at $0.10 per token. On network launch, they receive exactly 1,000 tokens.

Discount (more common): Investor buys $10,000 worth of tokens at a 20% discount to the public offering price. If the public sale later happens at $0.20 per token, the SAFT holder receives 60,000 tokens (worth $12,000 at public price, but they paid $10,000).

SAFTs also typically included terms around what triggers delivery — network launch, regulatory approval, or a specified date — and occasionally a cap on total dilution or price-protection clauses.

Legally, the SAFT was sold primarily to accredited investors, since it had no registration exemption like Regulation A. This meant projects raised from wealthy individuals and institutions rather than the retail crowd that participated in ICOs.

The attempted regulatory finesse

The architects of the SAFT model believed they’d found a loophole. The token itself, once distributed, might be a security or might not — that question was unsettled. But the agreement to deliver tokens wasn’t a security; it was a forward contract, like a futures agreement.

This logic was intellectually honest but regulatory confidence was low. The SEC never blessed SAFTs explicitly. They were simply less visible and more defensible than ICOs. Institutions (venture funds, hedge funds) were willing to buy SAFTs because they looked more like traditional early-stage investment documents — signed agreements with clear terms, not website token buys.

SAFT adoption and the Filecoin model

Filecoin, a decentralized storage project, became the SAFT’s signature case study. In 2017, Filecoin raised $202 million using SAFTs sold primarily to accredited investors. The tokens didn’t launch for two years. When they did, the 200+ million tokens hit exchanges and token holders faced immediate massive dilution from token-generation events.

This sparked a broader concern: SAFT holders who bought at a steep discount and waited years for launch often faced secondary-market flooding. The discount advantage disappeared immediately as supply hit the market.

Still, SAFTs became the de facto standard for projects raising above $10 million. Andreessen Horowitz, Polychain Capital, and other tier-one crypto investors preferred SAFTs because they came with legal documentation and investor rights (liquidation preference in some cases, board seats in others).

Differences from ICOs and direct sales

An ICO sells tokens now. A SAFT sells a promise of tokens later. This creates three practical consequences:

1. Accreditation: Most SAFTs went to accredited investors only (net worth or income requirements). ICOs sold to anyone with a crypto wallet.

2. Discount pricing: SAFT investors typically received discounts of 10–50% versus eventual public sale prices, compensating them for locking capital and bearing execution risk.

3. Terms and conditions: SAFTs came with signed legal agreements, often including rights to request liquidation or token delivery under certain conditions. ICOs often had none.

Projects that raised directly from VCs using SAFE or equity convertible notes would later add a SAFT when they wanted a second round of fundraising from crypto natives at higher valuation.

The present state: SAFTs as a legacy instrument

SAFTs remain in use, but they are no longer the default model. Many projects have shifted to Regulation A compliant offerings, direct token sales under clearer regulatory frameworks, or community-driven token distribution (airdrops, staking rewards, liquidity mining).

The regulatory environment tightened after the 2017–2018 boom. The SEC took enforcement actions against projects that sold tokens without registration, and the SAFT’s legal protection proved less durable than its architects hoped. Token deliveries are now often subject to more explicit disclosure and sometimes explicit statements that tokens may not be securities, rather than implicit jurisdictional arbitrage.

That said, mature projects still occasionally use SAFT-like structures for private token sales to institutional investors. The document is useful. It’s just no longer the bridge between ICO chaos and full regulatory compliance that it once promised to be.

See also