Laikelib – An entirely self-researched and developed public blockchain based on blockchain 3.0

Laikelib is an underlying architecture easy to use and access for commercially used blockchain 3.0. Through Laikelib, developers can self-define sidechains, intelligent contracts, and cloud storage in the blockchain and make profits by building, releasing, and distributing applications.

As envisioned by the LaikeLib team, LaikeLib will build a more efficient, safer and scalable credit value ecosystem that combines the quintessence of existing underlying technologies of blockchain.

Technical Design of Laikelib

1. System Introduction

Laikelib team, by combining the underlying quintessences of existing high-quality blockchain technologies, has built a more efficient, safer, and scalable credit value chain and application ecosystem.

DApp comprises an intelligent contract and client code. Laikelib is committed to building decentralized application services that are diversified and adaptable to various industries and service scenarios.

With Laikelib, developers can quickly start blockchain application development and bring safe and convenient applications to users; everyone can quickly understand blockchain and feel free to use blockchain products.

2. Overall Structure of Laikelib

The bottom layer of Laikelib blockchain is independently researched and developed by the Laikelib team who sticks to the concept of “open, sharing, and joint innovation” which allows developers to quickly join in and grow. The bottom layer of Laikelib has realized modules such as account and permission management, smart contracts, consensus mechanism, operation monitoring and fault tolerance repair based on blockchain technology.

In terms of Laikelib business model development, after implementing the corresponding interface, developers can complete the model library encapsulation and easily access the application through an upper-layer API. They can also add fully implemented business model library into the Laikelib library and get awards after we review their library. We will also open more business models that’ll be discussed and improved with everyone. We will also invite all industries in based on diversified implementation of the business logic.

Developers can access our open model library and search a business model that matches their industry. They can follow the access mode that we describe and import the model, without the need to consider the complex construction of the bottom layer. To promote the implementation of blockchain applications in various industries, we will also open and add more business model libraries and discuss them with everyone.

3. Main Chain and Side Chain of Laikelib

Laikelib comprises the main chain and side chain.

In a common sense, main chain is the chain which records main business records and expansions. The main chain and the side chain are pegged in two ways, allowing credit data to be transferred from the main chain to the side chain.

The Laikelib side chain supports a relative feature business model and has a bookkeeping and consensus mechanism similar to that of the main chain. It has its own on-demand account books, consensus mechanism, script and contract support, business model with relative features, independent credit recording mechanism similar to that of the main chain, etc. Credit value conversions between side chain and main chain are also provided (Check out our documentation for details).

The side chain and main chain are pegged in two ways and interact with each other but the businesses on the side chain and main chain do not affect each other because the business and credit records are recorded using different protocols.


Scenario example:

One main chain derives multiple side chains. The main chain represents the credit value and the side chains record not only various business data but also credit records similar to those of the main chain. Laikelib provides a public API for two-way pegging of the main chain and side chain and for exchanging credit information between them. Credit records of side chain are recorded on the side chain but can be transferred to the main chain via the API.

Comparison between Laikelib main chain and side chain:

Description Item

Main chain

Side Chain

Block capacity and quantity


Not fixed, customizable



Not fixed, customizable

Consensus mechanism



Business expansion

Fixed businesses related to main chain

Diversified business scenarios supported

Network mode

Nodes are expandable based on the Hypercube system

Nodes are expandable based on the Hypercube system

Value tracing


No tracking

Comparison between main chain and side chain

4. Hypercube

Laikelib network is constructed based on the idea of Hypercube which truly achieves synchronization of distributed and decentralized block network nodes.

Hypercube network is ideal for Laikelib to achieve high availability, regular and wide distribution, and hashing of expansible network nodes. Traditional peer-to-peer connection technology only realizes peer-to-peer network communication. However, in high-speed network expansion and equalization, in order to achieve high-speed node communication and network security and smooth expansion, monitoring and introducing intelligent capacity expansion and node mediation mechanism are necessary in order to adjust and optimize connection between nodes.

