> 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/profiles-and-community.md).

# Profiles and Community

Every wallet on Osige has a public profile.\
Osige also provides a community feed where you can add verifiable onchain evidence to market discussion.

This page covers both features.

## Your profile

Open [Profile](https://osige.exchange/profile) or view any address at `/profile/<address>`. Profiles show:

* **Identity:** A wallet address, a readable display name resolved from `up.id` or ENS, and an automatically generated avatar. An address with an Upbit Web3 Name displays an `up.id` field. See [Identity Features](/osige-docs/osige-features/identity.md).
* **Five tabs:** *Overview*, *Posts*, *Portfolio* (holdings, allocation, and OLP positions), *Activity* (indexed onchain history), and *Jose-On* (the [tax analysis screen](/osige-docs/osige-features/jose-on-tax.md)).
* **Connections:** You can follow other wallet profiles. Select the follower or following count to open the complete list.

Profiles display public data.\
Profiles, badges, and follower counts do not prove trading skill or predict future performance.

## Badges and titles

Profiles can earn **community badges**, shown in the badge section of the profile:

| Badge                   | How to earn it                                                                                                                                    |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| LP Farmer               | Create one or more Osige liquidity positions                                                                                                      |
| Whale Watcher           | Complete one or more verified copied positions                                                                                                    |
| 10k Holder / 100k Whale | Combined value of recognized assets and LP positions is at least $10k / $100k. This is a dynamic condition and can be removed if the value falls. |
| Active Voice            | Publish 10 or more active community posts                                                                                                         |
| Trending Author         | Receive 10 or more likes on active posts                                                                                                          |
| KOL / Osige             | Granted manually by the Osige team                                                                                                                |

Choose one earned badge as your **primary badge** under Edit profile → Primary community badge. It appears beside your name on every post and comment.

## Community login

All profiles are public.

Posting, commenting, reacting, following, and editing a profile require **SIWE (Sign-In with Ethereum)**. This is a gas-free wallet signature that proves ownership of the address.

Osige sessions expire and have no token-approval permissions, so they cannot move funds. Before signing, always check that the message explicitly names `osige.exchange`.

## Posts, reactions, and topics

The community feed appears alongside market pages. You can find it in the token-specific feed on the [Trade page](/osige-docs/trading/swap.md), the topic feed in Explore, and the author feed on a profile. Posts support:

* Text and up to two images, in png/jpeg/gif/webp format, 5 MB each
* **Like/dislike** reactions and threaded comments
* **Topic tags** for a token or pool, connecting discussion to that market

If you post in a token or pool topic while actually holding that token or providing liquidity to that pool, your post receives a **Holder** or **LP** proof badge for the topic. This provides trustworthy context without leaving the feed.

## Protocol embeds: posts with evidence

In the composer, you can attach the following live protocol data to a post:

* **Holdings**: A token you own
* **Swap**: One of your transactions
* **Liquidity position**: One of your OLPs

You can select only from your own onchain activity.

Before rendering a card, the server independently verifies it against chain state. Embedded numbers are chain-derived values, not values entered by the author. An embed shows its verification status, and a card that fails verification is rejected.

On Osige, “I bought here” can be a verifiable claim rather than a screenshot.

{% hint style="info" %}
Community content, including posts, comments, reactions, and profiles, is application data stored by the Osige service rather than onchain. It may be modified or reset during the testnet period.

Never post a seed phrase, private key, or personal information. No legitimate user or Osige team member will ask for them.
{% 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/profiles-and-community.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.