> For the complete documentation index, see [llms.txt](https://hice-token.gitbook.io/hice-token-lab/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hice-token.gitbook.io/hice-token-lab/supporting-infrastructures/core-blockchain.md).

# Core Blockchain

Introduction

The Blockchain Trilemma is a well-studied problem by both academics and market participants. It states that all cryptocurrencies, including Bitcoin, Ethereum, etc. must make trade-offs between optimal security, scalability, and decentralization.

Our solution to the trilemma above is Satoshi Plus consensus, which operates at the core of the Core Network. Satoshi Plus consensus combines Proof of Work (PoW) and Delegated Proof of Stake (DPoS) to leverage the strengths of each while simultaneously ameliorating their respective shortcomings. Specifically, Bitcoin computing power guarantees decentralization, the DPoS and leadership election mechanisms ensure scalability, and the entire network holistically maintains its security. Core is the first chain to implement our new consensus mechanism. Although it will not be the last, we believe that with the strength of our community, CORE will achieve the necessary network effects required to create a successful currency and serve as the much needed springboard for broader Web 3 adoption.

| Transactions | Addresses | Community |
| :----------: | :-------: | :-------: |
|     154M+    |    10M+   |    2M+    |

Learn more about Core [HERE](https://coredao.org/)!


---

# 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://hice-token.gitbook.io/hice-token-lab/supporting-infrastructures/core-blockchain.md?ask=<question>&goal=<user_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.