The team has invested heavily in optimizing the Laikelive event monitoring scheduling engine for high speed node broadcasting, optimal connection algorithm, event dispatch communication and so on. The engine can monitor and properly coordinate the connection and communication mechanisms between nodes and ensure smooth and fast communication between nodes.

Scenario example: A node newly launched will be broadcast to every node. The current node, based on the information returned by the broadcast, computes the optimal node after coordination and precisely broadcasts the optimal node to the network. Once in a while, the current node will communicate with adjacent nodes to properly adjust and optimize the network connection.

5. POP (Proof of Power)

1. Introduction to Common Consensus

Consensus means an agreement that every node acknowledges when making a transaction. For example, a Bitcoin miner receives transactions from the Internet and packs it into a block. Then it calculates the Hash value of the block to make the block meet certain rules and then broadcast the block. Other nodes then receive the block, verify it and add it to the blockchain. Currently, famous consensus mechanisms on the market are PoW, PoS, and DPoS.

Proof of Work (PoW) guesses a numerical value (nonce) through calculation and enables the Hash value of the content added with the transaction data to meet the newly specified upper limit.

Proof of Stake (PoS) uses a deposit (either credit, fame, or other items with value) to make a legal block become a new block by competition. The profit is the interest and service fees charged on the pledged credit proof. The more deposits (such as credit records) are provided, the bigger probability of winning the right for bookkeeping will be. A legal bookkeeper can get this profit.

DPoS is a new algorithm proposed by bitshares that protects the security of cryptocurrency. It, while trying to solve the problems of traditional POW and PoS used by NXT, also offsets the negative impacts of centralization through implementing technological democracy.

2. Proof of Power

Proof of Power (PoP). By referring to the past records of rights got, the more the historical records are, the greater the rights to keep accounts will be.

In the past 1000 record blocks, the more credit records one keeps, the higher the probability of he/she obtaining the right to record the next piece of block information. In a certain period of time, whoever first calculates the Hash that meets the target value, he/she can get the right to keep accounts, and this will also affect the difficulty in obtaining the right to record the next block. In the future, if no next block is calculated, and now the node which has more rights calculates the block with the same height, then the block of that node is considered the longest chain. However, in this mechanism, it is not always the node with larger right to continue to obtain the recording right. If another node (with smaller right) wants to obtain the right to record data, it needs to improve its calculating power, and as the calculating power increases, the calculating speed increases, it will be less difficult to obtain the right to record the current block. A node with a larger right may not be able to obtain the record right before other nodes that have already increased their power.

6. Account and Verification Methods

The address of Laikelib’s each account in each chain is unique, and the ways each business chain obtains the address signatures are different.

Accounts are decrypted through strict cryptography, and determine ownership through signature verification. For different businesses, signatures and verification methods are different.

7. Concurrent Scheduling

With the continuous increase of users and service volume, the request instructions may reach the peak of the processing volume in a certain period of time, and the server may not be able to process them at the same time, thus congestion may occur. For example: at the same time, a large number of smart contract registration instructions are sent from the client over, and the server cannot handle all in a timely manner, resulting in too much accumulation of requests.

Due to the frequent occurrence of high concurrency services, Laikelib, based on a high-speed network node communication, uses an event monitoring module to determine whether the processing unit reaches the current processing bottleneck, so as to reasonably judge and relay processing instructions. If the bottleneck is not reached, the instruction is pushed into the transaction queue of the current service processing unit.

Processing scenario: A smart contract registration instruction is delivered. However, the peak value of the current node unit is 5000 times / min, the monitoring module finds that the unit reaches the bottleneck, so it properly collects the node throughput from the adjacent nodes and forwards the current service request to a processing node with relatively smaller number of requests.

8 Light Service Client and Public API

1. BaaS light service client

BaaS means blockchain as a service. It uses a unified API or SDK to access back-end services.

Laikelib will provide lightweight micro-service client (Linux platform) for easy access from developers. It supports HTTP protocol and TCP / IP protocol access; using BaaS service for access is smooth and simple.

