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

Endpoints

PreviousAsset AccountingNextThreshold Signatures

Last updated 2 months ago

Unlike Smart Contract wallets, dBOOK employs MPC (Multi-Party Computation) threshold wallets.

Threshold wallets
Smart Contract wallets

MPC support

Yes

No

Code Vulnerability

Low

High

Multi Chain Complexity

Low

High

Transaction cost

Low

High

Private key shares are distributed and rotated among active dBOOK guardians, ensuring that no single entity controls the entire key. These wallets function as standard wallets and support off-chain signing. All assets and information sent for deposit or execution on the dBOOK network are received by these endpoint wallets.

dBOOK Endpoints, built on Threshold Wallets, are deployed across all connected blockchains and serve as gateways to the network. These Endpoints manage both asset deposits and execution instructions. Assets are securely pooled within the Endpoints (governed by dBOOK Guardians), while all accounting is precisely maintained through the user’s dBOOK Account.