> 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/security/responsible-disclosure.md). # Responsible Disclosure How to report a security vulnerability in Rome Protocol responsibly — contact channels, what to include, and disclosure guidelines. If you discover a security vulnerability in Rome Protocol, please report it responsibly. ## Reporting Email , or open a ticket in the [Rome Discord](https://discord.gg/vZ9rnCdNSB) to reach the core team privately. **What to include:** * Description of the vulnerability * Steps to reproduce * Potential impact assessment * Your contact information for follow-up ## Guidelines * Do **not** publicly disclose the vulnerability before a fix is deployed * Do **not** exploit the vulnerability beyond what is necessary to demonstrate it * Do **not** access or modify data belonging to other users * Allow reasonable time for the team to investigate and fix the issue ## Scope In scope: * Rome EVM on-chain program * Rome Proxy and Hercules services * Rome Solidity SDK and contract libraries * Oracle Gateway adapters * Bridge contracts (ERC20SPL, Factory) Out of scope: * Third-party dependencies (report to their maintainers) * Social engineering attacks * Denial of service against testnet/devnet infrastructure * Issues in deprecated or archived repositories ## Community * [Discord](https://discord.gg/vZ9rnCdNSB) — general questions and support * [Telegram](https://t.me/+tdnr-M6kcngxYzhk) — community updates * [GitHub](https://github.com/rome-protocol) — code and issue tracking --- # 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/security/responsible-disclosure.md?ask=&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.