Operating modes of traditional Internet blockchain application systems are mostly based on B / S or C / S architecture, but the blockchain data are hashed in the distributed storage service media, and the need to constantly synchronize the data on the chain is a trouble. Laikelib’s BaaS light client will change this. It can make blockchain system running on the Internet equivalent to running locally. Applications can access the local light service client to get data.

A user who accesses Laikelib using a light service client can connect to the full version of the server and then to the network (if the full server opens API access to the owner of the application, he can call the corresponding public API Service) to synchronize the complete blockchain from other full service nodes through the network link. Developers can publish and develop their own applications on our blockchain by simply referencing to the public APIs that we provide, packaging the data, and pushing it to the appropriate business interface.

2. Public API access

Laikelib provides public API for developers to access.

Laikelib’s public API design draws on and integrates prototypes of ODIN and Fabric application architectures. It combines the open data index design ideas to implement a diversified searching and locating engine based on “data index naming identifier” and “business index naming identifier”. The design idea of Superbook (Fabric) is implemented in accordance with the “use case driven” approach where all functions should have corresponding use case needs. Given its design ideas, Laikelib module allows of business models to achieve diversified business model accesses.

9. Laikelib system features

1. Decentralization

    Blockchain technology’s core design idea is decentralization.

Laikelib is committed to implementing and promoting decentralized applications technically.

2. Business model diversification, access simplification.

Laikelib extends business model libraries with other developers to accommodate diversified business scenarios and application accesses, simplify developer preparation and reduce difficulty of accessing the underlying blockchain. If developers want to participate in business model library development, they only need to achieve the corresponding interface that we provide and they can package a business model library. We also provide public model libraries that we will explore and develop with everyone, and integrate blockchain technology into more industries. Such as: decentralized smart retail system, decentralized personal credit collection & management system, decentralized data API service, and decentralized distributed cloud computing systems.

In terms of accessing Laikelib, you can use the public API or directly use our SDK for access, or use the light service client for access which is multi-language and easy to expand.

3. Efficient, fast, and smart.

Laikelib constructs the communication network based on Hypercube design ideas. The LaiKelive peer-to-peer network communication service can, according to the volume of concurrent traffic and the service bottleneck, appropriately switch or adjust the communication transmission channel to reduce channel congestion rate.

The event monitoring scheduling engine can, according to business throughput, determine whether to accept the current event processing request, if it does not receive, it will forward the request to the neighboring processing unit.

4. Data storage is safe, high quality and reliable.

    High-frequency exchange of information may contain some dirty data. Before the data is processed by the unit, the verification module verifies its identity, source, and the event monitoring scheduling engine distributes it to processing unit nodes through reasonable algorithm judgment and determination. Timely judgment and filtering of dirty data ensure data security, quality and reliability.

5. Good scalability.

(1) Adaptability to diversified and multi-industry services, and horizontal expansion.

(2) Easy management: when one of the chains needs to be upgraded, simply upgrade it and no need to upgrade the entire chain.

(3) Flexible use: users only need to synchronize the main service chain information; no need to synchronize all chain information.

(4) Easy maintenance: different business models adapt to different business scenarios with different amount of data. For different services, the data structure is different, the block output time and block size are different, and the billing is also different.

Laikelib Welcomes Your Participation

Laikelib will remain inclusive and welcomes all of you to participate in the endeavor to improve the blockchain ecosystem.

Relying on the technological advantages of blockchain, Laikelib makes data synchronization faster and saves a lot of time for users. Laikelib does not have to synchronize data of sidechains, thus saving a lot of capacity for users. Users only have to synchronize business data relating to them. Therefore, they can control all transaction data freely and create more social value.

Compared with transactions through a third party, transactions through Laikelib are more convenient, transparent and decentralized, therefore more trustworthy.

Media Contact
Company Name: Shanghai Heshu Software Co., Ltd
Contact Person: Mr. Wang
Country: China