> 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/metachain/metaanthill.md).

# MetaAnthill

MetaAnthill technology has been developed for the hybrid mining system in MetaChain to synchronize at high speed and use the resources of the platform-independent hardware most efficiently.

Inspired by nature, MetaAnthill literally means ‘anthill’. The working method of ants – who can instinctively recognize the most advanced and optimal scenarios – has been adopted in terms of workforce allocation and efficiency, and the structure of the anthill has been internalized in terms of the created work path. MetaAnthill is a software library written in Java. It acts as a platform-independent integrated accelerator and a smart processing router.

MetaAnthill scans the device at the hardware level and acts according to the configuration and available resources of the hardware. It also creates the path structure of the network for the synchronization between nodes.

![](https://docs.metatime.com/whitepaper/~gitbook/image?url=https%3A%2F%2F989455816-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FAIzmobbGXH6E0WrRNrgp%252Fuploads%252FWyTTVjB1g6m1tdrVYvW4%252Fmetaanthill.png%3Falt%3Dmedia%26token%3D86b11c30-00c6-48d5-ba42-457f96c71b36\&width=768\&dpr=3\&quality=100\&sign=99fc678673e43a7b8618d10b02594eaa\&sv=3)

MetaAnthill allows the blockchain network to be more scalable. It minimizes confirmation times of transactions and instantly meets millions of transactions on MetaChain. It provides pre-verification and confirmation of the transactions because of seamless inter-node synchronization.

![](https://docs.metatime.com/whitepaper/~gitbook/image?url=https%3A%2F%2F989455816-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FAIzmobbGXH6E0WrRNrgp%252Fuploads%252FMCMcAnbUVnsoPu0Hi04M%252Fmetaanthill2.png%3Falt%3Dmedia%26token%3D23f6345c-e819-47a7-a27d-aa63cbc2ab5c\&width=768\&dpr=3\&quality=100\&sign=b07f428c8da16d89c532ba39d1d09a59\&sv=3)

![](https://docs.metatime.com/whitepaper/~gitbook/image?url=https%3A%2F%2F989455816-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FAIzmobbGXH6E0WrRNrgp%252Fuploads%252FWdMMJAC999zfq2TvE6BT%252Fmetaanthill3.png%3Falt%3Dmedia%26token%3Dfbc24fa5-bb43-41df-98aa-b37cd41c5a11\&width=768\&dpr=3\&quality=100\&sign=1db698f6b1bab7f511646d6b40bfaaad\&sv=3)

MetaAnthill also performs different tasks depending on the role and node type of the miners that make up the system.

**MetaMiner** monitors the entire network traffic and routes the traffic according to the incoming transactions.

**MacroMiner** ensures that the hardware required for MetaChain is analyzed, the necessary software installations are completed and the most up-to-date software is used.

**MicroMiner** monitors node density and ping time, and provides communication and fast synchronization, and integration of all transactions into the blockchain network in the shortest way.

![](https://docs.metatime.com/whitepaper/~gitbook/image?url=https%3A%2F%2F989455816-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FAIzmobbGXH6E0WrRNrgp%252Fuploads%252FzrUGVmYgRHKlWaHVd0oQ%252Fmetaanthill4.png%3Falt%3Dmedia%26token%3D98785549-2580-4b23-9a63-0b75e4d25df5\&width=768\&dpr=3\&quality=100\&sign=021e9f68edee600aa2e5fb826b068ebd\&sv=3)

**MetaAnthill** divides incoming queries to the blockchain into transactions and more.

To ensure the verification and confirmation of hundreds of thousands of transactions in the same second, all incoming transactions are pre-verified by MetaAnthill. These are then sent to MetaMiner, MacroMiner, and MicroMiners – that are part of the hybrid mining system –, for block generation by using smart load optimization. Verified transactions, if confirmed, are processed into blocks, shared with the entire network, and synchronized by Meta and Macro nodes.

Incoming Smart Contracts, on the other hand, are transmitted directly to TxPool, without any waiting process, they take their place in the generated block and are synchronized.

![](https://docs.metatime.com/whitepaper/~gitbook/image?url=https%3A%2F%2F989455816-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FAIzmobbGXH6E0WrRNrgp%252Fuploads%252FMg1g858DaJejqd7wnqcY%252Fdipnot.png%3Falt%3Dmedia%26token%3D17ebe656-6885-4b97-a74f-d79a5ec9f3f8\&width=768\&dpr=3\&quality=100\&sign=aa4de4fe235f4038de396689fd2abc1b\&sv=3)


---

# 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/metachain/metaanthill.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.
