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

# Audit dan pelaporan kerentanan

Pelaporan kerentanan, referensi kontrak, dan pengumuman keamanan

## Laporkan kerentanan

Kirim laporan ke <security@hann.finance>. Sertakan:

1. Jaringan, kontrak, layar aplikasi, atau integrasi yang terdampak.
2. Penjelasan masalah dan dampaknya pada dana, izin, atau data.
3. Langkah reproduksi, ID transaksi, atau reproduksi minimal.
4. Alamat dompet untuk pengakuan laporan atau reward jika relevan.

Hann Finance memakai pengungkapan terkoordinasi: laporan dibagikan kepada tim agar investigasi dan perbaikan dapat dikoordinasikan sebelum diumumkan ke publik.

## Kontrak dan izin transaksi

[Smart contract](/id/developers/smart-contracts.md) mencantumkan referensi deployment. Cocokkan jaringan, token, dan alamat kontrak saat memeriksa transaksi.

Persetujuan token dan izin Permit2 menetapkan siapa yang dapat menggunakan token, jumlahnya, dan masa berlaku. Kegagalan pertukaran atau pinjaman tidak mencabut allowance yang sudah diberikan.

Batas pertukaran melindungi output dan waktu eksekusi yang ditetapkan. [Panduan Zapper](/id/protocol/zapper.md) menjelaskan izin dan operasi gabungan; [pengungkapan risiko](/id/security/risk-disclosure.md) menjelaskan kondisi likuidasi, oracle, vault, dan bridge.

## Pengumuman

Pengumuman keamanan disampaikan melalui kanal Hann Finance:

* [Situs web](https://hann.finance)
* [𝕏](https://x.com/HannFinance)
* [Discord](https://discord.gg/tzUgd7c68P)


---

# 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.hann.finance/id/security/audits-and-security.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.