F-Tokens
F-Tokens develops open-source frameworks, methods, and reference architectures for building modular, upgradeable smart contract systems. Its kernel-orchestrated architecture keeps a small, stable core while installable modules handle evolving functionality, with namespaced storage isolation to prevent collisions. The frameworks are designed for long-lived on-chain systems that must change safely over years.
- Artificial Intelligence
- Blockchain & Cryptocurrency
- Developer Tools
- Software Only
- Web3 & NFTs
Funding
Founders
Product
Problem
Modern blockchain protocols are no longer single smart contracts but evolving systems of modules, permissions, storage domains, interfaces, and governance constraints. Developers struggle to build and upgrade these complex systems without risking storage collisions, unintended access to functions, or requiring full redeployment, which threatens the security and longevity of on-chain applications.
Solution
F-Tokens provides open-source frameworks, methods, and reference architectures for building secure, composable, upgradeable, and long-lived on-chain systems. The architecture centers on a small, stable kernel that governs routing, installation, upgrades, and lifecycle transitions, while all changing functionality lives in installable modules. Each module declares its identity, version, storage namespace, and exact callable surface, enabling installation, upgrade, and removal without redeploying the system or risking storage collisions. The frameworks include lifecycle hooks for boot, upgrade, and removal, making state transitions explicit and auditable, and are designed for systems that must evolve safely over years rather than single-shot deployments.
Target Audience
Primary users are blockchain developers and protocol engineering teams building complex, long-lived on-chain systems who need secure, modular architectures that can be upgraded and extended over time.
Features
- Kernel-orchestrated architecture with a small, stable core governing routing, installation, and lifecycle
- Installable and upgradeable modules that can be added, removed, or updated without system redeployment
- Namespaced storage isolation providing collision-free storage domains for each module
- Explicit interface surfaces where modules declare their exact callable functions, preventing accidental access
- First-class lifecycle hooks for boot, upgrade, and removal to make state transitions auditable
- Open-source, permissively licensed frameworks designed to be inspected, forked, and extended