> For the complete documentation index, see [llms.txt](https://docs.u2u.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.u2u.xyz/introduction/litepaper/consensus.md). # Consensus **Introduction to Helios Consensus** The U2U Network is the next generation of blockchain build upon the DAG technology to address the limitations of traditional blockchain systems. It aims to offer efficient, secure, and scalable solutions for various use cases and industries. Helios Consensus mechanism lies on the heart of U2U Chains which play the crucial role in achieving consensus among network participants. Helios Consensus is a highly innovative and ground breaking mechanism that sets U2U Chain apart from other existing blockchain technologies. What makes this mechanism truly exceptional is its exclusive focus on Layer 0 (protocol layer), where efficiently addresses the need of enterprises and incorporates key ESG (Environmental, Social, and Governance) factors. By prioritizing these aspects, Helios Consensus ensures that U2U Chain not only offers cutting-edge technological solutions but also promotes scalability and protection to entities or businesses. This unique combination of advanced functionality and commitment to social and environment has set the significant successful of U2U Chain. **Helios Consensus security built at the core** Helios Consensus utilizes aBFT (Asynchronous Byzantine Fault Tolerance) and DPoS (Delegated Proof of Stake) mechanism to enhanced security, improve scalability and efficient validation. By doing away with the assumption that some messages will always get through, even if they are lost or delayed forever, aBFT offers robust security against malevolent or bad bad actors, even in the presence of malfunctioning nodes. It ensures that all participant nodes agree with timing and order of transaction in the network. The DPoS permits the election of a small group of reliable and trusted validators who will take part in the consensus process and validate transactions in addition to the security features of aBFT. Efficiency, scalability, and transaction processing speed will all increase with DPoS. --- # 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.u2u.xyz/introduction/litepaper/consensus.md?ask=&goal= ``` `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.