Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.gamercoin.com/llms.txt

Use this file to discover all available pages before exploring further.

GHX runs on three chains. The native deployment lives on Ethereum; the BNB Chain and Solana versions are bridged copies backed by locked supply on the origin chain. The addresses, decimals, and primary DEX for each deployment are below — these are the only authoritative references.
Tokens with similar names exist on every major chain. Always verify a contract address against this page or gamercoin.com before swapping, bridging, or approving spends.

​
Deployments

FieldValue
StandardERC-20
Address0x728f30fa2f100742c7949d1961804fa8e0b1387d
Decimals18
ExplorerEtherscan
Primary DEXUniswap (GHX/WETH)
A note on decimals. Ethereum and BNB Chain use 18 decimals (the ERC-20/BEP-20 default). The Solana SPL token uses 9 decimals (Solana’s convention for fungible tokens). Read decimals from the contract directly when formatting amounts in code — never assume.

​
Bridging

GHX bridging across Ethereum (ERC-20), BNB Chain (BEP-20), and Solana (SPL) — all three networks fully interconnected
All three deployments are interconnected. Live routes:
  • Ethereum ↔ BNB Chain — via cBridge (Celer Network).
  • Ethereum ↔ Solana and BNB Chain ↔ Solana — also live.
When you bridge, the source-chain supply is locked or burned and an equivalent amount is minted on the destination chain. Total cross-chain supply stays conserved minus the historical burns.

​
Audits

Public smart-contract audit reports are not linked from this documentation. The GHX whitepaper is registered with the Malta Financial Services Authority (MFSA), and the issuing entity (COINAXE LTD) is registered in Malta. For an audit attestation needed for due diligence, contact the team via the community channels.

​
Reporting a security issue

If you discover a vulnerability in any GHX deployment, please disclose it privately before posting anywhere public. The fastest paths are a direct message on the official Discord or Telegram, or an email through the contact form on gamerhash.com. Do not share exploit details or proof-of-concept code in public channels — even partial disclosure can put user funds at risk before a fix is shipped.