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

Accounts

Last updated 6 months ago

dBOOK ensures that user onboarding process is streamlined. Users can use their existing accounts from Solana, Ethereum, Bitcoin, etc. to dBOOK or can use social logins to create fresh accounts.

This is made possible because dBOOK natively supports multiple signature and address derivation schemes including:

  • ECDSA: Secp256k1 & Secp256r1

  • EDDSA and Schnorr: Ed25519

  • Address encoding of major ecosystems such as Solana, EVM, Cosmos, BTC, etc.

An Account has 3 components:

1. Compliance Module

With the evolving regulatory landscape for digital assets, having an on-chain compliance module that evolves with these changes is crucial.

dBOOK accounts offer flexible compliance, so that anyone can configure compliance as per their requirements. As a result, developers who require compliance and do not require compliance have access to the same network.

Core features:

  • Whitelist Management: Control which addresses and tokens are accepted by the account

  • Add Delegators: Whitelist third-party addresses(eg. custodians) to act as realtime transaction screeners

2. User Assets

Asset information is stored directly in user accounts. These assets are identified by their chainID and source chain address.

dBOOK currently supports major fungible and non-fungible asset standards.

3. Actions Module

Actions module is a very lean set of self-custodial transactions built on top of financial primitives of credit and debit.

Types of transactions:

  • Direct transfers: Simple credit and debit between two accounts

  • Approve/Reject: Accept/Reject normal or delegated transactions

KYC Integration: Facilitates on-chain legal identity verification for users by integrating with services such as

: Issue conditional transactions (such as limit orders or RFQs) that lock assets in user's account until fulfilment

: Issued by counterparties specified in the Promises, fulfilling the transaction and performing the final settlement

zkMe
Promises
Settle