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. Interoperability
  • 2. Compliance
  • 3. Self-custody
  1. Core Components
  2. Settlement Engine

Accounts

PreviousPath FinderNextRecommendation Engine

Last updated 1 month ago

Accounts on dBOOK are designed for interoperability, compliance and self-custody. They are mapped to the End User address.

1. Interoperability

Any EOA (Externally owned account) or a smart contract on any chain can own and control accounts on the dBOOK ledger. dBOOK supports multiple signature and address derivation schemes including:

  • ECDSA: Secp256k1 & Secp256r1

  • EDDSA and Schnorr: Ed25519

2. Compliance

Accounts can define on-chain policies for increased asset control or to be compliant with regulations.

Currently dBOOK has three main policies

  1. Reject Credit - Unlike traditional blockchains where anyone can send funds to your wallet, on dBOOK you can enable reject credits, which allows one to reject incoming transactions.

  2. Approval Authority - Accounts can assign other accounts with the power to approve/reject incoming and outgoing transactions.

  3. Whitelists - Accounts can configure a whitelist of permissible senders and permissible assets to streamline screening.

3. Self-custody

Building on TradFi’s “execute-then-settle” model, dBOOK introduces self-custodial transaction types -

  • Promise - Conditional transactions that ensure assets remain in accounts until fulfilment of said conditions. These could be issued by accounts to or to other accounts. Promises power a wide variety of use-cases from self-custodial trading on an exchange to cross-chain trading.

  • Settle - Issued by counterparty fulfilling the promise.

Operators