D
D
DAS Documents
Search…
english
Introduction
FAQ
Glossary
Register DAS
Pricing
Open Registration Rules
Charsets
Reserved DAS List
Contribute to DAS
Contribute to DAS
Promoters
Channel
Registrar
Keeper
Developers
Wallet Integration
Build applications on DAS
Records namespace
We are hiring
Position List
Chief Evangelist
Frontend Engineer
Backend Engineer - Golang
Smart Contract Engineer - Rust
Others
Why assets on CKB can be managed by BTC address?
Github
Website
Powered By GitBook
Introduction
DAS to the crypto world is what Phone/Email to the Internet.
DAS is a blockchain-based, open source, cross-chain decentralized account system that provides a globally unique naming system with a .bit suffix that can be used for cryptocurrency transfers, domain name resolution, authentication, and other scenarios.
DAS is the first decentralized account system with broad compatibility, allowing users to register and manage the DAS accounts using any public chain address or even email.
The core elements of a DAS account are: the owner/manager, and the parsed record (i.e. the data it is associated with). Unlike ENS, the owner/manager of DAS can be any public chain private key or even email; unlike DNS, DAS supports any type of parsed record.
The structure of a DAS account is as follows.
​
​
DAS is a decentralized application running on Nervos CKB. DAS accounts and related parsed records are stored on the permissionless blockchain. Nervos CKB is a PoW public chain with a highly open architecture using the UTXO model.
DAS have five main components:
  1. 1.
    Core Protocol
    This refers to a series of Lock Scripts and Type Scripts deployed on the Nervos CKB, which define the DAS accounts and related operational standards for DAS accounts, and are concrete implementations of the DAS core protocols.
  2. 2.
    Keeper
    Keeper is a set of off-chain programs that can be run by anyone without permission, and is responsible for triggering a series of transactions that conform to the core protocol. Running a Keeper earns DAS system rewards.
  3. 3.
    Resolution Service
    It resolves the global state of DAS based on the transactions on Nervos CKB and provides account resolution service in the form of an interface to the public.
  4. 4.
    Client SDK
    Includes SDKs in various languages to simplify the integration of mobile wallets, web wallets, server wallets and other DAS-related applications.
  5. 5.
    Dapp UI
    Users ultimately use the various features of DAS through a variety of application interfaces. These applications can be used directly in the browser or can be integrated into popular wallet software.
The source code for all the components above can be found on our Github repository. Also, developers can implement their own Keeper, Resolution Service, Client SDK, Dapp UI based on Core Protocol.
Next
FAQ
Last modified 7mo ago
Copy link