ReapChain Official
Published in

ReapChain Official

[Tech]ReapChain Consensus Process and Block Generation

ReapChain has a basic block generation cycle of 2 seconds. But in the Reap Middle Chain, that corresponds to the temporary ledger; approvals are notified in less than 1 second to create the same effect as if consumers are receiving credit card payment through authorized notifications. In reality, block generates within 2 seconds in ReapChain, so the consumers rarely notice any payment approval delays, and It thus makes the ReapChain suitable for commercial transaction deployment. The ReapChain can quickly reach a consensus within 2 seconds by selecting a coordinator from a standing committee that operates at all times. It is possible because it reaches the consensus with the minimum amount of network traffic under direct communication among 28 nodes surrounding the selected coordinator during the process. Mainly, time delays for a while and inevitably network loads occur in collecting validation messages that broadcasts in P2P networks; A coordinator exchanges message only once in the internal network organization. Such a coordinator ultimately becomes a single block producer to generate a block. If a block does not generate within 2 seconds, the block generation of the corresponding cycle skips.

In the ReapChain, It may require more time to reach the finality of every block, even though the block generates within brief seconds. Therefore, considerations can make to finalize the transactions after accumulating a certain number of blocks by installing checkpoints at every 20 blocks like in Ethereum Casper protocol.

ReapChain creates one round of tables for block generation. In one round, 15 steering committee nodes have selected among the general nodes through security enhanced random selection mechanism, and 14 standing committee nodes participated together in the validation process. The reliability of the consensus that is achieved within the ReapChain’s QSN (Quantum Safety Net) have insured here.

In the ReapChain, the Consensus process of generating blocks always establishes in-network, even if fewer nodes are participating due to some failure process. In particular, the reliable standing committee nodes that are constantly operated by the governance continuously perform a health check, and the coordinator selected from the standing committee nodes leads the consensus process. Considerations have made for a mechanism in which 2f+1 coordinators are selected just in case that there can be a chance of momentary failure even after the coordinator is selected.

★ ReapChain Official Community

Follow the ReapChain official community and have more news!

Telegram (ENG):
Telegram (KR):

Partnership and Affiliation Inquiries:
Investment and Sale Inquiries:
Project Inquiries:



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store