diff --git a/site/docs/faq.md b/site/docs/faq.md index 443126f6d..31688dba3 100644 --- a/site/docs/faq.md +++ b/site/docs/faq.md @@ -17,27 +17,27 @@ and endorser blocks (EBs) that validate them, enhancing the network’s capacity Leios offers several significant advantages: -- **Higher throughput and lower latency.** By splitting transaction processing +- **Higher throughput and lower latency:** by splitting transaction processing into IB and EB stages, Leios handles more transactions in parallel, enabling - faster and more responsive applications. -- **Better user experience.** Faster transaction processing means quicker - confirmations for wallet users and dApp interactions. -- **Flexible diffusion strategies.** Nodes can choose how to share blocks (e.g., - prioritizing newest or oldest data), optimizing network performance based on - conditions. -- **Enhanced cryptography.** Leios uses Boneh–Lynn–Shacham (BLS) signatures for + faster and more responsive applications +- **Better user experience:** faster transaction processing means quicker + confirmations for wallet users and DApp interactions +- **Flexible diffusion strategies:** nodes can choose how to share blocks (eg, + prioritizing the newest or the oldest data), optimizing network performance based on + conditions +- **Enhanced cryptography:** Leios uses Boneh–Lynn–Shacham (BLS) signatures for aggregated verification and verifiable random functions (VRFs) for fair leader - selection. -- **Robust simulations and formal methods.** Rust and Haskell simulations + selection +- **Robust simulations and formal methods:** Rust and Haskell simulations measure real-world performance, and executable specifications ensure - correctness. -- **Scalable cost model.** A cost calculator helps node operators estimate - expenses (e.g., storage, CPU usage). + correctness +- **Scalable cost model:** a cost calculator helps node operators estimate + expenses (for example, storage and CPU usage). -## What does Leios mean for Cardano users (e.g., wallet users, dApp developers)? +## What does Leios mean for Cardano users (eg, wallet users, DApp developers)? For everyday users, Leios means faster transaction confirmations and a smoother -experience in wallets and dApps—think near-instant payments or interactions +experience in wallets and DApps—think near-instant payments or interactions instead of waiting 20 seconds or more. For developers, it offers higher throughput (more transactions per second), enabling complex, high-volume applications like decentralized exchanges or gaming platforms. However, wallets, @@ -47,9 +47,9 @@ EBs, RBs), so expect some transition as it rolls out. ## What are the risks or trade-offs of Leios? Leios prioritizes scalability, but it’s not without trade-offs. Parallel -processing increases demands on node operators (e.g., more CPU, bandwidth, +processing increases demands on node operators (eg, more CPU, bandwidth, storage), potentially raising costs or requiring better hardware. The complexity -of three block types (IBs, EBs, RBs) could also introduce new bugs or delays +of the three block types (IBs, EBs, RBs) could also introduce new bugs or delays during implementation. However, extensive simulations and formal methods aim to minimize these risks, ensuring Leios remains secure and reliable as it matures. @@ -57,11 +57,11 @@ minimize these risks, ensuring Leios remains secure and reliable as it matures. Leios uses three distinct block types: -- **IB (input block):** a block that contains transactions. Produced by nodes +- **IB (input block)**. A block that contains transactions. Produced by nodes that win the IB sortition lottery. -- **EB (endorser block):** a block that references one or more IBs, providing +- **EB (endorser block)**. A block that references one or more IBs, providing endorsements. Produced by nodes that win the EB sortition lottery. -- **RB (ranking block):** a block that ranks or orders other blocks as part of +- **RB (ranking block)**. A block that ranks or orders other blocks as part of the consensus mechanism. Each block type plays a distinct role in moving transactions from submission to @@ -70,42 +70,46 @@ occur every ~20 seconds. ## What is the relationship between Ouroboros, Peras, and Leios? -### Ouroboros: The Foundation +### Ouroboros: the foundation - What it is: Ouroboros is the overarching family of proof-of-stake (PoS) consensus protocols that powers Cardano. It’s designed to be secure, energy-efficient, and provably fair, replacing proof-of-work (PoW) systems like Bitcoin’s. -- Key Features: +- Key features: - Slot-based time division (epochs and slots, with slots typically 1 second - long in earlier versions, now 20 seconds in Praos for block production). - - Stake pool leaders elected based on stake to mint blocks. - - Formal mathematical proofs of security (e.g., resistance to attacks like - double-spending or chain forks). + long in earlier versions, now 20 seconds in Praos for block production) + - Stake pool leaders elected based on stake to mint blocks + - Formal mathematical proofs of security (for example, resistance to attacks like + double-spending or chain forks) - Role: Ouroboros is the bedrock consensus mechanism that Peras and Leios build upon or refine. -### Peras: A Modular Upgrade +### Peras: a modular upgrade - What it is: Peras is a proposed evolution of Ouroboros aimed at improving efficiency and modularity. -- Key Features: - - Separation of Concerns: Peras splits consensus into modular components, such +- Key features: + - Separation of concerns. Peras splits consensus into modular components, such as transaction ordering, validation, and ledger state updates, to allow parallel processing and flexibility. - - Improved Finality: It introduces mechanisms for faster confirmation times, + - Improved finality. It introduces mechanisms for faster confirmation times. + - Separation of concerns. Peras splits consensus into modular components, such + as transaction ordering, validation, and ledger state updates to allow + parallel processing and flexibility. + - Improved finality. It introduces mechanisms for faster confirmation times, potentially reducing the time to finality compared to Praos’ 20-second block intervals. - - Adaptability: Designed to integrate with future scaling solutions (like + - Adaptability. Designed to integrate with future scaling solutions (like Leios) and sidechains or layer-2 systems. - Relationship to Ouroboros: - Peras is a direct descendant of Ouroboros Praos, refining its mechanics - while staying within the PoS framework. It’s like an “Ouroboros 2.0,” + while staying within the PoS framework. It’s like an 'Ouroboros 2.0,' optimizing the core protocol without fundamentally changing its PoS nature. - It serves as a bridge between the foundational Ouroboros Praos and more radical scalability-focused variants like Leios. -### Leios: A Scalability Leap +### Leios: a scalability leap - What it is: Ouroboros Leios is a specific variant of the Ouroboros family, designed to dramatically increase Cardano’s throughput (transactions per @@ -114,43 +118,43 @@ occur every ~20 seconds. research community. - Relationship to Ouroboros: - Leios is a specialized extension of Ouroboros, taking the core PoS mechanics - and rearchitecting block production for scalability. + and re-architecting block production for scalability. - It retains Ouroboros’ security model but reimagines how transactions are ingested and validated, making it a next-generation Ouroboros variant. -### The Relationship +### The relationship -- Ouroboros as the Core: +- Ouroboros as the core: - Ouroboros (especially Praos) is the foundational consensus protocol that defines Cardano’s PoS system. Both Peras and Leios are built on this foundation, inheriting its security properties and stake-based governance. -- Peras as an Intermediate Step: +- Peras as an intermediate step: - Peras enhances Ouroboros by introducing modularity and efficiency improvements, potentially laying the groundwork for integrating advanced features like those in Leios. It’s a stepping stone that refines Praos’ mechanics, making it more adaptable to future needs. -- Leios as a Scalability Solution: +- Leios as a scalability solution: - Leios takes Ouroboros further by addressing throughput limitations head-on. It uses the same PoS principles but introduces a parallel processing model that Peras’ modularity could theoretically support or complement. - - Leios can be seen as a “plugin” or evolution that fits into the Ouroboros + - Leios can be seen as a 'plugin' or evolution that fits into the Ouroboros ecosystem, possibly relying on Peras’ groundwork for smoother integration. -- Timeline and Evolution: - - Ouroboros Praos → Current live protocol - - Peras → A near-future refinement for flexibility and efficiency - - Leios → A long-term scalability solution, still in research/development, +- Timeline and evolution: + - Ouroboros Praos → current live protocol. + - Peras → a near-future refinement for flexibility and efficiency. + - Leios → a long-term scalability solution, still in research/development, aimed at making Cardano competitive with high-TPS blockchains like Solana or - Ethereum layer-2s + Ethereum layer-2s. ## What's the state of an IB before an EB or RB gets created for it? Is it visible, is it usable? -Before an Endorsement Block (EB) or Ranking Block (RB) is created, an Input -Block (IB) is a proposed set of transactions in a preliminary state. Here’s what +Before an endorsement block (EB) or ranking block (RB) is created, an input +block (IB) is a proposed set of transactions in a preliminary state. Here’s what that means: -### State of an Input Block +### State of an IB -An IB is minted by a node (e.g., a stake pool operator) and contains unconfirmed +An IB is minted by a node (eg, a stake pool operator) and contains unconfirmed transactions from the mempool. It’s cryptographically signed for authenticity but hasn’t been validated or finalized by the network, leaving it in a pending state. @@ -159,12 +163,12 @@ state. Once minted, the IB is broadcast and visible to all nodes. This allows them to inspect its transactions and start validation, a key part of Leios’ parallel -processing design. However, visibility doesn’t mean it’s accepted—it’s just a +processing design. However, visibility doesn’t mean it’s accepted — it’s just a proposal. ### Usability -The IB isn’t usable yet—its transactions can’t be spent or relied upon because +The IB isn’t usable yet — its transactions can’t be spent or relied upon because they lack consensus and finality. Only after EBs endorse it and an RB finalizes it does it become part of the blockchain’s official state. Until then, it could still be discarded if it fails validation. @@ -174,36 +178,34 @@ still be discarded if it fails validation. Leios boosts performance by processing transactions in parallel, even though final confirmation still takes 20 seconds. Here’s how: -### Parallel Processing Boost +### Parallel processing boost -Think of Leios like a factory: In Ouroboros Praos, one worker (a slot leader) +Think of Leios like a factory: in Ouroboros Praos, one worker (a slot leader) builds a block every 20 seconds. In Leios, dozens of workers (nodes) create -Input Blocks (IBs) continuously, others check them with Endorsement Blocks -(EBs), and a supervisor (Ranking Block, RB) approves the batch every 20 seconds. +IBs continuously, others check them with EBs, and a supervisor (RB) approves the batch every 20 seconds. This parallelism lets the network handle far more transactions in that -time—potentially 10x to 100x more than Praos. +time — potentially 10x to 100x more than Praos. -### Splitting the Work +### Splitting the work -- **IBs**: Propose transactions frequently and in parallel. -- **EBs**: Validate IBs concurrently across nodes. -- **RBs**: Finalize everything every 20 seconds, ensuring security. Unlike +- **IBs**. Propose transactions frequently and in parallel. +- **EBs**. Validate IBs concurrently across nodes. +- **RBs**. Finalize everything every 20 seconds, ensuring security. Unlike Praos, where one block does it all, Leios splits these roles so transaction processing isn’t bottlenecked by the 20-second RB interval. -### Practical Gains +### Practical gains While IBs aren’t spendable until an RB confirms them, EBs provide early confidence, letting apps (like wallets) act on them sooner for low-risk tasks -(e.g., showing balances). The 20-second RB is a security anchor, not a +(for example, showing balances). The 20-second RB is a security anchor, not a limit—hundreds of IBs can queue up in that window, massively increasing throughput. ## How does Leios maintain security with parallel processing? Leios preserves Cardano’s strong security by combining parallel transaction -processing with a sequential finality layer. Input Blocks (IBs) and Endorsement -Blocks (EBs) are produced in parallel, but Ranking Blocks (RBs) finalize the +processing with a sequential finality layer. IBs and EBs are produced in parallel, but RBs finalize the ledger every 20 seconds, ensuring a single, consistent chain. This prevents double-spending or forks by resolving conflicts at the RB stage. Additionally, cryptographic tools like BLS signatures and VRFs ensure that only valid blocks @@ -214,9 +216,9 @@ guarantees. Leios finalizes blocks through a structured voting mechanism. Nodes may adopt: -- **Single-stage voting:** all votes are broadcast in one phase, possibly - resulting in a longer CPU usage 'tail' during high throughput. -- **Send-recv (two-stage) voting:** votes are first sent, then a follow-up +- **Single-stage voting**: all votes are broadcast in one phase, possibly + resulting in a longer CPU usage 'tail' during high throughput +- **Send-recv (two-stage) voting**: votes are first sent, then a follow-up receive phase ensures broader propagation before final tallies. You can configure voting through parameters such as leios-vote-send-recv-stages @@ -233,9 +235,9 @@ sortition' because once a node proves it was selected to produce a block or vote Leios supports multiple strategies for propagating blocks and votes: -- **Oldest-first:** prioritizes older blocks or transactions -- **Freshest-first:** focuses on the newest blocks or transactions first -- **Peer-order:** requests blocks in the order peers announce them. +- **Oldest-first**: prioritizes older blocks or transactions +- **Freshest-first**: focuses on the newest blocks or transactions first +- **Peer-order**: requests blocks in the order peers announce them. Your choice of strategy can affect latency, network load, and overall throughput. @@ -253,11 +255,11 @@ sharding, but it is not yet part of Leios. Leios incorporates multiple cryptographic techniques to ensure security and efficiency: -- BLS signatures: allows efficient aggregation of many signatures into one, +- BLS signatures: allow efficient aggregation of many signatures into one, reducing verification overhead - Mithril or Musen protocols: used for voting and proof aggregation, depending on the context -- VRFs: ensures fair selection of nodes for block production +- VRFs: ensure fair selection of nodes for block production. Recent benchmarking shows that aggregated BLS verification significantly speeds up certificate validation. @@ -290,11 +292,11 @@ Developers continually refine these simulations based on real-world data. Based on preliminary internal testing and simulations: -- **Block size:** commonly set to about one-third of the available link capacity +- **Block size**: commonly set to about one-third of the available link capacity for IBs -- **Voting stages:** choose single-stage or send-recv, depending on reliability +- **Voting stages**: choose single-stage or send-recv, depending on reliability and speed requirements -- **Diffusion strategy:** many operators use 'freshest-first,' though +- **Diffusion strategy**: many operators use 'freshest-first,' though 'peer-order' may help maintain compatibility with older setups. Operators can adjust these parameters, which evolve through community votes. @@ -306,7 +308,7 @@ You can follow: - Weekly updates on the Ouroboros Leios site - Technical reports for deeper insights - Leios glossary for definitions of commonly used terms -- Public GitHub repositories that host source code and simulations +- Public GitHub repositories that host source code and simulations. These resources provide transparency and regular updates on ongoing development. @@ -315,9 +317,9 @@ These resources provide transparency and regular updates on ongoing development. Leios changes how transactions are validated and how blocks and memory pools operate, potentially affecting: -- **Wallets and SDKs,** which need to accommodate new block types (IBs and EBs) -- **Explorers,** which must handle higher throughput and multi-block referencing -- **Indexers and APIs,** which will see more granular block and vote data. +- **Wallets and SDKs**, which need to accommodate new block types (IBs and EBs) +- **Explorers**, which must handle higher throughput and multi-block referencing +- **Indexers and APIs**, which will see more granular block and vote data. Weekly updates provide a deeper analysis of these topics, including how advanced indexing and potential sharding solutions might eventually mitigate challenges. diff --git a/site/docs/how-it-works.md b/site/docs/how-it-works.md index 3d9e85f9b..1c9ce206f 100644 --- a/site/docs/how-it-works.md +++ b/site/docs/how-it-works.md @@ -2,47 +2,44 @@ sidebar_position: 3 --- -# How It Works +# How it works -Leios is a high-throughput overlay protocol designed to enhance blockchain -scalability, such as for Cardano’s Ouroboros, by managing a structured flow of -transactions. Here’s a breakdown of how it operates: +Leios is a high-throughput overlay protocol designed to enhance blockchain scalability — such as for Cardano’s Ouroboros — by managing a structured flow of transactions. Here’s a breakdown of how it operates: -1. **Creating Input Blocks (IBs)**:
Stake pool operators (SPOs), acting as - validators, bundle transactions into Input Blocks (IBs) every 0.2–2 seconds +1. **Creating input blocks (IBs)**
Stake pool operators (SPOs), acting as + validators, bundle transactions into IBs every 0.2–2 seconds and broadcast them across the network for parallel processing. -2. **Proofs of Data Availability**:
Validators check that IBs’ transaction - data is valid and accessible, a process later confirmed through Endorser - Blocks (EBs) and voting, ensuring no data is missing or malformed. +2. **Proofs of data availability**
Validators check that IBs’ transaction + data is valid and accessible, a process later confirmed through endorser + blocks (EBs) and voting, ensuring no data is missing or malformed. -3. **Generating Endorser Blocks (EBs)**:
EBs aggregate multiple verified +3. **Generating EBs**
EBs aggregate multiple verified IBs, grouping them for validation and proposing their inclusion in the blockchain’s final ledger. -4. **Pipelined Processing**:
The protocol uses a seven-stage endorsing +4. **Pipelined processing**
The protocol uses a seven-stage endorsing pipeline (detailed below) to process IBs, EBs, and votes in parallel, maximizing network bandwidth and throughput. -5. **Voting and Certification**:
Validators vote on EBs using +5. **Voting and certification**
Validators vote on EBs using stake-weighted BLS signatures to certify their correctness and data - availability, ensuring only compliant IBs (e.g., valid scripts) proceed. + availability, ensuring only compliant IBs (eg, valid scripts) proceed. -6. **Final Inclusion in the Blockchain**:
Certified EBs are referenced by - a certificate included in a Ranking Block (RB)—a Praos-style block minted +6. **Final inclusion in the blockchain**
Certified EBs are referenced by + a certificate included in a ranking block (RB) — a Praos-style block minted every ~20 seconds—finalizing IB transactions on the blockchain while maintaining a verifiable, efficient record. ## Leios architecture -The Leios protocol utilizes a pipelined architecture to achieve high throughput. -A pipeline instance comprises seven stages: +Leios uses a pipelined architecture to achieve high throughput. Each pipeline instance includes the following seven stages: 1. **Propose**:
- Validators concurrently generate and propose IBs with transaction data, - kicking off the pipeline instance and targeting frequent output (e.g., - every 0.2–2 seconds). + kicking off the pipeline instance and targeting frequent output (for example, + every 0.2–2 seconds) - IBs proposed during this stage are the focus of the current pipeline instance. @@ -50,21 +47,21 @@ A pipeline instance comprises seven stages: - Time is allocated for proposed IBs to spread across the network using a freshest-first diffusion strategy, ensuring honest nodes receive them - within a set delay (e.g., Δ_hdr) despite potential adversarial bursts. + within a set delay (eg, Δ_hdr) despite potential adversarial bursts - Duration is crucial for ensuring all honest nodes receive IBs before the next stage. 3. **Link**:
- - Validators create EBs that reference Propose-stage IBs, grouping and - ordering them for validation and eventual blockchain inclusion. + - Validators create EBs that reference propose-stage IBs, grouping and + ordering them for validation and eventual blockchain inclusion - EBs serve as containers for grouping and ordering IBs. 4. **Deliver2**:
- Time is allocated for any adversarial IBs referenced by EBs to disseminate, ensuring honest nodes have all data needed for fair voting and availability - checks. + checks - Ensures honest nodes have received all relevant IBs before casting votes. 5. **Vote1**:
@@ -77,33 +74,33 @@ A pipeline instance comprises seven stages: - New EBs reference Vote1-certified EBs, linking across pipeline instances to reinforce IB confirmation and ensure high throughput by cross-referencing - honest data. + honest data - Strengthens overall confirmation of IBs. 7. **Vote2**:
- - Validators cast final votes for Endorse-stage EBs, certifying them as + - Validators cast final votes for endorse-stage EBs, certifying them as Vote2-certified if they reference a majority of Vote1-certified EBs, - preparing them for RB inclusion and ledger finality. + preparing them for RB inclusion and ledger finality - Must reference a majority of Vote1-certified EBs. -## Network Resilience +## Network resilience Leios counters adversarial tactics with: -- **Freshest-First Diffusion**: Nodes prioritize downloading the newest IBs and +- **Freshest-first diffusion**: nodes prioritize downloading the newest IBs and EBs (via VRF-based timestamps), limiting delays from malicious message bursts. -- **Equivocation Proofs**: If a validator double-signs (e.g., sends conflicting +- **Equivocation proofs**: if a validator double-signs (eg, sends conflicting EBs), honest nodes detect and propagate proofs, ensuring only one valid block per slot is processed, minimizing bandwidth waste. ## Integration with Ouroboros -- Leios enhances Ouroboros Praos by overlaying its Ranking Blocks (RBs) with +- Leios enhances Ouroboros Praos by overlaying its RBs with high-throughput IB and EB processing. RBs, minted every ~20 seconds, anchor the ledger’s security, while Leios’ pipeline scales transaction capacity without altering Praos’ core settlement guarantees. This pipelined architecture ensures continuous IB generation, parallel processing, and robust confirmation, enabling Leios to achieve near-optimal -transaction throughput (e.g., (1-δ) of network capacity) while resisting +transaction throughput (eg, (1-δ) of network capacity) while resisting adversarial tactics like message bursts and equivocations. diff --git a/site/docs/resources.md b/site/docs/resources.md index 00183f666..9feec2d3a 100644 --- a/site/docs/resources.md +++ b/site/docs/resources.md @@ -18,56 +18,48 @@ technical papers, presentations, and videos. - Cardano’s mainnet periodically faces congestion, with block utilization exceeding 90%, delaying transactions and impacting user experience, especially for use cases like airdrops, DEXes, oracles, and DApps. As new applications - and bridges (e.g., Cardano-Midnight, Cardano-Bitcoin) increase demand, current + and bridges (eg, Cardano-Midnight, Cardano-Bitcoin) increase demand, current throughput (~12 TPS max) lags far behind competitors like Solana (7229 TPS). - In Ouroboros Praos, security constraints (e.g., 5-second block relay within a + In Ouroboros Praos, security constraints (eg, 5-second block relay within a 20-second slot) limit block size and script execution, underutilizing network resources. This CPS calls for research into scaling solutions like Ouroboros Leios to boost transaction volume, size, and execution units, while ensuring predictable processing times for time-sensitive applications. Goals include defining stakeholder needs, safely increasing limits, and leveraging underused - resources—all without compromising security or raising node costs. Historical + resources — all without compromising security or raising node costs. Historical data shows frequent near-full blocks and Plutus execution bottlenecks, underscoring the urgency as Cardano aims for nation-state-scale usage by 2030. ### Leios CIP -- [Leios CIP](https://github.com/cardano-foundation/CIPs/pull/379) - -#### Summary - -- – the Cardano Improvement Proposal by Duncan Coutts, -- CIP-0079, proposed by Duncan Coutts in November 2022, introduces Ouroboros - Leios as a long-term solution to boost Cardano’s transaction throughput beyond - the limitations of Ouroboros Praos. This CIP provides the rationale and a - high-level design of the protocol. - -### Leios Research Paper - -- [High-Throughput Blockchain Consensus under Realistic Network Assumptions](https://iohk.io/en/research/library/papers/high-throughput-blockchain-consensus-under-realistic-network-assumptions/) - -#### Summary - -- The original research defining the core protocol and its theoretical - properties. Published on May 31, 2024, by Sandro Coretti, Matthias Fitzi, - Aggelos Kiayias, Giorgos Panagiotakos, and Alexander Russell, this research - paper introduces Leios, a blockchain protocol overlay that transforms - low-throughput permissionless protocols (PoW or PoS) into high-throughput - systems, achieving near-optimal throughput of (1-δ)σ_H (where σ_H is the - honest stake fraction and δ>0) under realistic network conditions. Unlike - prior models assuming unbounded message capacity, Leios addresses adversarial - tactics like protocol bursts (mass message releases) and equivocations - (double-signing in PoS) using a freshest-first diffusion network model - (F_FFD). It employs five key techniques: (i) concurrent Input Block (IB) - generation for transactions, (ii) Endorser Blocks (EBs) with data availability - proofs, (iii) a pipelined architecture for uninterrupted processing, (iv) - freshest-first message prioritization with VRF-based timestamps, and (v) - equivocation proofs to limit malicious spam. Full Leios ensures throughput - scales with network capacity, retains base protocol settlement times (adjusted - by a δ-related constant), and supports dynamic participation, proven secure - with a stake-based voting scheme using BLS signatures. Applied to Ouroboros, - Leios offers a scalable, secure layer-1 solution for Cardano, balancing - throughput, latency, and resilience. +- [Leios CIP (CIP-0079)](https://github.com/cardano-foundation/CIPs/pull/379) — Cardano Improvement Proposal by Duncan Coutts, November 2022. + +**Summary** + +CIP-0079 introduces Ouroboros Leios as a long-term solution to raise Cardano +throughput beyond the limits of Ouroboros Praos. The CIP explains the rationale +and provides a high-level protocol design. + +### Leios research paper + +- [High-Throughput Blockchain Consensus under Realistic Network Assumptions](https://iohk.io/en/research/library/papers/high-throughput-blockchain-consensus-under-realistic-network-assumptions/) (May 31, 2024) — Sandro Coretti, Matthias Fitzi, Aggelos Kiayias, Giorgos Panagiotakos, and Alexander Russell. + +**Summary** + +The paper presents Leios, a protocol overlay that transforms low-throughput PoW +or PoS systems into high-throughput chains, achieving near-optimal throughput of +(1 − δ) σ_H (where σ_H is the honest-stake fraction and δ > 0). Leios addresses +adversarial tactics such as message bursts and equivocations via: + +1. Concurrent input-block (IB) generation +2. Endorser blocks (EBs) with data-availability proofs +3. A seven-stage pipeline for uninterrupted processing +4. Freshest-first diffusion with VRF-based timestamps +5. Equivocation proofs to cap malicious spam. + +Applied to Ouroboros, Leios yields a scalable, secure layer-1 for Cardano while +maintaining settlement guarantees and supporting dynamic participation. + ## Videos @@ -87,7 +79,7 @@ technical papers, presentations, and videos. - [December 2024](https://drive.google.com/file/d/1F07oKxBgdOEasGcstxEavkPCgr58sbIO/view?usp=sharing) - - [January 2025](https://www.youtube.com/live/6ovcWDCdqFU?si=-dgnvO7353tUyiDZ&t=120) + - [January 2025](https://www.youtube.com/live/6ovcWDCdqFU?si=-dgnvO7353tUyiDZ&t=120). ## Presentations