Skip to main content

Wallets

Essential insights for CKB dApp developers, covering JoyID integration, wallet choices, address specifics, and CKB transfer guidelines

Integrate Wallet (JoyID)

For developers looking to integrate wallets into their dApps, we currently recommend using JoyID, the most popular wallet in our ecosystem. JoyID offers a seamless experience for users, enabling secure and efficient interactions with your dApp.

For a comprehensive guide on integrating JoyID, please visit JoyID-Connect. Stay tuned for future integration guides for additional wallets as our ecosystem continues to grow.

CKB Wallet Options

Crypto wallets store private keys to access cryptos. They come in two types: hot wallets (online) and cold wallets (offline). Hot wallets, such as web-based, desktop, and mobile wallets, offer convenience but pose higher risk. Cold wallets, including paper and hardware wallets, provide enhanced security by keeping keys offline.

When it comes to storing and securing CKB assets, users have various options, including hot and cold wallets. While storing assets on exchanges is common, additional security can be achieved with dedicated wallets.

These wallets listed below offer custody and security services tailored to CKB. For more information, refer to the respective guides for each wallet.


CKB Address

Nervos CKB follows Bitcoin's bech32m address format (BIP-350) for address generation. It features a new full address format like this: ckb1qzda0cr08m85hc8jlnfp3zer7xulejywt49kt2rr0vthywaa50xwsqdnnw7qkdnnclfkg59uzn8umtfd2kwxceqxwquc4.

The previous short address format is now deprecated, for example: ckb1qyq5lv479ewscx3ms620sv34pgeuz6zagaaqklhtgg.

Tools for address generation and transformation include:

For detailed specifications, refer to RFC0021: CKB Address Format.

Requirements for CKB Transfers

To initiate a transfer, you need at least one Cell. Each Cell comprises the essential data fields: capacitylockargs, and hash_type, with storage sizes as follows:

  • capacity: 8 bytes
  • lock: 32 bytes
  • args: 20 bytes
  • hash_type: 1 byte

Thus, a single Cell requires at least 61 bytes of storage, equivalent to 61 CKBytes (CKB). Allocating 62 CKB is recommended to cover additional fees.