# Technical Architecture

Green Meta is developed based on the Pantanal public chain architecture, effectively addressing the increasingly complex demands and enabling rapid iteration of specified functionalities without impacting other module functions. It is a comprehensive technological revolution that combines six key technological pillars: blockchain, interactivity, game engine and twin engine technology, artificial intelligence, comprehensive intelligent network technology, and Internet of Things. These six technologies are creatively combined and abbreviated as BIGANT, also known as the "Great Ant."&#x20;

At the application layer, Green Meta adopts a top-down design approach. Firstly, it focuses on designing the blockchain protocol to address data standardization and interoperability across multiple chains. Secondly, it defines a component model for general interactivity, game engine, and twin engine technology, achieving loose coupling and plug-and-play capabilities for specific functional components to meet the need for custom extensions in applications. Finally, based on standardized artificial intelligence, comprehensive intelligent network technology, Internet of Things, and component models, it builds carbon-neutral metaverse tools and development kits that meet specific application standards, providing tools for rapidly realizing commercial-grade metaverse applications.

<figure><img src="/files/HpLfVDq7hUO8MbA4YTtX" alt=""><figcaption></figcaption></figure>

**1. Blockchain Protocol**&#x20;

Green Meta relies on the Pantanal public chain to create a blockchain protocol as the top-level architectural design. The blockchain protocol defines the data format standards for blockchain, including ledger state, historical proof, ledger operation set, and contract instruction set.&#x20;

**2. Component Model**&#x20;

The "component model" is the framework model for the logical components of Green Meta, representing the implementation framework for underlying system protocols. It includes components such as network, ledger, persistence engine, and contract engine.&#x20;

**3. Service Model**&#x20;

The "service model" represents the specific implementation of the upper-level blockchain protocol and component model, consisting of gateways, services, node networks, SDKs, and a set of toolkits.&#x20;

These technological forces are the key drivers of productivity transformation, changes in production relations, societal and era changes, and iterative leaps in civilization. They are the most powerful tools for achieving carbon neutrality and the future of the human community. They empower Green Meta to realize DAO organizational autonomy, develop commercial ecosystems, govern the metaverse's new society, and construct a next-generation hybrid human society.&#x20;

Ants, though individually low in intelligence, form highly intelligent small societies when they come together. They can regulate temperature, construct complex ant nests, manage fungus farms, tend aphid farms, and form armies. The larger the population, the higher the collective intelligence. In the same way, as technology advances, the intelligence of the Green Meta metaverse increases, providing greater value in enabling carbon neutrality.

<figure><img src="/files/qXiS9J1rT22kkXy1QFuu" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://doc.greenmeta.biz/white-paper/green-meta-architecture-system/technical-architecture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
