Quick Answer
Fogo is a Layer 1 blockchain built for institutional-grade settlement. It leverages the Solana Virtual Machine (SVM), uses colocated validators for deterministic low-latency execution, and via that same low latency it eliminates MEV at the protocol level, whilst providing gasless transaction execution (at point of use) through Fogo Sessions. Built by veterans of Jump Crypto, Citadel, JPMorgan, and State Street, Fogo brings the infrastructure discipline of traditional high-frequency finance to on-chain settlement. Mainnet launched December, 2025.
Key Stats at a Glance
Metric | Value | Verified |
|---|---|---|
Block time | 40ms | Chainspect, Explorer |
Throughput | 99,825 | Chainspect |
Finality | 1.3s | Explorer |
Uptime | 100% | Since Dec 2025, mainnet |
Execution model | SVM (Sealevel, parralel) | Protocol |
MEV protection | Protocol-level | Protocol |
Gas model | Zero gas fees for users via Fogo Sessions | Protocol |
The Problem Fogo Solves
On-chain execution today carries three categories of risk that cost capital on every trade.
Execution Risk is latency variance. When confirmation time is unpredictable (400ms one block, 800ms the next), strategies can't execute at their intended price. Every additional millisecond between signal and settlement creates mark-to-market exposure. This is the on-chain equivalent of what co-location services exist to minimize in traditional finance.
MEV Risk is counterparty extraction. On most blockchains, profitable transactions are observable in the mempool before confirmation. Validators and MEV bots can insert transactions to capture value before your trade executes: front-running, sandwich attacks, back-running. This is a systematic transfer of value from legitimate liquidity providers to extractors. It shows up in worse fill prices, tighter market maker spreads, and reduced depth on AMMs.
Operational Risk is gas friction. Fee estimation, failed transaction costs, and unpredictable gas spikes under congestion. For programmatic strategies, per-transaction gas overhead accumulates. For autonomous agents, gas unpredictability requires defensive logic that adds latency and reduces performance.
Fogo has a specific mechanism for each:
Risk | Mechanism | Result |
|---|---|---|
Execution Risk | Validator Colocation + 40ms deterministic blocks | Latency variance eliminated |
MEV | Reduced by minimizing latency | Most front-running and sandwich attacks are eliminated at the protocol level |
Operational | Fogo Sessions (protocol-native session keys) |
|
Each of these features are live on mainnet.
How Fogo Works
SVM: The Execution Layer
Fogo runs the Solana Virtual Machine. Transactions execute in parallel through Sealevel; independent state updates don't block each other. The developer toolchain is compatible with Solana: same account model, same program structure, same parallel execution semantics.
For developers, this means existing Solana knowledge and programs are transferable. You're not learning a new execution environment. You're running SVM on infrastructure built to a different specification than Solana's.
Validator Colocation: The Infrastructure Layer
Traditional finance built co-location services decades ago. NYSE, CME, and most major exchanges let institutional traders rack their servers in the same data centers as the matching engine. The latency between order management systems and execution drops to microseconds. The industry built entire service categories around this because the performance differential is measurable and significant.
Fogo applies this to blockchain validators. Validators are colocated with institutional liquidity providers. The same infrastructure discipline that powers co-location in TradFi, applied to decentralized settlement.
Combined with deterministic block times, this bounds Execution Risk from both sides. Physical proximity sets a floor on latency. Deterministic block times set a ceiling on confirmation variance.
Dual Flow Batch Auctions: MEV Elimination
MEV requires time. A front-runner needs to see your transaction, build their own, and get it included ahead of yours. At 400ms block times, that window is workable. At 40ms, it mostly isn't.
Fogo's block speed is the mechanism. 40ms is not enough time for most extraction strategies to observe a pending transaction and act on it. The speed does the work.
Fogo Sessions: The Application Layer
Fogo Sessions are protocol-native session keys. A user or protocol authorizes a session by specifying: a spend cap (maximum value the session can move per asset), an asset whitelist (which tokens the session can touch), a time limit (expiry), and an action scope (which contracts and functions).
Within that scope, every transaction executes with zero gas. The session authorization has a one-time FOGO cost. After that, the execution is gasless until the session expires or the spend cap is hit.
For high-frequency applications and autonomous agents, this changes the economics fundamentally.
The Fogo Ecosystem
Applications live on mainnet alongside Fogo's core infrastructure are viewable here.
FOGO Token
FOGO is the native token of the Fogo blockchain. Three uses:
Gas token: dApps use FOGO to cover gas fees, rather than the user
Staking: Stake FOGO to participate in validator rewards and governance
Liquid staking: Convert FOGO → stFOGO/iFOGO via Brasa or Ignition for yield plus liquidity
How Fogo Compares
Fogo vs. Solana
Fogo and Solana share the SVM execution model. Everything else is different.
Fogo | Solana | |
|---|---|---|
Block time | 40ms | ~400ms |
TPS ATH | 99,825 (live mainnet) | 5,289 (live mainnet) |
Finality | 1.3s | ~12-14s |
MEV protection | Protocol-level | Limited (JITO tip market) |
Gas model | Zero for users via Sessions. Low for developers. | Per-tx SOL fee |
Validator design | Colocated | Distributed |
Solana's advantages are ecosystem depth and developer community size, neither of which Fogo matches yet. For applications where execution speed, MEV protection, or gasless sessions are requirements, Fogo's infrastructure is stronger.
Fogo vs. Hyperliquid
Hyperliquid is the dominant perps chain by volume (~70% of on-chain perps market share, $350B+ monthly). Its performance comes from a centralized matching engine. Execution is fast because there's no decentralized consensus overhead.
Fogo is a general-purpose L1 with decentralized consensus. Perps platforms on Fogo should expect to achieve Hyperliquid-competitive execution times via validator colocation and sub-40ms deterministic blocks, without the counterparty risk and custody assumptions of a centralized infrastructure. Applications built on Fogo also aren't limited to perps. The full programmability of a general-purpose SVM chain is available.
Fogo vs. MegaETH
MegaETH targets high-throughput EVM execution. MegaETH uses the EVM execution model; Fogo uses SVM. MEV protection on MegaETH is limited; Fogo endeavours to eliminate MEV at the protocol level.
Who Fogo Is For
Perps traders and market makers who compete on execution quality, not just strategy alpha. At sub-40ms with MEV elimination, the infrastructure stops being a constraint.
DeFi protocol builders who need a settlement layer their application can rely on. Predictable block times and deterministic finality simplify protocol design considerably.
Autonomous agents and AI trading systems that require predictable execution environments. Gas unpredictability and MEV exposure are existential problems for autonomous strategies; Fogo resolves both.
Institutional allocators evaluating on-chain capital deployment. The same infrastructure discipline that governs TradFi co-location applies here, built by people who came from that world.
Solana developers who want SVM compatibility with institutional-grade infrastructure. The toolchain transfers; the execution guarantees improve.
The Autonomous Capital Thesis
There's a broader argument behind Fogo's architecture.
The next generation of on-chain capital won't have a human at the keyboard. AI agents are already executing DeFi strategies. As the technology matures, the share of on-chain volume generated by autonomous systems will grow. These systems have different requirements than human traders: deterministic execution, predictable costs, no edge cases from gas estimation failures, permissioned sessions that constrain the agent's scope.
Fogo's architecture addresses all of these. Sub-40ms deterministic blocks mean execution timing is predictable. Fogo Sessions with spend caps and asset whitelists give agents a permissioning framework that limits downside from bugs or adversarial inputs. MEV elimination means agent fills aren't being extracted by validators.
Whether you believe the autonomous agent thesis or not, the infrastructure requirements it implies are the same requirements institutional human traders have always had. Building for that reality means Fogo ends up serving both.
Frequently Asked Questions
Is Fogo live on mainnet?
Yes. Fogo mainnet launched December, 2025. It has maintained 100% uptime since launch.
What is the FOGO token used for?
FOGO is the native gas token, the staking asset, and the base for liquid staking (stFOGO/iFOGO via Brasa or Ignition).
Is Fogo compatible with Solana programs?
Fogo runs SVM, so Solana programs are structurally compatible. Deployment configurations and RPC endpoints differ; a tiny amount of integration work is required, but you're not rewriting from scratch.
What is Fogo Sessions?
Protocol-native session keys that allow zero-gas execution within an authorized scope. You set spend caps, asset whitelists, and a time limit at session creation. Every subsequent transaction within that scope is gasless.
Who built Fogo?
Veterans of Jump Crypto, Citadel, JPMorgan, and State Street. The institutional trading infrastructure world, applied to blockchain.
How does Fogo compare to Hyperliquid?
Hyperliquid is an app-specific perps chain with centralized infrastructure. Fogo is a general-purpose L1. Valiant (Fogo's perps DEX) competes with Hyperliquid on execution quality while providing decentralized settlement and full SVM programmability.