# Orbit Chain's Design Goal

**Decentralization:** Anybody can participate in the blockchain with O( c ) amount of resources, including but not limited to verification and sending. 

**Resilience:** The chain is to maintain connectivity even if majority of the nodes on the network becomes disconnected or offline. 

**Simplicity:** Complexity is lowered, even if it means less efficiency. 

**Longevity:** The chain is to be built with modular designs regarding functions as to maintain operation continuously despite security / governance flaws while they are being rectified. 

**Scalability:** Transactions and other functionalities are to be processed in a parallel way to increase scalability. 

**Connectivity:** The chain is to connect to different systems regardless of their format and design. 

**Block chain Security:**  Risk of 51% Attack

**Finality reversion:** Should a certain block A be finalized by a Validator, it must be prevented from being finalized again by another individual. 

**Invalid chain finalization: ‌**A validator cannot finalize an invalid block. 

**An invalid block must be rejected, following the laws regarding blocks and signature information.** 

**Liveness denial:** The chain is to continue functioning in the event that a small number of validators stop producing blocks

**Because Orbit Chain is based on PoS consensus algorithm, validators that do not validate are pushed out of validator group by penalization through the algorithm.** 

**Censorship: ‌**Validator must verify all transactions made on the blockchain fairly. 

Should the majority of validators choose to take advantage of their majority voting power, a small number of honest nodes may run the chain independently from the main chain through a soft fork process. In this case, the market is left to choose between the original chain, and the new chain.