dBOOK Whitepaper
  • Introduction
    • Overview
    • Why dBOOK?
    • Architecture
  • Service lifecycle
  • Core Components
    • Intelligence Engine
      • LLM
      • Model Context Protocol
    • Settlement Engine
      • Home Chain
      • Operators
      • Validators
      • Path Finder
      • Accounts
    • Recommendation Engine
      • Protocol & Metadata Registry
      • Context Module
  • Core Concepts
    • Hybrid Ranking System
    • Challenge Flow
    • Asset Accounting
    • Endpoints
    • Threshold Signatures
Powered by GitBook
On this page
  1. Core Concepts

Threshold Signatures

PreviousEndpoints

Last updated 6 months ago

dBOOK employs , a three round based threshold ECDSA protocol that provides superior bandwidth and latency performance.

Threshold ECDSA:

  1. Key Generation for creating secret shares

  2. Signing for using the secret shares to generate a signature

  3. Verification and validation of signatures using the knowledge of public keys

In MPC, a set of parties that do not trust each other try to jointly compute a function over their inputs while keeping those inputs private.

(TSS) is the name we give to this composition of distributed key generation (DKG) and distributed signing of a threshold signature scheme.

  • dBOOK validators utilises TSS based multi-party ECDSA for key generation, signing, verification and rotation

  • All the participating validators rotate their private key share over a fixed interval time T

  • Confirmation for bridging assets/information is dependent on the parent chain confirmation times

  • Light clients are used by the validators for verifying transactions on the parent chain

DKLs23
Threshold signature scheme