> For the complete documentation index, see [llms.txt](https://docs.metaverse-ico.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.metaverse-ico.net/whitepaper/abstract.md).

# Abstract

The principles of data storage, processing, ownership, and transparency of blockchain technology have led developers to create decentralized applications at a growing rate day by day. Given the increasing demand for these developed applications and technology, existing solutions have faced **scalability, speed, and security** problems. Besides, the solutions have been given priority to narrow user groups familiar with technology instead of the wider audience. To enable the mass acceptance and widespread use of Web 3.0 era, blockchain infrastructures need to be scalable, cost-effective, reliable, and continuously improved structures similar to cloud solutions. In this way, the development of applications that are used by the wider audience can be advanced.

**MetaChain** is a blockchain network that is built on the EVM (Ethereum Virtual Machine) and it prioritizes scalability, speed, security, and decentralization to eliminate the aforementioned problems. The network allows large audiences to access blockchain technology with human-centered interaction surfaces.

**MetaChain** has been in development since 2019 by MetaChain. MetaAnthill Technology focuses on the "human" factor named after the organized working capacity of ants. It includes original and innovative solutions such as the Hybrid Mining system within the Proof of Meta concept. This combination of innovative technologies and models eliminates the fundamental problems that hinder the widespread adoption of Web 3.0.

**MetaChain** benefits from MetaAnthill technology to enable fast and secure transactions. MetaAnthill acts as a software library written in Java, a platform-independent integrated accelerator, and a smart processing router that works accordingly.

Proof of Meta hybrid consensus mechanism sends all transactions to MetaMiner, MacroMiner, and MicroMiners, which are part of the hybrid mining system. With the help of smart load optimization, hundreds of thousands of transactions can be audited and processed simultaneously. The verified transactions, if confirmed, are shared on the network by processing them into the blocks and synchronized by all nodes.

The unique hybrid mining system allows the human factor to directly contribute to and drive the ecosystem. In this context, 3 mining options are offered with different roles called MetaMiner, MacroMiner, and MicroMiner, and each of these options has decision-making mechanisms that contribute to the ecosystem.

MetaChain is the main component of the entire ecosystem in which basic applications work integrated and form the infrastructure of the ecosystem.

The main solutions developed by MetaChain will be a part of the ecosystem on the first day the blockchain network is launched and will have their own roles in MetaChain.


---

# 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.metaverse-ico.net/whitepaper/abstract.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.