Join The Discord
Use Discord for public discussion, chain coordination, support routing, and docs feedback. Keep private keys, seed phrases, payment details, and private operating details out of chat.
What Belongs There
Discord should reduce confusion, not become the source of truth for private controls or unsupported claims.
AnnouncementsShort public updates, chain milestones, and status links.
Chain HelpWallet setup, funding-route status, transaction lookup, and official Core observatory links.
Status QuestionsPlain explanations of public labels from the website and Core surface.
Provider InterestCapacity questions, readiness labels, and non-private onboarding steps.
Docs FeedbackConfusing terms, missing explainers, and Rosetta Stone updates.
Support RoutingStart from Receipts And Support; move sensitive reports to an approved private path only when one is published.
Good First Questions
The best conversations start from public evidence and stay specific.
Can I verify the chain?
Open Core and compare the chain ID, block view, validators, and metadata.
What can I use?
Use the official surface path for wallet setup, funding coordination where available, public transaction lookup, and Infra product routes.
What is still closed?
Read Roadmap, Activation, and Readiness before assuming mainnet economics are open.
Where should feedback go?
Use Discord for docs gaps, confusing labels, broken links, or surface friction.
Support Path
- Start: read public status and the verification guide before asking for help.
- When using public chain routes: use the official funding, ledger, blocks, and status links only.
- If a transaction fails: share only public transaction IDs, wallet type, and the page where the issue happened.
- If a page looks quiet: check whether the site labels that surface as live, staged, pending, closed, or unavailable.
- Participation boundary: chain activity, Discord membership, funding-route use, bug reports, and code contributions create no allocation, reward eligibility, governance right, leverage, or future entitlement.
Safety Rules
- Never share seed phrases, private keys, passwords, or payment details.
- No direct-message support promises from unknown accounts.
- No pay-to-play coordination access.
- No exploit details in public channels.
Current Discord Readiness
These labels should change only when the public path exists.
InvitePublic
FundingOfficial chain path only
ExplorerCore observatory
Support pathPublic chat first
Where To Send People
Discord should route questions back to the public surface that owns the answer. Proposal discussion should keep using the Governance Guide so chat does not become private authority.
Core stateBlocks, validators, chain metadata, and current Core status.
Infra productBIGHT wallet, funding, upload, verify, retrieve, balances, ledger, receipts, and proof.
Bridge passageAcquisition, inventory, source pools, owner vaults, host evidence, proof, and lane-gated labels.
Liquid motionMotion, risk, settlement posture, readiness, and market-closed labels.
VerifyEvidence ladder and claim reading rules.
UpdatesDated public notes when surface posture changes.
Shown
Public updates, status labels, known issues, support prompts, and links to public status pages.
Withheld
Private controls, operator procedure, access details, sensitive reports, and private mitigation detail.
Escalated
Security reports, value custody questions, and sensitive account issues move to an approved private path once published.