> For the complete documentation index, see [llms.txt](https://docs.ggez.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ggez.one/readme.md).

# Introduction

## Welcome to GGEZ1 Chain

GGEZ1 is a Layer 1 blockchain ecosystem dedicated to tokenizing high-value sustainability assets to create stable and transparent asset-backed cryptocurrencies. The platform is designed to bridge Web3 technology with real-world investments in sustainability, promoting Regenerative Finance (ReFi) to accelerate the transition to a sustainable economy​.

GGEZ1 is built on the Cosmos SDK, ensuring scalability, interoperability, and cost efficiency. It provides an infrastructure that enables fast, low-cost transactions, smart contract functionality, decentralized applications (dApps), and asset-backed cryptocurrencies like the GG ReFi Coin and GGEZ1 Governance Coin​.

This documentation provides technical guides, APIs, and smart contract integrations to help developers build on the GGEZ1 blockchain. Whether you're creating a dApp, issuing tokenized assets, or exploring ReFi opportunities, GGEZ1 provides the infrastructure for the next generation of sustainable finance.


---

# 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.ggez.one/readme.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.