EVM tools
Connect MetaMask, deploy with Remix, verify a contract with Foundry or Hardhat, and trace a transaction on the testnet.
Connect MetaMask
Add the testnet to MetaMask (or any EVM wallet) with these values. Both RPC addresses take wallet transactions: use the first one, and the second if your tool wants the EVM lane by name.
| Setting | Value |
|---|---|
| Chain ID | 101102 (0x18aee) |
| RPC URL | https://rpc-testnet.vordium.com |
| RPC URL (EVM lane) | https://rpc-testnet.vordium.com/evmrpc |
| Currency symbol | VORD |
| Decimals | 18 |
| Block explorer | https://testnet.vordscan.io |
An account needs test VORD to pay gas. The faucet gives test USDC; for test VORD, write to [email protected] with your test address.
Deploy with Remix
- Open remix.ethereum.org, write or open your contract, and compile it.
- In Deploy & run transactions, set Environment to Injected Provider – MetaMask.
- In MetaMask, switch to the testnet. Remix shows the chain ID
101102under the environment. - Press Deploy and confirm the transaction in MetaMask.
- The deployed contract appears under Deployed Contracts. Its address and the transaction are on the explorer.
Verify a contract
The explorer takes verification the way most block explorers do, at https://testnet.vordscan.io/api. It needs no API
key: tools that insist on one accept any text. Wait until the explorer shows your contract before you verify it, and
verify with the same compiler version and settings you deployed with. The examples below use Solidity 0.8.24 with the
optimizer off, the defaults of both tools.
Foundry
forge verify-contract <address> src/Counter.sol:Counter \
--chain 101102 --compiler-version v0.8.24+commit.e11b9ed9 \
--verifier custom --verifier-url https://testnet.vordscan.io/api --verifier-api-key vordscan \
--watchHardhat
With @nomicfoundation/hardhat-verify, add the testnet to hardhat.config.js:
module.exports = {
solidity: "0.8.24",
networks: {
vordiumTestnet: {
url: "https://rpc-testnet.vordium.com",
chainId: 101102,
accounts: process.env.PRIVATE_KEY ? [process.env.PRIVATE_KEY] : [],
},
},
etherscan: {
apiKey: { vordiumTestnet: "vordscan" },
customChains: [{
network: "vordiumTestnet",
chainId: 101102,
urls: { apiURL: "https://testnet.vordscan.io/api", browserURL: "https://testnet.vordscan.io" },
}],
},
sourcify: { enabled: false },
};The private key is needed only to deploy; verifying needs none. Verify from the project you deployed from, or run
npx hardhat compile first, then:
npx hardhat verify --network vordiumTestnet --contract contracts/Counter.sol:Counter <address>Once it is verified, the explorer shows the source, and getsourcecode on its API returns it.
Trace a transaction
The testnet answers the usual trace methods on its RPC address:
| Method | What you get |
|---|---|
debug_traceTransaction with no tracer | every opcode step, the gas used, whether it failed and the return value |
debug_traceTransaction with {"tracer": "callTracer"} | the call tree: from, to, input, gas used, and every inner call |
trace_transaction | the calls as a flat list |
debug_traceBlockByNumber, debug_traceBlockByHash | the trace of every transaction in a block |
callTracer is the only named tracer; another name is refused with the list of tracers it accepts. With Foundry:
cast rpc debug_traceTransaction <transaction hash> '{"tracer":"callTracer"}' --rpc-url https://rpc-testnet.vordium.comA transaction from before the network started keeping traces has none: the answer says so.
Network facts last checked against the network 2026-10-25 14:24:36 UTC · mainnet spec v28 · testnet spec v8