awesome-repositories.com
Blog
awesome-repositories.com

Descubre los mejores repositorios open-source con nuestra búsqueda potenciada por IA.

ExplorarBúsquedas curadasAlternativas open-sourceSoftware autohospedableBlogMapa del sitio
ProyectoAcerca deCómo clasificamosPrensaServidor MCP
Aviso legalPrivacidadTérminos
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
·

7 repositorios

Awesome GitHub RepositoriesLight Client Synchronization

Methods for verifying chain state using minimal data from trusted nodes.

Distinguishing note: Focuses on light-weight state verification rather than full history synchronization.

Explore 7 awesome GitHub repositories matching data & databases · Light Client Synchronization. Refine with filters or upvote what's useful.

Awesome Light Client Synchronization GitHub Repositories

Encuentra los mejores repositorios con IA.Buscaremos los repositorios que mejor coincidan usando IA.
  • unionlabs/unionAvatar de unionlabs

    unionlabs/union

    73,961Ver en GitHub↗

    Union is an interoperability messaging protocol and trust-minimized asset bridge designed to transport data and instructions across diverse blockchain ecosystems. It provides a zero-knowledge cross-chain bridge and a state verifier that uses zero-knowledge provers and light clients to validate blockchain state transitions without relying on trusted intermediaries. The project features a WebAssembly blockchain runtime that hosts virtualized smart contracts and stacks for extensible network functionality. It employs a modular relayer architecture and a decentralized mechanism for moving assets

    Tracks external chain headers and validator sets to enable trust-minimized verification of remote network states.

    Rustastroblockchaincosmos
    Ver en GitHub↗73,961
  • ethereum/go-ethereumAvatar de ethereum

    ethereum/go-ethereum

    51,178Ver en GitHub↗

    Geth is a comprehensive execution client for the Ethereum network, serving as a foundational node implementation that processes transactions, maintains the distributed ledger state, and participates in peer-to-peer consensus. It provides a robust infrastructure for synchronizing, validating, and serving blockchain data, utilizing a persistent Merkle Patricia Trie database to ensure the cryptographic integrity of historical records. As a sandboxed smart contract runtime, it executes bytecode according to deterministic protocol rules, enabling the deployment and interaction of decentralized appl

    Connects to beacon nodes to verify chain state using finalized epoch checkpoints.

    Goblockchainethereumgeth
    Ver en GitHub↗51,178
  • rt2zz/redux-persist-storeAvatar de rt2zz

    rt2zz/redux-persist-store

    12,969Ver en GitHub↗

    Redux Persist is a state management utility designed to maintain application data across sessions by synchronizing state with local storage. It functions as a middleware-based engine that automatically saves and restores application state, ensuring that user sessions remain intact after page refreshes or application restarts. The library distinguishes itself through granular control over the persistence lifecycle and data structure. It supports recursive state tree partitioning, allowing developers to apply distinct storage configurations and filtering rules to specific branches of the applic

    Facilitates converting older versions of saved data into the current format before loading to ensure compatibility after application updates.

    TypeScript
    Ver en GitHub↗12,969
  • chia-network/chia-blockchainAvatar de Chia-Network

    Chia-Network/chia-blockchain

    10,827Ver en GitHub↗

    Chia is a decentralized blockchain platform that uses a proof-of-space-and-time consensus mechanism, enabling energy-efficient farming on commodity hardware. It implements a full blockchain node, farmer, harvester, timelord, and wallet in Python, prioritizing readability and cross-platform compatibility. The platform manages transactions through a simplified UTXO model that minimizes on-chain state and supports fast validation. The project introduces Chialisp, a Turing-complete functional smart contract language designed for secure and auditable financial transactions. It features a pooling p

    Implements an objective light client syncing protocol for fast blockchain state verification.

    Pythonblockchainblockchain-networkchia
    Ver en GitHub↗10,827
  • spesmilo/electrumAvatar de spesmilo

    spesmilo/electrum

    8,501Ver en GitHub↗

    Electrum is an open-source, non-custodial Bitcoin wallet client that manages keys, transactions, and balances using Simplified Payment Verification (SPV) for lightweight transaction verification without downloading the full blockchain. It operates through a persistent background daemon that exposes a JSON-RPC interface for wallet operations and automation, and generates wallet keys from a mnemonic seed phrase using hierarchical deterministic key derivation. The wallet distinguishes itself through support for cold storage security with offline transaction signing on air-gapped devices, integra

    Verifies transactions by checking block headers and Merkle proofs without downloading the full blockchain.

    Pythonbitcoinbitcoin-walletelectrum
    Ver en GitHub↗8,501
  • rrousselgit/riverpodAvatar de rrousselGit

    rrousselGit/riverpod

    7,315Ver en GitHub↗

    Riverpod is a reactive state management framework for Dart that manages application state through providers which automatically track dependencies and rebuild dependents when values change. It functions as an asynchronous data caching library, caching results of async operations and exposing loading, error, and data states to widgets without manual future handling. The framework includes a provider composition system that combines multiple providers into derived values that recompute automatically when any dependency changes, along with code generation for state providers that reduces boilerpl

    Replaces ChangeNotifier-based state with Notifier/AsyncNotifier to eliminate manual listener notifications.

    Dartdartflutterhacktoberfest
    Ver en GitHub↗7,315
  • ethereum/consensus-specsAvatar de ethereum

    ethereum/consensus-specs

    3,948Ver en GitHub↗

    This project provides the formal technical specifications and reference logic for the Ethereum proof-of-stake consensus layer. It defines the standards for block production, state transition rules, and the beacon chain logic required to ensure consistent network agreement. The implementation covers specialized mechanisms for chain security and efficiency, including fork-choice algorithms for canonical chain determination, committee-based signature aggregation, and KZG-based blob commitments for data availability. It also specifies the protocols for light client synchronization using sync comm

    Establishes protocols for low-resource nodes to verify chain state via sync committees and finalized headers.

    Python
    Ver en GitHub↗3,948
  1. Home
  2. Data & Databases
  3. Light Client Synchronization

