> For the complete documentation index, see [llms.txt](https://green-energy-network.gitbook.io/gen-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://green-energy-network.gitbook.io/gen-docs/tech-architecture/overview.md).

# Overview

The Green Energy Network (GEN) is built upon a **five-layer technical architecture** that integrates real-world data from green energy infrastructure into a secure and intelligent digital ecosystem. This framework ensures **traceability, compliance, automation, and impact-driven insights** for all stakeholders—enterprises, investors, and regulators.

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

{% stepper %}
{% step %}

## Energy Generation & Consumption Layer

**Purpose**: The foundation of the system, where energy data is generated through physical assets such as solar farms, EV charging stations, and energy-efficient facilities.

* Captures core metrics: energy generation (kWh), energy usage, voltage, current, environmental factors.
* Devices include: solar inverters, smart meters, EV charging units, and building management sensors.
* Supports physical linkage to tokenized real-world assets (RWA).

{% endstep %}

{% step %}

## IoT Monitoring & Edge Layer

**Purpose**: Provides **real-time connectivity** and ensures the data integrity from edge devices before transmission into the analytics and blockchain layers.

* IoT gateways relay data securely and reliably.
* Edge computing enables initial validation, data formatting, and latency reduction.
* Secure device authentication ensures traceability and tamper prevention.

{% endstep %}

{% step %}

## Blockchain Layer

**Purpose**: Serves as the **decentralized trust layer** for compliance, transparency, asset tokenization, and reward distribution.

* **Asset-specific smart contracts** store tariff configurations, verified energy outputs, and yield calculation logic.
* **Treasury contract** manages investor wallet mapping and reward distribution in stablecoins, while linking to fiat-based trust settlements.
* **Merkle root anchoring** and **IPFS hashes** are used for verifiable off-chain data.
* Stores only essential, low-frequency data:
  * Hourly/periodic energy output per asset
  * Yield distribution logs
  * Asset identity and tariff mapping
  * Carbon credit issuance and burn records

{% endstep %}

{% step %}

## AI-Enabled Analytics Layer

**Purpose**: Delivers **intelligence, optimization, and ESG insights** through large-scale data processing and modeling.

* Analyzes raw, high-frequency time-series data (e.g., every minute/second).
* Provides:
  * Energy performance forecasting
  * Predictive maintenance
  * ESG scoring and benchmarking
  * Carbon footprint tracking
  * Compliance report generation
* Data is stored and processed **off-chain** for scalability and speed.
* Results are visualized through dashboards and licensed via the platform.

{% endstep %}

{% step %}

### Application & Interface Layer

**Purpose**: Facilitates **user interaction**, ESG alignment, and access to investment and management tools.

* Investor dashboards: real-time yield updates, carbon offset records
* Enterprise portals: energy optimization controls, reporting center
* Regulator access: compliance audit tools
* Enables actions such as token purchases, credit trading, and proposal submissions for governance ($GEN)
  {% endstep %}
  {% endstepper %}

## On-Chain vs Off-Chain Data Categorization

| Category                          | Stored On-Chain (Blockchain Layer）                                                                                                                         | Stored Off-Chain (Analytics Layer)                                                                                                                                     |
| --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Energy snapshot (hourly/periodic) | <img src="https://img.icons8.com/?size=100&#x26;id=63312&#x26;format=png&#x26;color=000000" alt="" data-size="line"> Yes – For traceability & yield proof  | <img src="https://img.icons8.com/?size=100&#x26;id=63312&#x26;format=png&#x26;color=000000" alt="" data-size="line"> Also used for forecasting                         |
| Raw IoT data (per second)         | <img src="https://img.icons8.com/?size=100&#x26;id=63688&#x26;format=png&#x26;color=000000" alt="" data-size="line"> No                                    | <img src="https://img.icons8.com/?size=100&#x26;id=63312&#x26;format=png&#x26;color=000000" alt="" data-size="line"> Yes – For optimization, anomaly detection         |
| Tariff rate per asset             | <img src="https://img.icons8.com/?size=100&#x26;id=63312&#x26;format=png&#x26;color=000000" alt="" data-size="line"> Yes –  Per asset smart contract       | <img src="https://img.icons8.com/?size=100&#x26;id=63688&#x26;format=png&#x26;color=000000" alt="" data-size="line"> Not needed off-chain                              |
| Yield distribution record         | <img src="https://img.icons8.com/?size=100&#x26;id=63312&#x26;format=png&#x26;color=000000" alt="" data-size="line"> Yes –  With stablecoin logic          | <img src="https://img.icons8.com/?size=100&#x26;id=63312&#x26;format=png&#x26;color=000000" alt="" data-size="line"> For audit and investor dashboard                  |
| ESG score & benchmarks            | <img src="https://img.icons8.com/?size=100&#x26;id=63688&#x26;format=png&#x26;color=000000" alt="" data-size="line"> Not needed on-chain                   | <img src="https://img.icons8.com/?size=100&#x26;id=63312&#x26;format=png&#x26;color=000000" alt="" data-size="line"> Calculated and licensed to stakeholders dashboard |
| RECs / Carbon Credit logs         | <img src="https://img.icons8.com/?size=100&#x26;id=63312&#x26;format=png&#x26;color=000000" alt="" data-size="line"> Yes – Issuance, trading, burn records | <img src="https://img.icons8.com/?size=100&#x26;id=63312&#x26;format=png&#x26;color=000000" alt="" data-size="line"> For reporting & certificate generation            |
| Audit trail & reports             | <img src="https://img.icons8.com/?size=100&#x26;id=63688&#x26;format=png&#x26;color=000000" alt="" data-size="line"> No                                    | <img src="https://img.icons8.com/?size=100&#x26;id=63312&#x26;format=png&#x26;color=000000" alt="" data-size="line"> Stored in IPFS, CID logged on-chain               |

## Summary

GEN’s modular, 5-layer architecture balances on-chain trust and off-chain intelligence, enabling:

* Real-time monitoring and traceability
* Secure and scalable yield management
* ESG-driven insights and regulatory readiness
* Interoperable integration with stablecoins and fiat settlement systems

This architecture makes GEN the backbone of the next generation of **green digital infrastructure**.


---

# 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://green-energy-network.gitbook.io/gen-docs/tech-architecture/overview.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.