RIGO Core
1. State Machine
Architecture
Account
The account is responsible for asset ledger and balance management, asset transfer, validation, inquiry, reward payment, etc. Nonces are used to ensure the
correct order of transactions and prevent double spending, and block producers (proposer addresses) are paid fees as rewards.
Staking / Reward
Responsible for managing staking, delegatee and rewards. It consists, among others, of transaction verification, reward payment, staking, delegating and
withdrawal, and establishes a block reward system.
Staking and delegation have a minimum amount limit according to amountPerPower, which is defined in the governance rules. Minimum quantity units are explained
in the reward rules below.
Power is calculated in proportion to the amount staked and delegated, and this proportional value is governed by the governance rules. The power value is
calculated for each amountPerPower value unit defined in the governance rules, and the rewards are calculated based on the value defined in rewardPerPower.
Staking and delegated withdrawal can be canceled one-to-one with the executed transaction, and withdrawal transactions require the hash value of the staking
and delegated transactions. Based on the hash value, the quantity is converted into usable coins.
In order to execute the conversion to usable coins, a return grace policy is applied based on the lazyRewardBlocks defined in the governance rules. This is for the
stability of the RIGO network.
Governance / Voting
The governance rules of RIGO consist of maxValidatorCnt, amountPerPower, rewardPerPower, lazyRewardBlocks, lazyApplyingBlocks, minTrxFee,
minVotingPeriodBlocks, and maxVotingPeriodBlocks.
The rules are set initially and can be changed through proposals and voting.
In the proposal transaction, the voting start block height and block period should be set accurately, with the voting block period required to be set to a value
between minVotingPeriodBlocks and maxVotingPeriodBlocks.
The voting transaction includes the hash value and the choice value of the proposal transaction, and if a proposal is approved by a two-thirds majority, the proposal
is accepted and becomes effective at a set time.
Once voting has concluded, the application time is determined according to the value set in lazyApplyingBlocks.
Transaction Processing
The RIGO blockchain supports parallel processing, reducing response time and increasing overall transaction throughput (TPS).
2. Consensus Engine
Architecture
Consensus Algorithm
RIGO is based on the Tendermint consensus algorithm. This consensus algorithm combines the Practical Byzantine Fault Tolerance (PBFT) algorithm with the
Delegated Proof of Stake (DPoS) concept to enable block chain construction, with the main goal of achieving consensus while limiting the influence of malicious
validators such as Byzantine failure.
Proposal Phase: The leader proposes a new block. This proposal will be broadcast to other validators.
Prevote Phase: Each validator casts a pre-vote, choosing to accept or reject the proposal.
Precommit Phase: Validators verify the pre-voting results of other validators, and if there is a sufficient number of agreements, they confirm and precommit the pre-
voting results.
Commit Phase: Once the precommit is complete, the validators commit the block formally. At this stage, the block is guaranteed not to change.
P2P (Peer-to-Peer)
The RIGO network uses a P2P network model to interconnect validators and propagate blockchain data. This achieves distribution and decentralization, allowing validators to communicate and share data independently.
RPC (Remote Procedure Call)
In RIGO, validators can use RPCs to send messages to different nodes in the network, execute procedures on those nodes, and receive results in return. With RPCs,
validators can perform tasks such as block proposal, voting, and consensus-related message transmission. RPCs enable smooth interaction between validators in the
network as well as internal communication of the engine.
RIGO Bridge
1. Overview
RIGO Bridge is a system for exchanging assets issued via public and private blockchains, which supports safe and reliable asset exchange through multi-sig
transaction agreements.
RPC(Remote Procedure Call)
RIGO Bridge safely exchanges assets by the lock-and-mint and unlock-and-burn methods. When the validators verify the lock and burn results from the "from
Chain" and reach an agreement, the asset is exchanged through a mint or unlock process in another "to Chain". The entire asset exchange process is recorded,
making it transparent and reliable.
2. Architecture
RIGO Bridge consists of the Validator Group and the RIGO Bridge Chain. Each validator verifies the asset from the "from Chain" and safely transfers the asset to the
"to Chain“, requiring the consensus of multiple validators. If verification fails, no assets will be exchanged.
RIGO Scan
1. Overview
RIGO Scan is a RIGO Blockchain explorer that provides transaction, address and block information of the RIGO network, as well as validator and proposal information.
This allows users to check the network status in real time, verify the details and validity of transactions, and inquire about validators and governance rules.
BYFFIN DApp 
1. Overview
BYFFIN Wallet is a mobile application that interacts with the RIGO Blockchain network, providing secure and convenient RIGO wallet management. Users can create
wallets, manage assets, perform staking and delegation functions to check returns, and delegate their assets to validators.