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

# Audits and bug bounty

oripa.xyz audits and bug bounty: what has been checked, by whom, at which commit, and how to report what they missed.

**TL;DR:** All six oripa.xyz contracts are frozen for audit at commit `d84c69e`. Reports are linked here the day they are final. Security issues can be reported privately for a bounty.

## Audits

| Auditor  | Scope                                                                                                                                                               | Commit                                    | Report               | Date                 |
| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------- | -------------------- | -------------------- |
| BlockSec | All six contracts: OripaExchange, OripaPools, OripaToken, OripaStaking, SessionKeyManager, CctpDepositReceiver (≈1,250 nSLOC). Off-chain services are out of scope. | `d84c69e` (tag `audit-freeze-2026-11-08`) | Published when final | Published when final |

Reports are linked here the day they are final, with a summary of findings and what was fixed.

## Bug bounty

Report to: <security@oripa.xyz>.

Valid reports are rewarded case by case, by severity.

| Severity | Example                                                          |
| -------- | ---------------------------------------------------------------- |
| Critical | Move or freeze user funds; mint $ORIPA outside the curve         |
| High     | Bypass the timelock; pay a melt twice; break the pool commitment |
| Medium   | Relayer accepts a replayed or expired request                    |
| Low      | Incorrect figures on the site or in the docs                     |

**In scope.** The contracts on [Contracts](https://docs.oripa.xyz/trust/contracts.md), the relayer, and oripa.xyz.

**Out of scope.** Third-party wallets, the chain itself, phishing, denial of service, and anything that needs a leaked key.

**Rules.**

* Test on HyperEVM testnet (chain 998; API at api-testnet-hyper.oripa.xyz), not on mainnet with real users.
* Report privately first. Public disclosure after the fix is live.
* One payout per bug, to the first clear report.
* No social engineering of staff or users.


---

# 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.oripa.xyz/trust/audits.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.
