> For the complete documentation index, see [llms.txt](https://docs.giwa.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.giwa.io/giwa-chain/en/introduction/faq.md).

# Frequently Asked Questions

## General

### What is GIWA?

GIWA stands for **Global Infrastructure for Web3 Access**, carrying a technical meaning as well as our vision. Through GIWA, we aim to provide an **easy and accessible Web3 infrastructure for everyone**.

### What is the GIWA chain?

It is an Ethereum Layer 2 network built using the open-source **OP Stack**. Because it is fully compatible with existing EVM wallets and developer tools, both users and developers face very low barriers to entry. There is no separate native token—**Ethereum’s ETH is used directly** as the base token of the Layer 2. Transaction fees are also paid in ETH by default, and in the future, we plan to support the **Paymaster function**, allowing fees to be paid with global stablecoins.

### What makes GIWA different?

GIWA, which pursues innovation in a regulatory-friendly and trustworthy environment, aims to connect Web3 with everyday life—starting from Korea and expanding to the global stage. To achieve this, GIWA is developing **GIWA Chain**, a fast and secure blockchain infrastructure, and will provide **GIWA Wallet**, the most convenient way to access it. In addition, GIWA plans to introduce various integrated services in collaboration with institutions such as Upbit, laying the foundation for developers to build services that seamlessly blend into daily life. Furthermore, GIWA seeks to establish itself as a hub for both KRW and global stablecoins, continuously improving usability and driving financial innovation.

### Will there be a GIWA token?

GIWA Chain does not plan to issue its own token. The fundamental native token of GIWA is Ethereum’s ETH, so there is no need for a newly minted token.

### Which token is used to pay GIWA's fees?

Transaction fees (gas) are paid in ETH, but we will later support payment in various stablecoins as well. Since fees are significantly cheaper compared to Layer 1, even **micropayments and frequent transactions** can be made at low cost. By enabling stablecoins—assets with lower volatility—to be used for gas fees, GIWA provides users with greater **convenience and usability**.

***

## Service

### What is Onchian Verify?

On the GIWA Chain, authorized institutions conduct **Know Your Customer (KYC)** procedures, and the results are recorded on-chain. This allows users to reuse the same verified identity across multiple services without having to go through additional steps each time.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.giwa.io/giwa-chain/en/introduction/faq.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
