> 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/links-and-contact.md).

# Links & Contact

Official channels, key documents, and developer resources for Firelight Coverage.

### Risk Consortium

The [consortium](https://firelight.finance/#risk-consortium) launches with five confirmed members: Hypernative, Cyfrin, Credora, GFX Labs, and Native.

### General inquiries and support

Start with the official Firelight channels maintained by the Network . Authoritative channel URLs are listed below. The Phase 1 Resources page is no longer maintained.

| Channel                                          | Purpose                                                     |
| ------------------------------------------------ | ----------------------------------------------------------- |
| [Discord](https://discord.com/invite/m9APzp5KrJ) | Community discussion, general questions, ecosystem updates  |
| [X / Twitter](https://x.com/Firelightfi)         | Protocol updates, news, ecosystem content                   |
| [Blog](https://medium.com/@Firelight)            | Long-form content, launch announcements, technical writeups |

### Coverage-specific inquiries

| Topic                                               | Where to go                                                                  |
| --------------------------------------------------- | ---------------------------------------------------------------------------- |
| Institutional coverage onboarding                   | Contact form on the main Firelight site                                      |
| Protocol integration requests (new market listings) | Contact form on the main Firelight site, referencing the protocol and market |
| Risk Consortium inquiries                           | Direct outreach via the Network 's contact channel                           |
| Security disclosures                                | Official bug bounty submission channel (not public channels)                 |

Because coverage enablement is permissioned in the MVP, institutional program operators should begin with the onboarding contact form rather than public channels.

### Building on Firelight

Developers and protocol teams integrating with Firelight Coverage can review [Protocol Architecture](/protocol-architecture.md) for the coverage-specific components, and reach out through the partnerships channel for structured engagement. A public developer portal with full ABIs and integration guides is on the roadmap.

### Staying up to date

Major protocol changes, new approved markets, parameter adjustments, governance actions, material incidents, are announced through the official channels above.


---

# 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.firelight.finance/resources/links-and-contact.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.