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

Frequently asked questions

Answers to the questions that come up across every part of the docs (networks, wallets, bridging, opcode differences, node operation).

Glossary

Lumia-specific and general chain terms, defined once.

Contact & support channels

The same channels as a standalone page, plus a decision tree and when to use Talk to us instead.

Choose a channel

Telegram support bot

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.

Technical support email

Developer- and integration-level problems: RPC errors, contract deployment failures, bridge/transaction issues, SDK or API bugs.

General enquiries email

Non-technical questions: partnerships, media, account/access questions that aren't a technical fault.

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:

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

• Expected on Beam testnet: the result matches Beam's chain ID; see Networks 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, not values copied from an old tutorial or bookmark.

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 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

• Beam testnet explorer: 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.