Understand the project
Practical overview
When it fits
Use Flow Ft when a Flow or Cadence project needs a shared fungible-token contract model with resource-based storage, standard transfer behavior and capability-controlled withdrawals.
Who it is for
- Cadence developers creating fungible-token contracts on Flow.
- Wallet developers integrating Flow fungible tokens.
- Teams building Flow dApps or DeFi applications that accept standard-compliant tokens.
- Developers creating Cadence token-management tooling.
Documented uses
- Define a Flow fungible-token contract against a common interface.
- Store token balances as account-owned Vault resources.
- Transfer tokens through Provider and Receiver capabilities.
- Build wallet and dApp integrations that interact with conforming tokens.
- Use generic transaction templates for token interactions.
Before you choose
Requirements & limits
The repository is publicly accessible on GitHub and is published under the Unlicense. The standard contracts are documented as deployed on the Emulator, Testnet, Sandboxnet and Mainnet.
- Cadence is required for implementing the documented contract interfaces.
- Token balances use UFix64 with eight decimal places and no negative values.
- Each token-owning account stores a Vault resource.
- Provider capabilities can grant persistent or ephemeral withdrawal access, with custom contract logic able to govern withdrawals.
- The standard contracts are already deployed on the listed Flow networks.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Evidence and transparency
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 2 October 2026
- Original website title
- onflow/flow-ft · Official homepage title · retained in its source language