# System Architecture

The DeCharge system is a vertically integrated, modular infrastructure stack that bridges physical EV charging hardware with intelligent software coordination and a real-world reward system. Its architecture is designed for scale, adaptability, and trust, enabling thousands of independent deployments to operate as a single, cohesive energy network.

Rather than layering DeCharge on top of legacy infrastructure, the system has been built from the ground up with decentralization, interoperability, and telemetry as core design principles.

## **Architectural Layers Overview**

The DeCharge architecture spans five functional layers:

<table><thead><tr><th width="173.79998779296875">Layer</th><th>Description</th></tr></thead><tbody><tr><td>Hardware Layer</td><td>Physical chargers: Mini (3.3 kW), Beast (7.4 kW), Titan Mini (30 kW DC), Titan (60 kW DC)</td></tr><tr><td>Firmware Layer</td><td>Embedded control software, OTA-enabled, local diagnostics</td></tr><tr><td>Network Layer</td><td>Messaging via OCPP over Wi-Fi/4G/LAN</td></tr><tr><td>Coordination Layer</td><td>Performance tracking, reward engine, CMS integrations</td></tr><tr><td>Application Layer</td><td>Host dashboards, telemetry portals, installer panels</td></tr></tbody></table>

These layers operate independently but interconnect via secure telemetry protocols to ensure transparent operation and coordinated behavior across the global network.

### **1. Hardware Layer**

This includes the modular DeCharge chargers themselves, each of which serves as a standalone energy node capable of being monitored, controlled, and rewarded based on real-world usage.

* Chargers are pre-certified for country-specific compliance.
* Designed for low-cost, plug-and-play deployment.
* Modular design for upgradability and repair.
* Built-in security features to prevent tampering and unauthorized use.

### **2. Firmware Layer**

Each device runs embedded software that enables:

* Secure metering and session logging.
* Over-the-air (OTA) software upgrades.
* Real-time self-diagnostics and error reporting.
* Dynamic load control (in upcoming releases).

Firmware ensures uniform behavior across chargers, even as hardware generations evolve or network conditions vary.

### **3. Network Layer**

DeCharge chargers communicate with the backend using the OCPP (Open Charge Point Protocol), specifically designed for communication between EV Charging Stations.

Supported internet interfaces:

* Wi-Fi (secured with WPA2 or higher)
* 4G & 5G SIM cards (non-M2M only)
* LAN with surge protection (for Titans and enterprise hubs)

Data transmitted includes:

* Energy dispensed per session
* Uptime & connectivity reports
* Fault or error events
* GPS & deployment metadata

To ensure resilience, all devices buffer data locally and auto-resend if temporarily offline.

### **4. Coordination Layer**

At the core of DeCharge’s intelligence is its coordination backend. This is where:

* Devices are onboarded and mapped to hosts/investors.
* Telemetry is validated and stored in real-time.
* Reward points are calculated per 60-hour epoch.
* Inactive or misbehaving chargers are flagged or penalized.
* Deployment heatmaps and performance dashboards are generated.

This layer integrates directly with the web application, installer portals, and DeCharge’s reward distribution logic. It ensures that all device activity is linked to a verified participant and scored fairly based on usage.

### **5. Application Layer**

The user-facing layer is where participants interact with the DeCharge ecosystem:

<table><thead><tr><th width="169.79998779296875">Tool</th><th>Purpose</th></tr></thead><tbody><tr><td>Host App</td><td>View sessions, earnings, uptime, and device health + Guided setup, diagnostics, and verification workflows</td></tr><tr><td>Ops Panel</td><td>For DeCharge’s internal support and deployment teams</td></tr><tr><td>User App</td><td>Location-based search and usage interface for the users to initiate and pay for the charging sessions</td></tr></tbody></table>

These applications are web-based and mobile-responsive, accessible via any modern browser.

<div data-full-width="true" data-with-frame="true"><figure><img src="/files/jih9Ird51YSTUQzwSNpo" alt=""><figcaption><p>Flow of Data and Control</p></figcaption></figure></div>

This seamless end-to-end flow ensures real-time accountability, transparency, and trust in how rewards are issued and devices are monitored.

**DePINFi as the capital layer:** DePINFi Pools form the financial coordination layer of the DeCharge architecture. They connect global capital to verified deployments by pooling stablecoins into on-chain deployment clusters and turning chargers into yield-bearing, programmable assets.

Visit [DePIN-Fi Pools](/depin-fi-pools/depin-fi-pools-tokenized-energy-infrastructure.md) for more info.

## **Key Design Principles**

1. **Device-Agnostic Scaling**\
   All chargers speak a common telemetry schema, ensuring that older and newer models can coexist and be rewarded equally.
2. **Network Redundancy**\
   Each charger operates independently, so the failure of one device doesn’t affect others. This allows organic growth without single points of failure.
3. **No Reliance on External Gateways**\
   Devices connect directly to the backend, no need for separate hubs or concentrators.
4. **Interoperability**\
   Designed with full OCPP compatibility across all charger models to enable seamless API integrations and interoperability with third-party systems and networks.

## **Integration Pathways**

Future integrations are planned for:

* Energy storage systems
* Smart load balancing with grid signals
* Solar input and battery pairing (solar retrofit program)
* Shared protocols with other DePIN systems (e.g., DePHY, Geodnet)

## **Summary**

The DeCharge system architecture is built for resilience, flexibility, and precision. Every layer is designed to ensure:

* Real-world performance metrics are tracked securely.
* Rewards are earned fairly and transparently.
* Devices remain upgradable and modular.
* The network grows organically while staying coordinated.

This foundation enables DeCharge to serve not just today’s EV drivers but the entire spectrum of decentralized energy consumers of the future.


---

# 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://docs.decharge.network/network-and-technology/system-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.