Fogo primary sources — 2026-04-30

Project status in this pass

• No canonical standalone whitepaper or litepaper surfaced.
• The clearest current source of truth is Fogo’s official website, getting-started flow, developer docs, community docs, and public explorer.
• The project looks materially more concrete than a pure concept page because the public materials include live app-routing, wallet/session UX, and ecosystem/operator guidance, but most public framing still leans heavily on performance claims.

Primary-source snapshots

1) Official homepage

• URL: https://www.fogo.io/
• Key excerpt:
  • The homepage frames Fogo as a high-performance SVM Layer 1 “built for the speed of capital.”
  • It claims 40 ms block times, 1.3 s confirmation, gas-free sessions, and fair execution.
  • It says validators are colocated with major exchanges and that Fogo runs a custom Firedancer-based client while remaining SVM-compatible.
  • The positioning is explicitly trading-oriented rather than general-purpose smart-contract-chain marketing.

2) Getting-started flow

• URL: https://www.fogo.io/start
• Key excerpt:
  • The start flow says users can connect any SVM wallet, bridge assets in, inspect transactions on Fogoscan, and deploy capital across live applications.
  • It presents Fogo Sessions as the UX layer that removes repeated signing and direct gas payment from end users.
  • It links to concrete live surfaces such as Fogo Portfolio, Valiant, FogoLend, Pyron, Moonit, and the explorer.

3) Developer docs overview

• URL: https://docs.fogo.io/
• Key excerpt:
  • The docs define Fogo as a Layer 1 blockchain built for DeFi applications and based on Solana’s architecture.
  • They say Fogo implements multi-local consensus to minimize latency and uses a Firedancer-based client while maintaining full SVM compatibility.
  • The docs explicitly call out use cases like onchain order books, real-time auctions, precise liquidation timing, and reduced MEV extraction.

4) Community overview + docs query

• URL: https://community-docs.fogo.io/
• URL: https://community-docs.fogo.io/overview.md?ask=What%20does%20Fogo%20say%20about%20block%20times,%20finality,%20validator%20colocation,%20and%20the%20%24FOGO%20token?
• Key excerpt:
  • The community docs describe Fogo as the fastest SVM-compatible blockchain, built for speed, fairness, and performance.
  • They say the network targets 40 ms block times and 1.3 s finality.
  • They say the initial validators are physically located in the same high-performance data center to reduce latency.
  • They say the $FOGO token is used to pay transaction fees and secure the chain through staking.

5) Community ecosystem page

• URL: https://community-docs.fogo.io/getting-started/ecosystem.md
• Key excerpt:
  • The ecosystem page highlights a deliberately trading-centric launch set: Ambient, Valiant, Pyron, FogoLend, Brasa, FluxBeam, and Wormhole / Portal Bridge.
  • Ambient is especially important because the docs explain the project’s emphasis on fair execution and batch-auction market structure rather than raw speed alone.
  • This page makes clear Fogo is trying to launch with a full market stack, not just chain infrastructure in isolation.

6) Community FAQ

• URL: https://community-docs.fogo.io/getting-started/faq.md
• Key excerpt:
  • The FAQ explains that users may not see balances directly in their wallet extension and instead interact through Fogo Portfolio.
  • It says Fogo Sessions shifts transaction-fee burden from users to dApps via a paymaster model.
  • This is useful because it clarifies that “gas-free” is not literal fee elimination, but fee sponsorship and wallet abstraction.

7) Fogoscan explorer

• URL: https://fogoscan.com/
• Key excerpt:
  • The explorer is branded as a block explorer and analytics platform for Fogo and links back to docs, the main site, and community channels.
  • Even though the fetch snapshot was sparse, the public explorer reinforces that Fogo already has operational surfaces beyond a landing page.

Working conclusion

Fogo is best cataloged as low-latency SVM trading infrastructure with a gas-sponsorship wallet/session layer, not merely as another Solana-style Layer 1. The defining pattern is the combination of exchange-style latency claims, validator-colocation narrative, paymaster-backed session UX, and a trading-heavy day-one application stack.