← Hub Chain

Developer quickstart

Local EVM proof of concept. Test assets only. NFA/DYOR.

Network

Chain ID: 484148 (0x76334)
Native gas coin: HUB, 18 decimals
RPC: https://hubchain.thehubexchange.com/rpc
Explorer / faucet / wallet setup: https://hubchain.thehubexchange.com
Block interval: 1 second. EVM target: Cancun.

The localhost addresses work on the box only, not on your own device. When opening this site through its configured public tunnel, use that page's HTTPS origin followed by /rpc. Quick-tunnel URLs can change after a restart. Chain ID is an experimental local selection, not registered or guaranteed unique.

Deploy with Foundry

Use a dedicated, disposable test wallet. Request test HUB from the faucet first. Never use a wallet holding real assets.

export HUB_RPC_URL=https://hubchain.thehubexchange.com/rpc
cast wallet import hub-test --interactive
# Enter only the dedicated test wallet's key at the prompt.
forge create contracts/HubDemoToken.sol:HubDemoToken   --rpc-url "$HUB_RPC_URL" --account hub-test --broadcast

Run from /workspace/hubchain using foundry.toml. Foundry CLI is optional and not installed by this build; the included ethers deployment was verified instead.

Included working example

cd /workspace/hubchain
node scripts/compile.cjs
node scripts/verify.cjs

The verification script creates a disposable wallet, requests 10 test HUB, deploys an OpenZeppelin ERC-20, checks its supply, and transfers 123 HDT. Faucet cooldowns still apply; repeating within one hour from the same IP is intentionally rejected. Read verification.json for the already deployed contract and transaction hashes.

Faucet API

curl https://hubchain.thehubexchange.com/api/faucet   -H 'Content-Type: application/json'   --data '{"address":"YOUR_TEST_WALLET_ADDRESS"}'

10 test HUB per address per 24 hours, one per IP per hour; five HTTP attempts per IP per hour. Per-address and per-IP successful claim reservations persist across restarts. Signed transactions are accepted at /rpc; node administration, impersonation and unlocked-account sending are blocked there.

Launch a testnet token

Open the token studio →. Connect MetaMask, get test HUB from the faucet, choose a name, uppercase alphanumeric ticker (1–12 characters), human-readable supply and decimals (0–18), then confirm the transaction. Logo URL and description are optional. The full initial supply goes to the connected wallet.

The factory deploys an OpenZeppelin ERC-20 with no token owner or extra minting function. Names are limited to 64 UTF-8 bytes, logo URLs to 512 bytes and descriptions to 1,024 bytes. Logos must use HTTPS and are stored as metadata links, not uploaded. Creation events and the registry are on-chain. There is no platform charge; creation consumes test HUB gas.

The token detail page displays the creator, supply, decimals and metadata, plus an address balance lookup. A complete holder directory and transfer-history index are not included. No bonding curve or trading pool is created. These demonstration contracts have not been independently audited. NFA/DYOR.

cd /workspace/hubchain
node scripts/compile-factory.cjs
node_modules/.bin/forge test --use ./scripts/solc-forge.cjs -vv
node scripts/launcher-ui-test.cjs

Factory configuration: launcher-config.json. Supply passed directly to createToken is in smallest units; the studio converts the entered human-readable amount. Tests use a local standard-JSON adapter for the pinned solc-js compiler and do not require downloading a native compiler.

Operating limits

Anvil is a development node, not a decentralized consensus network. There is one operator, no independent validators, no uptime promise, no external audit and no production readiness. The operator can change or reset state. No bridge, real CRAIC migration or payment integration is included. Transaction history and EVM state snapshots live on this box. A box shutdown or disk loss makes the service unavailable; a crash may lose changes since the most recent 10-second snapshot.

The gateway exposes a deliberately small JSON-RPC allowlist and a basic recent-block explorer. Historical event indexing, WebSocket subscriptions, contract verification services and an archival explorer database are not included. Free public hosting is not configured. Hosting may impose bandwidth, storage, traffic and lifetime limits.