> For the complete documentation index, see [llms.txt](https://docs.fractalbitcoin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fractalbitcoin.io/overview/fips/fip-101-fractal-standard-indexing-service/fip-101-faq.md). # FIP-101: FAQ ### **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. *** ### **Why permissionless indexing is genuinely hard** The goal of FIP-101 is not simply to have more teams run indexers, but to create an indexing network where independent operators can participate under a shared standard, and where the network can recognize valid indexing work and reward contributors. That is difficult for several reasons: * First, the indexing logic needs to be standardized. If different indexers follow different rules, the ecosystem does not get a common data layer. Wallets, explorers, marketplaces, and applications need to build around the same interpretation of network activity. * Second, the software needs to be accessible. A permissionless network only works if independent operators can realistically join. If participation requires heavy infrastructure or specialized internal knowledge, the system may be open in principle but limited in practice. * Third, the network needs a way to verify submitted indexing results. Without verification, incentives cannot be safely distributed, and the system has no reliable way to distinguish valid work from invalid submissions. * Fourth, the incentive model needs to be sustainable. Indexing is not a one-time contribution. It requires continuous operation, maintenance, and reliability. Operators need an economic reason to support this infrastructure over time. * Finally, indexing must not become a bottleneck for block production. The network needs to reward indexing work without making block generation depend on the immediate completion of indexing verification. *** ### **The lightweight indexer: making participation realistic** A key component of FIP-101 is the development of an open-source lightweight indexer. Permissionlessness depends on practical accessibility- if only well-resourced teams can run indexing infrastructure, the network may be open in theory but narrow in practice. A lightweight, open-source implementation lowers the operational barrier for independent operators, ecosystem teams, and technically capable community participants. It also gives developers a clearer reference implementation, reduces the cost of participation for operators, and creates a more consistent data foundation for applications. For the network as a whole, this increases the realistic possibility of a broader and more resilient indexing layer. *** ### **Integrating data indexing into Fractal’s block reward economy** The second major component of FIP-101 is economic integration. Instead of treating indexing as an external service that applications must separately fund or privately operate, FIP-101 incorporates indexing into Fractal’s block reward structure. Indexer operators can provide standardized indexing services, submit valid results, and receive rewards according to the network’s rules. FB holders can support indexers through staking, creating a direct economic relationship between token holders, operators, and the data infrastructure the ecosystem depends on. This is a meaningful design choice. Block rewards are one of the strongest coordination mechanisms in a blockchain network. By allocating a portion of rewards to indexing, Fractal recognizes that data infrastructure is not secondary to application growth. It is part of what makes application growth sustainable. The result is a more complete network economy. Miners secure block production. Indexers support standardized data availability. Stakers help allocate economic weight to indexer operators. Developers and users benefit from a more consistent infrastructure layer. Critically, index verification and reward settlement are kept off the block production critical path. This allows the network to support indexing as a rewarded role without compromising liveness. *** ### **What this means for the ecosystem** For developers, FIP-101 reduces one of the biggest hidden costs of building Bitcoin-native applications: maintaining reliable indexed data infrastructure. A shared indexing standard means less duplicated work and a clearer foundation for wallets, explorers, markets, analytics products, and future application layers. For users, better indexing means a more reliable experience. Balances, ownership records, and protocol states should feel consistent across products, rather than depending on which data provider a specific application uses. For FB holders, index staking creates a deeper connection to Fractal’s infrastructure layer. Supporting indexer nodes becomes a way to participate in maintaining the data infrastructure the ecosystem depends on. *** ### **Development status** FIP-101 is currently in Public Testing Stage 2. The lightweight indexer, staking mechanism, and reward distribution workflow are now live for public testing, allowing anyone to deploy an indexer, become an Indexer Operator, and participate in the Index Mining and Staking system. During this stage, the FIP-101 is validating the complete indexing lifecycle in a real network environment, including indexer deployment, proof submission, staking, and reward distribution. Feedback from operators and developers will continue to guide refinements as the protocol moves toward its official launch.