# Regen Ledger

The Regen Ledger forms the foundation of Regen Network’s technical architecture. It provides the verifiable on-chain state that underpins all ecological accounting, ensuring each project, credit, and claim can be independently validated through a transparent and immutable record. Rather than serving as a full data repository, it acts as a trust and provenance layer, recording canonical registry data and cryptographic commitments to off-chain content.

## **Architecture & Core Modules**

<figure><img src="/files/coATPD78N4zkdM34yOaA" alt=""><figcaption><p><em>Regen Ledger architecture showing Cosmos SDK core modules, Regen-developed extensions, and smart contracting layer.</em></p></figcaption></figure>

Built on the Cosmos SDK, Regen Ledger leverages its modular framework to implement custom logic for ecological crediting and data anchoring while maintaining compatibility with interchain standards. Regen Ledger extends the base SDK with custom modules for ecological crediting and metadata management, alongside standard Cosmos modules for core blockchain operations.&#x20;

The table below describes the most commonly used modules.

<table><thead><tr><th width="173.33331298828125">Module</th><th width="432.333251953125">Purpose</th><th>Developed By</th></tr></thead><tbody><tr><td><strong>Ecocredit</strong></td><td>Core registry logic for credit classes, projects, batches, issuance, retirements, and internal marketplace operations.</td><td>Regen Network</td></tr><tr><td><strong>Data</strong></td><td>Anchors external metadata and evidence using IRIs, enabling verifiable off-chain storage and retrieval.</td><td>Regen Network</td></tr><tr><td><strong>Feegrant</strong></td><td>Allows one account to pay transaction fees for another, supporting delegated operations and more accessible participation.</td><td>Cosmos SDK</td></tr><tr><td><strong>Authz</strong></td><td>Provides delegated authorization for users or agents to perform actions on behalf of another account.</td><td>Cosmos SDK</td></tr><tr><td><strong>Bank</strong></td><td>Handles token balances, transfers, and escrow for credit transactions.</td><td>Cosmos SDK</td></tr><tr><td><strong>Gov</strong></td><td>Manages on-chain proposals, parameter changes, and protocol-level voting.</td><td>Cosmos SDK</td></tr><tr><td><strong>Staking / Slashing / Distribution</strong></td><td>Core SDK modules ensuring validator security, consensus, and network reward distribution.</td><td>Cosmos SDK</td></tr></tbody></table>

{% hint style="info" %}
For a full list of modules and technical specifications, see the [Regen Ledger Docs](https://docs.regen.network/).
{% endhint %}

***

## **DAO and Governance Integration**&#x20;

Regen Ledger integrates with **DAODAO**, a **CosmWasm-based governance framework** that provides the tooling and functionality for groups and organizations to coordinate decision-making around credit classes, community funds, and project-level governance.

Through DAODAO, DAOs can:

* Create and manage multi-signature treasuries.
* Propose and vote on registry or funding actions.
* Execute smart contract–based decisions that interact directly with ledger state.

This integration extends Regen’s native governance capabilities, allowing decentralized participation in ecological asset management and network upgrades while maintaining transparent, verifiable decision trails.

***

### **Access and Queries**

These endpoints are the same surfaces used by Regen’s indexers and applications, such as the Regen App, to stay synchronized with live state updates.

* **gRPC Endpoints** — Structured, performant queries for applications and indexers.
* **REST API** — Human-readable HTTP endpoints for direct developer use.
* **CLI Commands** — Full control for validators, agents, and power users.

Typical queries include retrieving project or credit class details, verifying metadata IRIs, and confirming ownership or retirement records.

{% hint style="info" %}
For detailed API references and more information about Regen Ledger, visit the [Regen Ledger Documentation](https://docs.regen.network/).
{% endhint %}


---

# 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://guides.regen.network/technical-documentation/core-concepts/regen-ledger.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.