A modular Layer-2 rollup launched on Ethereum mainnet in November 2024 that uses the Solana Virtual Machine (SVM) for execution, Celestia for data availability, and RISC Zero for zero-knowledge proofs. Eclipse brings SVM's parallel execution performance to Ethereum users with faster speeds and lower fees, hosting 60+ dApps across DeFi, gaming, and digital services.
Comece pela explicação mais curta e útil antes de aprofundar.
A modular Layer-2 rollup launched on Ethereum mainnet in November 2024 that uses the Solana Virtual Machine (SVM) for execution, Celestia for data availability, and RISC Zero for zero-knowledge proofs. Eclipse brings SVM's parallel execution performance to Ethereum users with faster speeds and lower fees, hosting 60+ dApps across DeFi, gaming, and digital services.
Use primeiro a analogia curta para raciocinar melhor sobre o termo quando ele aparecer em código, docs ou prompts.
Pense nisso como parte da engrenagem que mantém a ordenação, execução ou consenso da rede funcionando.
Coloque o termo dentro da camada de Solana em que ele vive para raciocinar melhor sobre ele.
Consenso, rotação de líderes, slots, epochs e o runtime.
Transforme o termo de vocabulário em algo operacional para produto e engenharia.
Este termo destrava conceitos adjacentes rapidamente, então funciona melhor quando você o trata como um ponto de conexão, não como definição isolada.
Use este bloco compacto quando quiser dar contexto aterrado para um agente ou assistente sem despejar a página inteira.
Eclipse (eclipse) Categoria: Protocolo Base Definição: A modular Layer-2 rollup launched on Ethereum mainnet in November 2024 that uses the Solana Virtual Machine (SVM) for execution, Celestia for data availability, and RISC Zero for zero-knowledge proofs. Eclipse brings SVM's parallel execution performance to Ethereum users with faster speeds and lower fees, hosting 60+ dApps across DeFi, gaming, and digital services. Aliases: Eclipse L2 Relacionados: SVM (Máquina Virtual Solana), Rollup, Layer 2 (L2)
Use contexto do glossário, relações entre termos, modelos mentais e builder paths para receber respostas estruturadas em vez de output genérico.
Opcional: cole código Anchor, Solana ou Rust para o Copilot mapear primitivas de volta para termos do glossário.
O Copilot vai responder usando o termo atual, conceitos relacionados, modelos mentais e o grafo ao redor do glossário.
Esses ramos mostram quais conceitos esse termo toca diretamente e o que existe uma camada além deles.
The Solana Virtual Machine—the execution environment that runs on-chain programs. SVM loads SBF bytecode, provides syscalls for account access and cryptographic operations, enforces compute budgets, and manages memory. The SVM is being modularized (via the SVM API) to enable use in rollups and other environments outside the main Solana validator.
A Layer 2 scaling technique that executes transactions off-chain, bundles them, and posts compressed data back to L1. Optimistic rollups assume transactions are valid and use fraud proofs for disputes (7-day challenge period). ZK rollups generate cryptographic validity proofs for every batch. Rollups inherit L1 security while providing 10-100x throughput improvement.
A scaling solution built on top of a Layer 1 blockchain that processes transactions off-chain while inheriting the security of the base layer. L2 types include optimistic rollups (Arbitrum, Optimism), ZK rollups (zkSync, StarkNet), state channels, and sidechains. L2s post transaction data or proofs back to L1 for finality.
Estes são os próximos conceitos que valem abrir se você quiser que este termo faça mais sentido dentro de um workflow real de Solana.
Essas entradas são fáceis de misturar quando você lê rápido, faz prompting em um LLM ou está entrando em uma nova camada de Solana.
An ordered unit within a block containing a mix of PoH ticks and transaction batches. Each entry includes a PoH hash, a count of hashes since the previous entry, and zero or more transactions. Entries without transactions are tick entries that advance the PoH clock; entries with transactions prove those transactions occurred between two points in time.
Entradas de glossário só ficam úteis quando estão conectadas. Esses links são o caminho mais curto para ideias adjacentes.
The Solana Virtual Machine—the execution environment that runs on-chain programs. SVM loads SBF bytecode, provides syscalls for account access and cryptographic operations, enforces compute budgets, and manages memory. The SVM is being modularized (via the SVM API) to enable use in rollups and other environments outside the main Solana validator.
A Layer 2 scaling technique that executes transactions off-chain, bundles them, and posts compressed data back to L1. Optimistic rollups assume transactions are valid and use fraud proofs for disputes (7-day challenge period). ZK rollups generate cryptographic validity proofs for every batch. Rollups inherit L1 security while providing 10-100x throughput improvement.
A scaling solution built on top of a Layer 1 blockchain that processes transactions off-chain while inheriting the security of the base layer. L2 types include optimistic rollups (Arbitrum, Optimism), ZK rollups (zkSync, StarkNet), state channels, and sidechains. L2s post transaction data or proofs back to L1 for finality.
Essas entradas vivem ao lado do termo atual e ajudam a página a parecer parte de um grafo maior, não um beco sem saída.
A clock mechanism that cryptographically proves the passage of time between events. PoH uses a sequential SHA-256 hash chain where each output becomes the next input, creating a verifiable ordering of events without requiring consensus. The leader produces ~400,000 hashes per slot (~400ms), and any validator can verify the sequence in parallel, enabling Solana's high throughput by removing the need for validators to agree on time.
Solana's custom BFT consensus algorithm built on top of Proof of History. Tower BFT uses PoH as a clock to reduce communication overhead in traditional PBFT from O(n²) to O(n). Validators vote on forks with exponentially increasing lockout periods—each consecutive vote doubles the lockout, making rollbacks progressively more expensive. A fork is finalized when it reaches supermajority (66.7%+ of stake).
A time window during which a designated leader validator can produce a block. Each slot lasts approximately 400 milliseconds. Slots are numbered sequentially from genesis and grouped into epochs of 432,000 slots (~2-3 days). Not every slot produces a block—a skipped slot means the leader was offline or too slow.
A set of entries produced by a leader during a single slot. A block contains transactions bundled into entries, each with a PoH hash proving ordering. Blocks are broken into shreds for network propagation via Turbine. Maximum block size is limited by compute units (48M CU cap per block) rather than byte size.