Getting Help
Where to ask, how to ask, and how to disclose security findings.
Community channels
X (Twitter)
Announcements, status updates, and ecosystem news.
Discord
Real-time community and developer support.
Telegram
Community chat with a regional focus.
GitHub
Code and security advisories.
Bug reports
For bugs in the chain, the bridge, the explorer, or these docs:
- Reproduce the bug. Capture the network (mainnet or testnet), affected addresses or transaction hashes, expected behavior, and the actual output.
- Report through Discord or Telegram (links above) with the details from step 1.
- If the bug affects funds, liveness, or user data, follow the security disclosure path instead.
Security disclosures
For vulnerabilities that put funds, user data, or the chain's liveness at risk, do not open a public issue. Report privately to security@mandalachain.io.
Include in your report:
- Affected component (chain, bridge, specific contract address, etc.)
- Reproduction steps or proof of concept
- Severity assessment in your own words
- A disclosure timeline you propose
The Mandala team acknowledges receipt, triages, and coordinates fix and disclosure. A public security advisory is published once the fix ships.
How to ask a useful question
The faster a maintainer or community member can reproduce your problem, the faster you get an answer.
- What you are trying to do, in one sentence.
- What you tried, with the exact command or code.
- What happened, with the exact error message.
- Where, including chain (mainnet or testnet) and any relevant addresses or transaction hashes.
A useful question:
Deploying
Counter.solto testnet (chain20011) with Foundry.forge createfails withError: chain id 20011 not found. Myfoundry.tomlhas the testnet RPC under[rpc_endpoints]. What am I missing?
A question that takes longer to answer:
Hi, my contract doesn't work, can someone help
What this page does not cover
- Finance, accounting, or regulatory questions. Out of scope. Talk to your own counsel.
- Token price, market, or trading questions. Out of scope. These belong in community channels, not docs.
- Validator-set, DAC membership, or partnership inquiries. These go through the Mandala team directly. Reach out via Discord or Telegram and ask for the appropriate contact.

