> For the complete documentation index, see [llms.txt](https://docs.rome.builders/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rome.builders/id/keamanan/responsible-disclosure.md).

# Pengungkapan yang Bertanggung Jawab

Cara melaporkan kerentanan keamanan di Rome Protocol secara bertanggung jawab — saluran kontak, apa yang perlu disertakan, dan panduan pengungkapan.

Jika Anda menemukan kerentanan keamanan di Rome Protocol, harap laporkan secara bertanggung jawab.

## Pelaporan

Email <rome@romeprotocol.com>, atau buka tiket di [Rome Discord](https://discord.gg/vZ9rnCdNSB) untuk menghubungi tim inti secara privat.

**Apa yang perlu disertakan:**

* Deskripsi kerentanan
* Langkah-langkah untuk mereproduksi
* Penilaian dampak potensial
* Informasi kontak Anda untuk tindak lanjut

## Pedoman

* Lakukan **bukan** mengungkapkan kerentanan secara publik sebelum perbaikan diterapkan
* Lakukan **bukan** mengeksploitasi kerentanan melebihi yang diperlukan untuk mendemonstrasikannya
* Lakukan **bukan** mengakses atau mengubah data milik pengguna lain
* Berikan waktu yang wajar bagi tim untuk menyelidiki dan memperbaiki masalah

## Ruang lingkup

Termasuk dalam ruang lingkup:

* program on-chain Rome EVM
* layanan Rome Proxy dan Hercules
* SDK Solidity Rome dan pustaka kontrak
* adapter Oracle Gateway
* kontrak jembatan (ERC20SPL, Factory)

Di luar ruang lingkup:

* Dependensi pihak ketiga (laporkan kepada pemeliharanya)
* Serangan rekayasa sosial
* Serangan penolakan layanan terhadap infrastruktur testnet/devnet
* Masalah pada repositori yang sudah tidak digunakan lagi atau diarsipkan

## Komunitas

* [Discord](https://discord.gg/vZ9rnCdNSB) — pertanyaan umum dan dukungan
* [Telegram](https://t.me/+tdnr-M6kcngxYzhk) — pembaruan komunitas
* [GitHub](https://github.com/rome-protocol) — kode dan pelacakan masalah


---

# 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.rome.builders/id/keamanan/responsible-disclosure.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.