Fuel Core is a production-grade Rust implementation of the Fuel blockchain node, serving as the execution layer for a modular rollup ecosystem. It operates as a full node with block production (PoA consensus via Redis leader lease), transaction pool, upgradable WASM-based execution, P2P networking (libp2p with gossipsub and request-response), an Ethereum relayer bridge, and a comprehensive GraphQL API for queries and transactions. The system uses a service-oriented architecture with clear port/adapter boundaries, allowing each subsystem (sync, compression, gas pricing, tx status management, etc.) to be independently tested and swapped. Key data flows include transaction submission through GraphQL or P2P gossip, verification by the txpool, inclusion in blocks by the producer, execution by the upgradable executor, and persistence to RocksDB. The codebase demonstrates high craftsmanship with clean abstractions, extensive integration and property-based testing, and a strong focus on performance and observability (Prometheus metrics, structured tracing). While it is primarily an application, it also includes research-grade components such as gas price algorithms (V0 and V1 with PD controllers) and block compression schemes.
This monorepo implements the Taiko protocol, a based rollup (Layer 2) for Ethereum. It is a production-grade infrastructure system comprising multiple services: a Go client (taiko-client) for block proposal, proving, and chain derivation; a Rust client (taiko-client-rs) for the same with additional preconfirmation support; a bridge UI (Svelte/TypeScript) for cross-chain token transfers; an event indexer (Go) that indexes on-chain events into a MySQL database with REST API; a relayer (Go) that processes bridge messages via RabbitMQ; an ejector (Rust) that monitors operator liveness and handles reorgs; and a balance monitor (Go) exporting Prometheus metrics. The architecture is microservice-oriented with shared protocol contracts (Solidity) in the protocol package. Key entry points include CLI binaries for each service, the bridge UI frontend, and deployment scripts for smart contracts. Data flows: L1 events are indexed by the eventindexer and relayer; the relayer processes bridge messages and submits claims; the driver derives L2 blocks from L1 proposals (blob sidecars) and syncs the execution engine; the prover generates and submits proofs (SGX, RISC0, SP1). External dependencies include Ethereum L1/L2 nodes, MySQL, RabbitMQ, IPFS gateways, and beacon chain APIs. The codebase is actively maintained with frequent releases and multiple audit reports.
This monorepo implements the classic Arbitrum optimistic rollup Layer-2 solution. The system consists of a custom Arbitrum Virtual Machine (AVM) written in C++, a Go-based node that provides an Ethereum-compatible RPC interface, sequencer/validator functionality, and Solidity smart contracts on L1 for bridge, rollup, challenge, and staking logic. Key data flows: the inbox reader ingests sequencer batches and delayed messages from L1, delivers them to the AVM for execution, and produces state updates and transaction results that are served via the RPC API. The architecture supports multiple node modes (forwarder, aggregator, sequencer, validator) with Redis-based lockout for sequencer exclusivity and optional Fireblocks integration for external signing. Despite being classified as 'classic' and superseded by the Nitro upgrade, the codebase continues to receive active maintenance and contains production-grade infrastructure for running Arbitrum nodes.
This is the original zkSync L2 scaling monorepo (zkSync Lite), implementing a ZK-rollup on Ethereum with low-gas ETH/ERC20 transfers, plus NFTs, swaps, and forced exits. The code is primarily a Rust backend with multiple binaries and services: the core state-keeper/committer (`zksync_core`), REST/JSON-RPC/Web3 API server (`zksync_api`), PLONK prover and witness generator, Ethereum transaction sender, event listener, data-restore tool, and exit-tree generator. It also contains Solidity smart contracts, JavaScript/Rust SDKs, a TypeScript integration test suite, and a large PostgreSQL storage layer with Diesel migrations. In production, the system receives L1 deposits and L2 transactions, validates them in a mempool, builds pending blocks in the state keeper, generates witnesses and proofs, and commits/verifies/executes blocks on Ethereum. The API exposes account, transaction, fee, and NFT endpoints, with WebSocket event notifications. The main external dependencies are Ethereum (via web3/ethabi), PostgreSQL, CoinGecko/CoinMarketCap price feeds, and custom `franklin_crypto`/`rescue`/`jubjub` zero-knowledge circuit libraries. The project is now in a deprecation/sunset phase: zkSync Lite is no longer the active product, and the `exit_tree_generator`/exit-tool paths exist primarily to help users withdraw funds. Architecturally, the monorepo is modular and contains several well-isolated patterns worth studying: a generic `Balancer` for channel-based load distribution, an async shared LRU cache, and generic serde wrappers for hex/BigUint/ratio serialization. These components demonstrate solid Rust engineering, but the repository also carries substantial legacy weight: multiple contract and schema versions, ignored tests, hardcoded development keys, old dependency versions, deprecated testnets, and a custom crypto fork. It is best treated as a reference for the original zkSync architecture or as a base for maintaining a sunset service, not as a codebase to absorb as a whole.
This repository contains the documentation for the X Layer blockchain network, an Ethereum Layer 2 solution. It provides educational resources, developer guides, and reference materials for building and interacting with X Layer. The content is organized into sections for developers (including building, deploying, and verifying smart contracts), academy (educational content on blockchain concepts), and various tools and infrastructure available on the network. The documentation follows a structured format using MDX (Markdown with JSX) components, with navigation defined in xlayer-docs.js. It includes tutorials for deploying smart contracts using popular frameworks like Hardhat, Foundry, and Truffle, guides for verifying contracts, explanations of blockchain fundamentals (ERC-20 tokens, Solidity concepts, gas fees), and information about integrating with third-party services such as oracles, node providers, and account abstraction solutions. While the repository contains valuable practical guides and tutorials, it suffers from several quality issues including inconsistent information about the underlying technology stack (referring to both Polygon CDK and Optimism Stack), a critical error in the testnet chain ID in one documentation file, outdated tool version examples, and some placeholder content. These issues reduce its reliability as a sole source of truth, though many of the core tutorials remain useful when cross-referenced with other official sources.