Scalaris | An upgraded version of Tendermint
Scalaris | An upgraded version of Tendermint
Scalaris | An upgraded version of Tendermint
  • Scalaris: High-Performance, Leaderless, Parallel, and MEV-Mitigated Consensus Framework
  • Overview
    • What is Scalaris?
    • Introduction
    • Background
    • DAG-based Consensus
    • Narwhal: Achieving Scalability and Throughput
    • The Bullshark Protocol
      • Fairness and Garbage Collection in DAG-Based BFT
    • Mysticeti: Enhanced Consensus Protocol for Scalaris
      • DAG Structure
      • Consensus Protocol
        • Decision Steps
        • Commit Phase
        • Summary
    • Scalaris Framework
      • Parallel Consensus
      • Scalaris Architecture
        • Compatibility with ABCI and Cosmos SDK
        • Support for EVM Execution
        • Support for Move Language
      • MEV Mitigation in the Scalaris Framework
        • Understanding MEV Attacks
        • MEV in Old BFT-Based Blockchains
        • Scalaris Framework Mitigation
      • Parallel Transaction Execution for EVM in Scalaris Framework
        • Challenges with Parallel Execution
        • Parallel Transaction Executor (PTE)
        • General Scheme
        • Modular Architecture
        • Construction Process of Transaction DAG
        • DAG Execution Process
    • Conclusion
  • Guides
    • Install Scalaris
    • Quick start
  • Apps
    • Using ABCI-CLI
    • Getting started
    • Indexing transactions
    • Application architecture guide
  • Core
    • Using Scalaris
    • Configuration
    • Running in production
    • Metrics
    • Validators
    • How to read logs
    • Subscribing to events via Websocket
    • Block structure
    • RPC
    • Block sync
    • State Sync
    • Mempool
    • Light client
  • Network
    • Docker compose
  • Tools
    • Debugging
    • Benchmarking
  • Spec
    • Core
    • ABCI++
    • Consensus
    • Light client
    • P2C
    • RPC
    • Blockchain
  • Scalaris Quality Assurance
  • RPC
Powered by GitBook
On this page
  1. Overview
  2. Mysticeti: Enhanced Consensus Protocol for Scalaris
  3. Consensus Protocol

Decision Steps

PreviousConsensus ProtocolNextCommit Phase

Last updated 11 months ago

  1. Direct decision rule

  • The validator marks a slot as to-commit if it observes 2𝑓 + 1 commit patterns for that slot, that is, if it accumulates 2𝑓 +1 distinct implicit certificate blocks

  • The direct decision rule marks a slot as to-skip if it observes a skip pattern for that slot.

  1. Indirect decision rule: if the direct decision rule fails to determine the slot, the validator resorts to the indirect decision rule to attempt to reach a decision for the slot. This rule operates in two stages. It initially searches for an anchor, which is defined as the first slot with the round number (𝑟 ′ > 𝑟 + 2) that is already marked as either undecided or to-commit

  • If the anchor is marked as undecided the validator marks the slot as undecided (Figure 3d)

  • If the anchor is marked as to-commit, the validator marks the slot either as to-commit if the anchor causally references a certificate pattern over the slot (figure 3e) or as to-skip in the absence of a certificate pattern (Figure 3f)