> 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/reference/risks-and-security.md). # Risks and Security Osige is experimental testnet software.\ This page explains what can go wrong, what is protected, and what is not. ## Testnet status Osige currently operates on **GIWA Sepolia**. This means: * Test tokens, balances, rankings, and displayed values have no monetary value. * Contracts, parameters, pools, and indexing history may be redeployed or reset at any time, and positions and balances may not persist. * External production security audits are not yet **complete**. * A successful testnet transaction proves nothing about a future mainnet deployment. ## You custody your own funds Osige is self-custodial. Your wallet holds your tokens and position NFTs, and Osige contracts do not custody them. The Osige team cannot move, freeze, or recover your assets. This means **you are fully responsible for wallet security.** Anyone who knows your seed phrase owns everything in that wallet. The indexer and API that display charts and rankings are read-only convenience features. They cannot move funds, approve transactions, or change onchain state. At worst, they can show stale or missing numbers. ## Smart-contract and hook risks All DeFi has contract risk, and hooks add one form of it. A hook is additional code attached to a pool that can reject actions or change fees. Check a pool’s hook policy before providing liquidity. The pool page shows whether a hook is present and what it does. A pool without a hook has no hook rules. Current Osige identity hooks check **entry only**, meaning liquidity addition. They do not gate liquidity removal or fee collection, so an expired identity cannot trap funds. Anyone can create tokens and pools. A token symbol, logo, or screenshot proves nothing. Verify the full contract address, and do not keep token approvals larger or longer than necessary. ## LP market risks Concentrated-liquidity positions can go out of range, change token composition, and perform worse than simply holding the tokens. This is impermanent loss, explained in [Provide Liquidity](/osige-docs/liquidity/provide-liquidity.md). Displayed APR is historical information, not a promise. Shallow testnet markets magnify all of these risks. ## Phishing and fake interfaces The most common cause of lost funds is not a contract bug, but signing on a fake site. * Use only the official links in [Glossary and Official Links](/osige-docs/reference/glossary-and-links.md). Bookmark `osige.exchange`. * Read the URL, network, contract, token, and amount in every wallet prompt. * Never enter your seed phrase or private key anywhere. No normal step in an Osige, GIWA, or wallet flow requires them. * Ignore contract addresses and “support” instructions received through DMs or unsolicited messages. ## Data on screen vs. chain Charts, rankings, Upbit market comparisons, and news are display surfaces with different refresh schedules. The chain is the source of truth. If numbers differ, check your wallet and the [GIWA Explorer](https://sepolia-explorer.giwa.io), and check the live quote before signing. {% hint style="info" %} This documentation is product information, not financial, legal, or investment advice. {% 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/reference/risks-and-security.md?ask=&goal= ``` `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.