How Does the SAFT Model Attempt to Satisfy the “Functional Network” Test?

The SAFT model attempts to satisfy the "functional network" test by legally separating the investment contract (the SAFT itself) from the eventual delivery of the utility token. The SAFT is sold as a security to accredited investors under an exemption, raising the capital needed to build the network.

The utility token is only delivered once the network is demonstrably functional and decentralized. The argument is that at the time of delivery, the token is no longer an investment in a common enterprise but a consumable product, thus satisfying the functional network criteria and avoiding security classification for the token itself.

What Is the Legal Distinction between a Utility Token and a Security Token?
What Are the Alternatives to the SAFT Model for Compliant Crypto Fundraising?
How Does a SAFT (Simple Agreement for Future Tokens) Differ from a SAFE (Simple Agreement for Future Equity)?
How Do Regulators Determine If a Token Is a “Security” or a “Utility”?
Can a Token’s Classification (Utility Vs. Security) Change over Time?
How Does the ‘Expectation of Profit’ Element of the Howey Test Apply to Utility Tokens?
What Role Does Token Utility and Network Adoption Play in Determining Intrinsic Value?
What Is the Legal Difference between a “Pre-Functional” Token and a “Consumptive Use” Token?

Glossar