Fogo

• Fogo is a Layer 1 built on the Solana Virtual Machine, targeting very low latency for high-frequency trading.

• It uses the Firedancer client and a zoned consensus design to reach sub-second finality.

• FOGO is the network token.

• Genesis supply of 10 billion FOGO, with about 39% unlocked at launch, including 6.6% for the airdrop and launch and 34% to core contributors vesting over four years.

• Used for fees, staking and governance.

Pros:

• SVM compatibility means Solana applications migrate with minimal changes.

• Latency targets are aimed squarely at a use case that current chains serve poorly.

• Uses production-grade client software rather than a novel implementation.

Cons:

• Zoned consensus concentrates validation geographically, which reduces decentralisation.

• Competes directly with Solana, which has the ecosystem it would need to take.

• In August 2026 an attacker obtained 400 million FOGO from the Fogo Foundation, more than 10% of circulating supply, and the team halted the mainnet in response.

• Exposure to a latency-focused chain with Solana compatibility.

• Migration path for existing Solana applications is straightforward.

• Weigh the decentralisation cost of the consensus design.

• Sub-second finality through geographically zoned consensus, targeting derivatives trading that current block times cannot support.

• Derivatives trading needs latency that even fast chains cannot deliver globally.

• Concentrating validators geographically cuts the latency, at a direct cost to decentralisation.

• Founding contributors include Doug Colkitt, with Robert Sagurton directing the Fogo Foundation.

• Backed by ecosystem investors including Distributed Global.

• Fogo sold 2% of supply in a public sale on Binance at a $350 million valuation, raising about $7 million ahead of its January 2026 mainnet launch, after an $8 million community round on Echo and an airdrop that replaced a cancelled presale.

• Geographic validator concentration is a real centralisation cost.

• Competes directly against Solana for the same developers.

• A foundation compromise in August 2026 forced a mainnet halt, and the attack vector has not been disclosed.

• Performance claims require sustained real load to verify.