FIP-101: Fractal Standard Indexing Service
FIP-101 Roadmap
2025 Dec2026FebMarAprMayJunJulAugSepOct
2025 Dec2026FebMarAprMayJunJulAugSepOct

Phase 3: Public Testing

8

Stage 1: Capped Staking with Single Indexer

Public testing will begin with a controlled setup using a single indexer and capped staking participation. This stage is designed to validate the staking flow, reward release mechanism, and user participation process under limited conditions.

9

Stage 2: Multi-Indexer Testing

The system will expand to support multiple indexers, allowing third-party indexer participation to be tested in a broader environment. This stage will help validate proof submission, reward competition, and network behavior before the full rollout.

10

Continued System Optimization Based on Testing and Feedback

How To Participate

A Step Towards a Truly Permissionless Network

FIP-101 introduces the Fractal Standard Data Indexing Service,
which aims to strengthen the network by making the data layer more open, standardized, and economically aligned.

Building the infrastructure layer applications can depend on

Fractal was built to support Bitcoin-native assets and applications at greater scale. Faster blocks, Bitcoin-compatible infrastructure, and native asset support are important foundations. As the ecosystem grows, however, one layer becomes increasingly important: indexing.

Wallets, explorers, marketplaces, analytics tools, and application interfaces all rely on indexed data to understand balances, ownership, transfers, inscriptions, and protocol states. Without reliable indexing, users may see inconsistent information across products, while developers face a hidden infrastructure cost before they can even start building.

In many ecosystems today, indexing is still built and operated as application-specific infrastructure. Teams duplicate similar work. Products rely on private or centralized APIs. Edge cases may be interpreted differently across services. New builders often need to solve a complex data problem before they can ship a useful product. For an early ecosystem, this model can work for a while. But as usage grows, indexing becomes a shared dependency. And shared dependencies need stronger standards, broader participation, and better incentive alignment.

FIP-101 is designed around this problem.