# Technical & Operational Q1: Why is Flux built on Solana?\ Flux requires a high-throughput environment to match the speed of modern financial data. Solana’s parallel processing (Sealevel) and low latency allow Flux to process and serve data in near real-time, a capability that is bottlenecked on EVM-based architectures. Q2: How is Flux different from traditional RPC nodes?\ RPC nodes provide raw, unstructured binary data (Instruction Logs). To make sense of this, developers usually have to build complex parsing logic. Flux does this heavy lifting for you. We provide structured, semantic data (e.g., "User PnL" instead of "Hex String"), saving developers hundreds of hours of backend engineering. Q3: What guarantees the accuracy of the data?\ Flux utilizes a decentralized consensus mechanism. Multiple Indexer Nodes process the same Projection logic in parallel. Before data is finalized, these nodes cross-validate their results. If a discrepancy is found, the divergent node is audited and potentially penalized (slashed). Q4: Can I build a Projection for a private or custom program?\ Yes. Flux is permissionless. As long as you have the IDL (Interface Definition Language) for the Solana program, you can write a Projection, stake $FLUX, and deploy it to the network to begin indexing immediately. Q5: How are costs calculated for Data Consumers?\ API usage is billed via Flux Credits. Queries are weighted by complexity—fetching a simple token balance costs fewer credits than calculating the historical PnL of a leverage trading position. Enterprise plans offer flat-rate access for high-volume users. Q6: Does Flux support historical data?\ Yes. When a new Projection is deployed, the Flux Engine can be configured to "Backfill" data, re-processing the Solana ledger from a specific slot height (Start Slot) to the present, ensuring you have a complete historical dataset. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.fluxtoken.vip/frequently-asked-questions/technical-and-operational.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.