> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ostium.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Support & Community

> Where to get help, report issues, and stay connected as Ostium evolves

Ostium's community runs across five surfaces: [Discord](https://discord.com/invite/ostiumlabs) for day-to-day support and discussion, [X](https://x.com/Ostium) for announcements and market commentary, the Ostium newsletter (posted on X and sent by email) for a regular wrap of markets and product updates, the [blog](https://www.ostium.com/blog) for long-form analysis, and [GitHub](https://github.com/ostium-labs) for open-source code. Discord is the primary support channel, monitored during active trading hours across US and European time zones. The routing table below maps each type of issue to the right channel.

## Where to Get Help

Different issues route to different channels. Trading questions and UX feedback go to Discord. Security vulnerabilities go through [Ostium's Immunefi bug bounty program](https://immunefi.com/bug-bounty/ostium/) before any public disclosure. Privacy requests go to [privacy@ostium.io](mailto:privacy@ostium.io). Legal, partnership, and general inquiries go to [team@ostium.io](mailto:team@ostium.io). Using the right channel produces the fastest response and keeps sensitive matters off public timelines.

| Issue                                | Route To                                                                                                     |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------ |
| General trading question             | Discord                                                                                                      |
| A trade did not execute as expected  | Discord (include wallet address and transaction hash)                                                        |
| Deposit or withdrawal issue          | Check [Deposit](/vault/getting-started/deposit) or [Withdraw](/vault/getting-started/withdraw), then Discord |
| UI bug                               | Discord or [team@ostium.io](mailto:team@ostium.io)                                                           |
| Security vulnerability               | [Ostium's Immunefi program](https://immunefi.com/bug-bounty/ostium/) (never post publicly)                   |
| Privacy request                      | [privacy@ostium.io](mailto:privacy@ostium.io)                                                                |
| Partnership or institutional inquiry | [team@ostium.io](mailto:team@ostium.io)                                                                      |
| Legal or terms question              | [team@ostium.io](mailto:team@ostium.io)                                                                      |

## Reporting Security Issues

Report security vulnerabilities in Ostium smart contracts or infrastructure through [Ostium's Immunefi bug bounty program](https://immunefi.com/bug-bounty/ostium/) before any public disclosure. Public disclosure before reporting disqualifies the reporter from any security reward and can enable attacks against live user funds. Full scope, disclosure criteria, and reward details (up to \$200K USDC on Arbitrum) are on the Immunefi page; cross-referenced from the [Smart Contract Audits](/protocol/security/audits) page.

## Staying Informed

Protocol changes, new market listings, and product upgrades are announced on X ([@Ostium](https://x.com/Ostium)) and the [blog](https://www.ostium.com/blog). X carries real-time announcements and market commentary; the blog hosts long-form analysis. For a packaged recap, the Ostium newsletter goes out on a regular cadence, published as an X post and sent by email; subscribe at the blog URL above.

## FAQ

<AccordionGroup>
  <Accordion title="Is there an official Telegram group?">
    Ostium's primary community channel is Discord. A Telegram trading bot exists for placing trades directly from Telegram (see the [Terms of Use](/legal/terms-of-use) for details), but general community discussion, feature requests, and support happen in Discord. There is no official Ostium-run community Telegram group.
  </Accordion>

  <Accordion title="Can the Ostium team access my wallet or recover lost funds?">
    No. Ostium is non-custodial: the team cannot access your wallet, move your funds, or reverse transactions. If tokens are sent to the wrong chain or address, the team cannot recover them. Always verify the recipient address and network before sending. The [Fund Your Account](/traders/getting-started/fund-account) page covers safe bridging practices.
  </Accordion>

  <Accordion title="How do I tell a bug from a security issue?">
    Functional bugs (UI glitches, display errors, unexpected behavior that does not expose user funds) go to Discord or [team@ostium.io](mailto:team@ostium.io). Security issues (smart contract vulnerabilities, access control flaws, anything that could compromise user funds) go through [Ostium's Immunefi bug bounty program](https://immunefi.com/bug-bounty/ostium/) privately. When in doubt, treat it as a security issue and use the Immunefi channel.
  </Accordion>
</AccordionGroup>

## What to Read Next

<CardGroup cols={3}>
  <Card title="Connect Your Account" icon="wallet" href="/traders/getting-started/connect-account">
    Set up a wallet and start trading.
  </Card>

  <Card title="Smart Contract Audits" icon="shield-check" href="/protocol/security/audits">
    Independent security reviews and the full responsible disclosure process.
  </Card>

  <Card title="How Ostium Works" icon="compass" href="/protocol/how-ostium-works">
    Two-layer architecture, settlement and hedging, and the four core services that run the protocol.
  </Card>
</CardGroup>