FluxFlux is a high-speed decentralized data layer for Web3. Cross-chain queries, sub-second latency, and ZK-proofed results—trustless, verifiable, and ready for real on-chain action. Fast, cross-chain, and provable—this is what real Web3 data should feel like.
Flux is designed as a high-integrity data execution layer, built to serve real-time systems that require speed, proof, and cross-chain consistency. It provides a query infrastructure that delivers verified results across multiple chains without relying on centralized trust.
Flux executes structured queries with cryptographic guarantees. Results are delivered in under 500ms, and attached proofs are generated instantly, enabling high-frequency logic on-chain.
With a single query language, developers can interact with Ethereum, Solana, Aptos and more. Schema normalization is built-in, removing the need for custom adapters or protocols.
Each response is probably tied to on-chain data sources. There's no TEE, no external trust dependency—just verifiable math and transparent computation.
Flux serves any system that needs data to be fast, verifiable, and available across chains. Whether on-chain or off-chain, Flux provides the same trustless interface to all execution environments.
Trigger financial actions with proof-backed data in <1 second. Flux feeds execution directly, not via oracles.
Monitor states and messages across chains, with a unified schema and full traceability.
Query real-time chain data with verifiable results directly from natural language or embedded SQL.
Build dashboards, alerts, or risk models that run on proof-backed data, not indexer assumptions.
Serve analytics, vault stats, or governance history from Flux APIs without building custom pipelines.
Compare L1/L2 vaults, activity, or TVL using unified models from Ethereum, Solana, Aptos, etc.
Executes your query and proves it's correct. Flux runs SQL or GraphQL queries inside a custom zero-knowledge engine. As it computes, it generates a cryptographic proof that shows the data was processed honestly.
Let anyone double-check the result — on-chain or off-chain. Smart contracts or apps can use Flux's lightweight verifier to confirm a result's origin and correctness, without trusting any centralized system.
Keeps a secure record of each verified query. After a query is validated, its key details—inputs, output hash, and proof—are stored on a tamper-proof ledger. This makes results permanent, traceable, and usable across systems.
$FLUX is the native utility token that fuels the Flux network's verifiable data layer. It is used for query payments, validator staking, proof verification, and developer revenue sharing—creating a closed, incentive-aligned economy.
Core protocol development and Ethereum-first implementation
Public validation and early developer integration
Permissionless deployment and incentive activation
Network expansion and on-chain governance
Flux is a verifiable query execution network that delivers real-time, cross-chain data with cryptographic proofs—usable by smart contracts, AI agents, and automated systems.
Traditional endpoints provide raw data, but cannot prove its correctness. Flux treats queries as computation with provable integrity, generating zero-knowledge proofs alongside results.
Flux launches on Ethereum, with support for Solana, Aptos, and Arbitrum in the roadmap. All chains are normalized into a unified schema model for cross-chain compatibility.
A Capsule is a reusable module that defines a query, its schema, proof behavior, and pricing logic. Once registered, it can be invoked by contracts or apps and monetized via $FLUX.
Yes. Queries can be issued permissionless using Flux SDKs, the CLI, or visual tools. Users can also build and publish their own Capsules with custom access rules.
Each query returns a ZK proof. This can be validated independently via on-chain contracts or off-chain APIs, ensuring result integrity without reliance on infrastructure providers.
Validators verify proof correctness and commit results to the network. They stake $FLUX, earn fees per validation, and are subject to slashing if they misbehave.
Governance is executed via the Flux DAO. $FLUX holders can propose and vote on protocol changes, validator rules, treasury allocation, and Capsule-level parameters.
$FLUX is used for query fees, validator staking, developer monetization, and governance participation. It underpins both the execution and incentive layers of the network.
Yes. The SDK and testnet environment are live. Developers can build queries, verify outputs, and deploy integrations using Flux Studio, CLI tools, or REST/GraphQL interfaces.