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

# Support and community

**Who this is for:** anyone using Lumia (developers, issuers, node/wallet holders, or general users) who has hit a problem or has a question the docs don't answer.

## In this section

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Frequently asked questions</strong></td><td>Answers to the questions that come up across every part of the docs (networks, wallets, bridging, opcode differences, node operation).</td><td><a href="broken://pages/9e279a21f2eabd3e6d18f0c449e122e9053ffac8">Broken link</a></td></tr><tr><td><strong>Glossary</strong></td><td>Lumia-specific and general chain terms, defined once.</td><td><a href="broken://pages/8d9818e098eb9ccb5b47263c88aed5ad286252b6">Broken link</a></td></tr><tr><td><strong>Contact &#x26; support channels</strong></td><td>The same channels as a standalone page, plus a decision tree and when to use Talk to us instead.</td><td><a href="broken://pages/279eed6eabb30ad71ea08504a54929dd3d72d1f3">Broken link</a></td></tr></tbody></table>

## Choose a channel

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden></th></tr></thead><tbody><tr><td><strong>Telegram support bot</strong></td><td>Any issue, question, or request. Submitting here creates a support ticket and the team follows up. This is the default channel: start here if you're not sure which to use.</td><td><a href="https://t.me/lumia_helpdesk_bot">https://t.me/lumia_helpdesk_bot</a></td></tr><tr><td><strong>Technical support email</strong></td><td>Developer- and integration-level problems: RPC errors, contract deployment failures, bridge/transaction issues, SDK or API bugs.</td><td><a href="mailto:service@lumia.org">service@lumia.org</a></td></tr><tr><td><strong>General enquiries email</strong></td><td>Non-technical questions: partnerships, media, account/access questions that aren't a technical fault.</td><td><a href="mailto:general@lumia.org">general@lumia.org</a></td></tr></tbody></table>

If you're not sure which of the two email addresses applies, use the Telegram bot instead. It routes to the right team internally.

## Before you file a ticket: check you're on the right network

The single most common cause of "nothing works" reports is a wallet or app still pointed at a **retired** network that shares a similar name with the current Beam testnet. Rule this out before you write up anything else.

Run this against whatever RPC endpoint your wallet or app is actually using:

```bash
curl -X POST -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}' \
  <YOUR_RPC_URL>
```

{% hint style="warning" %}

* **Expected on Beam testnet:** the `result` matches Beam's chain ID; see [Networks](file:///5838283/reference/Networks-and-endpoints.md) for the exact hex and decimal value.
* **If you get a connection error, timeout, or a different chain ID:** you are not on Beam. In particular, chain ID `1952959480` is a separate, retired "Lumia Testnet"; its RPC and explorer are dead. It is not Beam, and no current Lumia service points at it. Reconfigure your wallet or `.env` using the values in [Networks](file:///5838283/reference/Networks-and-endpoints.md), not values copied from an old tutorial or bookmark.
  {% endhint %}

This single check resolves a large share of "transaction won't send", "wallet won't connect", and "explorer shows nothing" reports without needing to open a ticket at all.

## What to include in a good ticket

A ticket with the following gets a faster, more accurate answer than a description alone:

* **Network and chain ID:** see [Networks](file:///5838283/reference/Networks-and-endpoints.md) for the confirmed values, and verify with the `eth_chainId` check above rather than recalling it from memory.
* **RPC endpoint used:** the exact URL your wallet, script, or app is pointed at.
* **Transaction hash**, if the issue involves a specific transaction.
* **Wallet address** involved.
* **Expected result vs. actual result:** what you thought would happen, and what happened instead (include exact error text/screenshots where you have them).
* **Steps to reproduce:** the minimum sequence of actions that triggers the issue.

## What's out of scope for support

The support channels above are for technical and account issues. They are not the right channel for:

* Token price, price predictions, or trading advice
* Exchange listing status or requests
* Investment, financial, or "should I buy/hold" questions

Questions like these won't get a substantive answer through support. None of the above are things the support team is positioned to comment on.

## Check status yourself first

Before filing a ticket about downtime or missing data, check the network directly:

* Mainnet explorer: [explorer.lumia.org](https://explorer.lumia.org/)
* Beam testnet explorer: [beam-explorer.lumia.org](https://beam-explorer.lumia.org/)

If the explorer shows the chain producing blocks normally, the issue is more likely local to your wallet, RPC configuration, or network path. Include that detail in your ticket.