Note

It’s highly recommended to use the CCC SDK as your primary development tool within the CKB ecosystem. CCC is the latest and most robust JavaScript SDK designed to streamline and enhance your development process. By choosing CCC, you'll be leveraging the best practices and most up-to-date features available for CKB development. To get started with CCC, follow the installation guide and explore the documentation to integrate it seamlessly into your projects.

lumos

As of now, lumos contains the following components:

• ckb-indexer: a cell/tx indexer base on ckb-indexer.
• BI: a big number library for lumos.
• toolkit: JavaScript toolkit for Nervos CKB. It contains a series of independent tools that can aid development of CKB dapps. This is different from a normal CKB SDK, since it tries to minimize the work done in an SDK, while providing more utilities that could be handy.
• lumos: A root package to integrate of common functions from the Lumos sub-package.
• base: a base package containing common types and utilities that are used by most packages. If there is a CKB specific task you need to perform, you might want to look here first. Chances are they are already provided.
• helpers: a helper package containing more utilities. The difference between helpers and base, is that base contains pure stateless functions, while helpers works in a more intrinsic way: it requires config-manager mentioned below to be setup.
• common-scripts: integrations for known scripts on CKB. While we try our best to provide integrations for popular CKB scripts, people might be working on innovations every day. As a result, we are also designing a set of APIs, so developers can freely integrate their own scripts into lumos for everyone to use. One integrated, common-scripts should be able to leverage those new scripts as well.
• config-manager: a manager for dealing with differences between different chains, such as mainnet, testnet, or numerous dev chains. We abstract each chain into individual config file. Once loaded, config manager will be able to handle the chain specific logic, so you don't have to deal with this in your own code.
• transaction-manager: a transaction manager for CKB. One problem with UTXO based blockchains, is that a certain amount of gap period exists between a transaction is accepted by a blockchain, and when it is actually committed on chain. During this gap, new cells created by the pending transaction will not be available. Transaction manager package takes care of this. It wraps an indexer instance, and makes sure cells created in pending transactions, are also exposed and available for assembling new transactions. This means you are no longer bounded to one transaction at a time, you can freely send series of transactions as you wish.
• hd: an HD wallet manager for CKB. It supports mnemonic and keystore, compatible with Neuron and ckb-cli, you can load keystore from Neuron or ckb-cli directly and import mnemonic generated by Neuron.
• hd-cache: an HD cache manager for CKB. It build a memory cache for derived addresses and live cells of these addresses.
• rpc: RPC module for CKB RPC. Provide type definitions for CKB RPC interface.
• experiment-tx-assembler: here are some experimental features for simplifying the transaction assembling process.

Examples

we have provided some use cases for Lumos, such as interactions with MetaMask, transfers CKB, address conversions, etc. which you can find in examples

Building

Requirements

• Node.js
• pnpm

sudo apt-get update
sudo apt install nodejs
npm install -g pnpm

Build

pnpm run build

Test (ava)

pnpm run test

Test Coverage (c8)

pnpm run test-coverage

Format & Lint

pnpm run lint

Clean

pnpm run clean