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

# Identity Features

Osige's signature feature connects GIWA-native identity to visible pool behavior. The base DEX remains fully permissionless, while pools can offer better conditions to verified or named users, or limit liquidity provision to them.

## Two identity primitives

**Upbit Web3 Names** (`up.id`) are ENS-based, readable names in the form `username.up.id`, issued in the GIWA ecosystem.\
On Osige, an active `up.id` provides a readable display name on a [profile](/osige-docs/osige-features/profiles-and-community.md) and can unlock the benefits below in eligible pools.

**Dojang Verified Address** is GIWA's attestation service.\
A trusted issuer verifies a wallet and records that fact onchain. Osige does not view or store personal information. A Verified Address can enter compliance-oriented gated pools.

Both are external GIWA services that Osige only reads. Osige does not issue names or attestations.\
Obtain them through official GIWA channels: [Upbit Web3 Names](https://docs.giwa.io/giwa-chain/en/giwa-ecosystem/giwa-id) · [Verified Address](https://docs.giwa.io/giwa-chain/en/giwa-ecosystem/dojang/verified-address)

## What identity unlocks

<table><thead><tr><th width="168" align="center">Pool profile</th><th>Rule</th></tr></thead><tbody><tr><td align="center"><code>up.id</code> fee discount</td><td>Eligible <code>up.id</code> holders swap with discounted LP fees, using a dynamic fee with a current 50% discount prototype.</td></tr><tr><td align="center"><code>up.id</code> liquidity gate</td><td>Providing liquidity requires an active <code>up.id</code>.</td></tr><tr><td align="center"><code>up.id</code> member pool</td><td>Combines member-only liquidity with an eligibility-based fee policy.</td></tr><tr><td align="center">Dojang Verified LP</td><td>Providing liquidity requires a Dojang Verified Address.</td></tr></tbody></table>

On GIWA Sepolia, these features operate as actual pool profiles. For example, there is a BTC/USDC pool with an `up.id` fee discount and gated pools for the other profiles. At the time of an action, identity checks are performed onchain against the GIWA registry, and the pool UI shows your eligibility before you sign.

## How hooks work

These rules are implemented through an optional contract attached when a pool is created: a **hook**. A hook is part of the pool's identity.

A WETH/USDC pool with an `up.id` gate is a different pool with separate liquidity from a regular WETH/USDC pool. A hook runs only on the pool to which it is attached, and most Osige pools have **no hook**.

When [creating a pool](/osige-docs/liquidity/create-a-pool.md), you may attach a deployed identity preset or leave it out. This pool hook is unrelated to Dojang's internal “resolver hook.” They use the same word but are different features.

## Boundaries that preserve fairness

* **Swaps remain open.** Identity gates apply only to *providing liquidity* in gated pools. Anyone can swap in any pool, while fee-discount pools simply charge eligible users lower fees.
* **Exits are never blocked.** Identity hooks check entry only. Even if an `up.id` expires or an attestation is removed, liquidity removal and fee collection are always available. A change in identity cannot trap funds.
* **No personal information is held onchain or by Osige.** A hook reads only a yes/no eligibility result from the GIWA registry. Osige stores no identity documents, and Verified Address does not reveal a person's identity.
* **The design is per pool.** There is no identity rule applied across the entire protocol. Each pool's hook policy is displayed on its pool page, so check it before providing liquidity.

{% hint style="info" %}
Current identity pools are testnet prototypes. Parameters such as the discount rate are demonstration values, not permanent commitments. Contract addresses and technical mechanisms are in the [developer documentation](https://osige.gitbook.io/developers/).
{% endhint %}


---

# 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://osige.gitbook.io/osige-docs/osige-features/identity.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.