> For the complete documentation index, see [llms.txt](https://docs.aeternity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aeternity.com/aeternity-developer-tools/protocol/core-protocol-components.md). # Core Protocol Components The æternity blockchain offers a robust suite of core components designed to power the next generation of decentralized applications. At the heart of the protocol lies the Next Generation Nakamoto [consensus ](/developer-documentation/protocol/consensus.md)mechanism, which achieves significantly higher throughput compared to traditional blockchains through its innovative use of key-blocks and micro-blocks. The ecosystem includes [Generalized Accounts](/developer-documentation/protocol/generalized_accounts.md) that provide flexible authentication options beyond standard signatures, Smart Contracts with [Sophia](/aeternity-developer-tools/markdown.md) - a functional programming language built for security, and State Channels for off-chain transaction processing. Additionally, æternity features built-in Oracles for bringing real-world data onto the blockchain, creating a comprehensive infrastructure that combines scalability, security, and developer-friendly tools in one cohesive platform.\ \ Each of these components is explored in detail in the following sections, providing comprehensive documentation for both developers and users to understand and leverage the full potential of the æternity blockchain. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.aeternity.com/aeternity-developer-tools/protocol/core-protocol-components.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.