> For the complete documentation index, see [llms.txt](https://docs.orbitchain.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.orbitchain.io/orbit-chain-network/orbit-chains-design-goal.md).

# 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.orbitchain.io/orbit-chain-network/orbit-chains-design-goal.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.