> For the complete documentation index, see [llms.txt](https://docs.firelight.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.firelight.finance/resources/audits-and-security.md). # Audits and Security Security is central to a coverage product. If the protocol itself is exploited, it cannot credibly protect the positions it covers. This page collects audit and security resources for Firelight. ### **Phase 1: Launch Vault Audits** * [OpenZeppelin - smart contract audit](https://github.com/firelight-protocol/firelight-core/blob/main/audits/2025-07-21_OpenZeppelin_Firelight.pdf) * [Coinspect - frontend audit](https://github.com/firelight-protocol/firelight-core/blob/main/audits/2025-09-01_Coinspect_Firelight_Frontend.pdf) * [Immunefi - audit competition](https://github.com/firelight-protocol/firelight-core/blob/main/audits/2025-12-01_Firelight_Audit_Competition_Summary_Report.pdf) ### **Phase 2: Feature-Complete Launch** * Audits coming soon. ### Bug bounty program Firelight maintains an active bug bounty program covering deployed coverage contracts, integrations with external custody and liquidation venues (where Firelight code is involved), and off-chain services that write to on-chain state under authorized roles. Reports should be submitted through the official bounty channel rather than disclosed publicly. ### Monitoring integrations The protocol integrates with third-party monitoring infrastructure for real-time incident detection. Covered protocols are required to participate in this monitoring as a condition of coverage. Alerts feed the Claims Registry and the Risk Consortium when an incident is detected. ### External dependencies Firelight's security posture depends on several external components: the host chain, oracle infrastructure, custody providers, and liquidation counterparties. Due diligence on these is part of the Network's ongoing responsibility, and incidents at any of these layers are reflected in the monitored risk view for affected markets. ### Incident response If an incident affects the coverage protocol itself (rather than a covered protocol), active operations may be paused to contain the issue, the Network coordinates with service providers and auditors to assess scope, affected participants are notified through official channels, and a post-mortem is published once remediation is complete. Pausing is reserved for genuine emergencies, not routine operations. ### Where to read next * [Links & Contact](/resources/links-and-contact.md) for the bug bounty channel and full cover terms. --- # 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://docs.firelight.finance/resources/audits-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.