Recently, we’ve all noticed that numerous projects have started building blockchains using the Solana Virtual Machine (SVM). However, these projects are merely Layer 2 or sidechains of Solana, and none have yet to build a Layer 1 blockchain using SVM. Therefore, Fogo is introduced, offering several advantages, most notably being 100% SVM compatible.
Fogo is a layer 1 blockchain that utilizes the Solana Virtual Machine (SVM), offering high-performance capabilities in terms of transaction processing speed (TPS), latency, and congestion. Fogo aims to address the congestion issues plaguing Solana’s network, particularly during periods of high transaction volumes.
Fogo Blockchain is comprised of several critical components, including :
Protocol and clients
Multi-local consensus
Validator set
Perspectif extension
Let’s break down these terms in simple language to help newcomers understand and get started with building DApps on Fogo.
Fundamentally, Fogo leverages Solana’s established and extensively utilized protocol across diverse applications to optimize its speed. By concentrating on the utilization of a single canonical client, Fogo is able to achieve superior performance, as its network consistently operates at the speed of the fastest client.
Solana’s transaction processing also employs a client called Firedancer, developed by Jump Crypto, which offers high-performance capabilities compared to Validator clients in terms of parallel processing, memory management, and SIMD instructions. Currently, Fogo utilizes a hybrid form between Validator and Firedancer, known as Frankendancer, during development. Once the implementation is deemed sufficient, Fogo will transition to a pure Firedancer implementation.
Fogo introduces a novel approach to consensus execution, enabling validators to coordinate their physical locations and cryptographic data across epochs in different time zones. This allows the network to achieve consensus with ultra-low latency during normal operation, while seamlessly transitioning to global consensus when necessary.
In real-world scenarios, consensus processing can be optimized by adapting to transaction conditions at specific validator locations in real-time, facilitating consensus achievement despite high transaction densities in specific geographic locations. The algorithmic search for the fastest validator enables seamless transaction processing, akin to the sunflower’s movement following the sun’s trajectory, allowing transactions to flow continuously without hindrance.
To achieve high performance and mitigate excessive MEV attacks, Fogo selects trusted validators with a target of 20-50 validators at the initial genesis.
Each validator running a node is required to delegate a certain amount of tokens to be staked in order to meet the requirements to become a validator.
We’ve discussed a lot about the core of Fogo, such as multi-local consensus, client performance, and validator set. But we shouldn’t overlook the most crucial aspect of all blockchains: token payment fees.
Fogo implements a payer_fee_unsigned system, where users can perform transactions even if they don’t have SOL tokens as gas fees, but instead can use other tokens as gas fees to complete the transaction.
Wow, Fogo is implementing a system similar to chain abstraction to make it easier for users to pay gas fees with other tokens.
Example: Alice has assets of 0 SOL, 10 USDT, and 20 USDC. Then, Alice wants to send 10 USDT to Bob, so Alice can perform the transaction by sending 10 USDT using USDC as the gas fee.
The devnet session has been launched, conducting a series of experiments that have resulted in 25,000 TPS to 45,000 TPS. The testnet session is expected to start in Q1 if it is launched according to plan.
Special thanks for cute mascot and banner
Follow me
Join Fogo community
Discord : https://discord.gg/FogoChain
takanome
