> For the complete documentation index, see [llms.txt](https://docs.fast.poker/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fast.poker/community/12-community.md).

# Discord, official links, governance, contributing

Official links, support paths, governance, and contribution notes.

## Official links

| Resource                | URL                                           |
| ----------------------- | --------------------------------------------- |
| Website                 | `https://fast.poker`                          |
| X                       | `https://x.com/FastdotPoker`                  |
| Frontend source         | `https://github.com/FastPoker/frontend`       |
| Indexer source          | `https://github.com/FastPoker/indexer`        |
| Dealer Service releases | `https://github.com/FastPoker/dealer-service` |

Only trust repository links from these docs, the official website, and the official X account.

Fast Poker will never DM you first, ask for your seed phrase, or send surprise wallet-connect links.

## Discord

The Fast Poker Discord is the main community hub for support, hand discussion, dealer coordination, and product feedback.

Use the Discord link from `https://fast.poker`.

## Support

| Need help with                           | Where to go                                                  |
| ---------------------------------------- | ------------------------------------------------------------ |
| Wallet or login issue                    | Support channel in Discord                                   |
| Bug report                               | Bug report channel in Discord                                |
| Dealer operation or Dealer License issue | Operator/dealer-license support section in Discord           |
| Security issue                           | Email `security@fast.poker` or open a private Discord ticket |

## Governance

Fast Poker uses multisig-controlled administration for sensitive protocol actions.

Large economic changes, such as rake percentages, emission curve changes, or Platform Fee policy changes, should be discussed publicly before execution.

The long-term direction is less team dependency and eventually frozen upgrade authority when the protocol is ready for that step.

## Contributing

Contribution areas:

* Custom frontend rooms and wallet flows.
* Read-only indexer integrations.
* Docs improvements.
* Frontend improvements.
* Dealer and indexer tooling.
* Security review.
* Community guides.

For larger changes, align with the team before opening a large pull request.

## Code of conduct

* Do not collude.
* Do not discuss soft-play arrangements.
* Do not scam, impersonate staff, or post malicious wallet links.
* Keep security reports private until triaged.
* Respect players, dealers, builders, and support volunteers.