LogoLogo
Developer Docs
Developer Docs
  • Platform Architecture
    • πŸ’ Introduction
  • πŸ’»Application Layer
    • πŸ™‹β€β™€οΈAlith - AI Agent Framework
    • 🏦DeFAI: AI-Driven DeFi
    • πŸ›’DAT Marketplace
    • πŸš€Agent Launchpad
  • πŸ›‘οΈTrust & Execution Layer
    • Consensus Protocol
    • Settlement Layer
    • Execution Layer
    • Data Availability Layer
  • πŸ–‡οΈExetention Layer
  • Data Anchoring Token (DAT)
    • 🧠Introduction
    • πŸ”DAT Specification
    • πŸ’ŽValue Semantics
    • πŸ“DAT Lifecycle Example
  • Quorum-based BFT Consensus
    • πŸ’ŽIntroduction
    • πŸ› οΈiDAO-Quorum Interaction
    • πŸ“Quorum-Based BFT Protocol
    • 🫡Slashing & Challenger System
    • πŸŒ€Quorum Rotation & Benefit
  • Verified Computing Framework
    • πŸ”·Overview
  • πŸ—οΈVerified Computing Architecture
  • Contract & Execution Flow
  • LAZAI Workflow & Runtime
    • 🧩E2E Process
    • βš™οΈPOV Data Structure
    • πŸ”΅AI Execution Mechanism
  • What's More?
    • πŸ”Data Protection
  • πŸ›£οΈRoadmap
  • πŸ†ŽGlossary
  • ⁉️FAQs
Powered by GitBook
On this page
  • Key Entities
  • Design Principles
Export as PDF
  1. Quorum-based BFT Consensus

Introduction

PreviousDAT Lifecycle ExampleNextiDAO-Quorum Interaction

Last updated 6 days ago

LazAI’s Quorum-Based BFT (QBFT) consensus is a modular and scalable consensus protocol optimized for AI-centric decentralized systems. It blends practical Byzantine Fault Tolerance (pBFT) with a Quorum-based voting mechanism to ensure efficient validation, integrity, and liveness in a multi-agent AI data network.

Key Entities

Component

Role

Quorum

A logical group of validators (iDAO members) responsible for data validation.

Proposer

A rotating member of the quorum responsible for proposing the next block/data state.

Validator

iDAO participant who verifies, signs, and votes on proposed blocks.

Challenger

External party capable of submitting fraud proofs or challenges.

Design Principles

  • AI Data-Aware Consensus: Handles metadata-rich, non-deterministic AI data (e.g., dataset hashes, ZK proofs, computation logs).

  • Quorum-Based Delegation: Only assigned quorums participate in consensus, improving scalability.

  • Dynamic Quorum Rotation: Quorum members are periodically re-elected or rotated for decentralization.

  • Hybrid Validity Layer: Supports ZK-SNARK/TEE proofs and Optimistic Proofs (OP) as validity inputs.

πŸ’Ž