Explorar subetiquetas

  • Bootstrapping PackagesProvision of data packages containing block headers and committee data for initial synchronization. **Distinct from Light Client Synchronization:** Focuses on the construction of the bootstrap package itself rather than the general synchronization process.
  • Data MigrationsProcesses for converting legacy client data and headers into current protocol versions. **Distinct from Light Client Synchronization:** Distinct from Light Client Synchronization: specifically handles the conversion of old data formats to new ones, not the verification process.
  • Forced State UpdatesRecovery mechanisms to advance light client state when expected updates are missing or delayed. **Distinct from Light Client Synchronization:** Specific to timeout-driven state advancement, distinct from general state verification or data exchange.
  • Header ConversionsTransformation of full blocks into condensed headers and Merkle proofs for light clients. **Distinct from Light Client Synchronization:** Specifically handles the data transformation from full block to light header, distinct from general sync logic.
  • Header VerificationsProcesses for validating the authenticity of block headers using cryptographic proofs like Merkle branches. **Distinct from Light Client Synchronization:** Focuses specifically on the verification of headers via Merkle proofs, a specialization of light client synchronization.
  • Light Client Data Exchange2 sub-etiquetasP2P transmission of finality updates and bootstrap data for light client synchronization. **Distinct from Light Client Synchronization:** Focuses on the P2P transmission of sync data rather than the internal verification logic of light clients.
  • Objective Verification ProtocolsProtocols for light clients to quickly verify blockchain state using objective proofs without downloading the full chain. **Distinct from Light Client Synchronization:** Distinct from Light Client Synchronization: specifically focuses on the objective verification protocol aspect rather than general light client sync methods.
  • State Migrations1 sub-etiquetaLogic for transforming legacy light client state data into current version formats. **Distinct from Light Client Synchronization:** Distinct from Light Client Synchronization: focuses on the structural transformation of state data for version compatibility.
  • State Store InitializationSetup of the local state storage using trusted checkpoints and bootstrap objects. **Distinct from Light Client Synchronization:** Focuses on the local storage setup for light clients specifically, rather than general chain synchronization.
  • State Update GenerationLogic for producing attested headers and signatures to advance the view of a light client. **Distinct from Light Client Synchronization:** Distinct from Light Client Data Exchange: focuses on the generation of update payloads rather than their P2P transmission.
  • Subjectivity-Based SynchronizationsSynchronization mechanisms that rely on a trusted checkpoint within a specific time window to prevent long-range attacks. **Distinct from Light Client Synchronization:** Focuses on trust-based checkpointing for security, whereas general Light Client Synchronization covers broader verification methods.