Network
| Network name | Velana Chain Testnet |
|---|---|
| Chain ID | 484148 (0x76334) |
| Native coin | VELA · 18 decimals · test-only, no monetary value |
| RPC (HTTPS) | https://hubchain.thehubexchange.com/rpc |
| Explorer | https://hubchain.thehubexchange.com/explorer.html |
| Block time | About 1 second |
| EVM version | Cancun |
| Client | Anvil v1.7.1, single node |
| WebSocket | Not available |
| Faucet | 10 VELA per address / 24 h, one claim per IP / hour |
The explorer, faucet and wallet setup are served from https://hubchain.thehubexchange.com. Chain ID 484148 is an experimental selection, not registered or guaranteed unique. MetaMask users who added the network as Hub Chain should remove it and add Velana Chain again.
JSON-RPC
Signed transactions are accepted at /rpc; node administration, impersonation and unlocked-account sending are blocked. Batches are limited to 20 requests, and the endpoint is rate-limited per IP.
| Method | Use |
|---|---|
eth_chainId | Chain ID (0x76334) |
eth_blockNumber | Latest block number |
eth_getBlockByNumber / eth_getBlockByHash | Block data |
eth_getTransactionByHash / eth_getTransactionReceipt | Transaction and receipt |
eth_getBalance / eth_getTransactionCount | Account balance and nonce |
eth_getCode / eth_getStorageAt | Contract code and storage |
eth_call / eth_estimateGas | Read-only calls and gas estimates |
eth_gasPrice / eth_maxPriorityFeePerGas / eth_feeHistory | Fee data |
eth_getBlockTransactionCountByHash / ByNumber | Transaction counts |
eth_sendRawTransaction | Submit a transaction signed locally |
net_version / net_listening / net_peerCount | Network info |
web3_clientVersion / web3_sha3 | Client info and Keccak-256 |
Deploy with Foundry
Use a dedicated, disposable test wallet. Request test VELA from the faucet first. Never use a wallet holding real assets.
export VELA_RPC_URL=https://hubchain.thehubexchange.com/rpc
cast wallet import velana-test --interactive
# Enter only the dedicated test wallet's key at the prompt.
forge create contracts/HubDemoToken.sol:HubDemoToken --rpc-url "$VELA_RPC_URL" --account velana-test --broadcastIncluded working example
The operator's repository includes a verification script that creates a disposable wallet, requests 10 test VELA, deploys an OpenZeppelin ERC-20, checks its supply and transfers 123 HDT. Faucet cooldowns still apply.
node scripts/compile.cjs
node scripts/verify.cjsFaucet API
curl https://hubchain.thehubexchange.com/api/faucet \
-H 'Content-Type: application/json' \
--data '{"address":"YOUR_TEST_WALLET_ADDRESS"}'10 test VELA per address per 24 hours, one per IP per hour; five HTTP attempts per IP per hour. Successful claim reservations persist across restarts. A successful response looks like {"txHash":"0x…","amount":"10","symbol":"VELA","testOnly":true}.
Token launcher
Open the token studio, connect MetaMask, get test VELA from the faucet, choose a name, an uppercase alphanumeric ticker (1–12 characters), a 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 VELA gas.
- The token detail page shows the creator, supply, decimals and metadata, plus an address balance lookup. A full 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.
Factory configuration: launcher-config.json. Supply passed directly to createToken is in smallest units; the studio converts the human-readable amount.
Operating limits
Anvil is a development node, not a decentralised 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, token migration or payment integration is included.
The gateway exposes a small JSON-RPC allowlist and a basic recent-block explorer. Historical event indexing, WebSocket subscriptions, contract verification and an archival explorer database are not included.
State and recovery
Current balances, contract storage, blocks and transaction records are retained. Per-block archival account-state caches are pruned, so arbitrary historical state queries are not supported. The operator keeps bounded rolling recovery checkpoints on the same server; these are not off-site disaster recovery, and a crash may lose changes since the most recent checkpoint.