Networks & Multichain

HODL.DANCE runs on BNB Chain (BSC) mainnet today. The product and API are prepared so additional EVM chains can be added later without changing the core user model of “one market per network.”

Live network (now)
Network BNB Chain (BSC)
Chain ID 56
Native gas token BNB
Explorer bscscan.com
App hodl.dance

Official contract addresses: Contract Addresses.

How multi-chain will work (product)

When more than one network is enabled:

Surface Behavior
Discover / markets / Create Active chain only — switch network in the app, then browse or deploy on that chain
Token identity Pair (chainId, address) — the same hex address on two chains is two different tokens
Token card / page Small network badge when multi is live
Profiles One wallet (EOA) across chains; holdings and created tokens carry chainId

There is no mixed Discover feed of all chains in one list (avoids wrong routers and confusing sort).

Rewards & Leaderboard (planned multi)

Topic Decision
DANCEMAN points Counted from activity on all enabled chains (one ledger per wallet)
Leaderboard Filter Global + per chain
Payout / claim At least initially BNB on BSC (chain 56) — wallet may need to switch to BSC to claim

Details can evolve; this is the product direction locked for v1 multi.

Agents, Meme It!, Buy Bot

Feature Multi readiness
Telegram Buy Bot Works in token/bot context; supported when the bot is configured for that network
AI Agents Multi-chain packages required; on networks not ready yet → Soon in the app
Meme It! Multi-chain packages required; on networks not ready yet → Soon in the app

API: chainId (available now)

Public REST already accepts an optional chainId query parameter.
Default: 56 (BSC mainnet).

Examples:

HTTP
GET https://hodl.dance/api/tokens?chainId=56
GET https://hodl.dance/api/tokens/0xYourTokenAddress?chainId=56
  • Missing chainId → same as 56 (backward compatible).
  • Unknown / not enabled chain → 400.
  • Token objects may include a chainId field (new tokens and migrated data use 56).

Full list endpoints: API Tokens · API Overview.

For integrators (short)

  1. Prefer always sending chainId=56 so your client is multi-ready.
  2. Store tokens as (chainId, address) in your own DB.
  3. Do not assume one global unique address across networks.
  4. When a second chain ships, you will only need the new id + explorer + contracts page — not a full API redesign.

Related