CTMScan endpoints
| Network | Explorer | Verifier API | EVM RPC |
|---|---|---|---|
| Mainnet | ctmscan.io | https://ctmscan.io/api | https://public-evm-rpc.c8ntinuum.com |
| Testnet | testnet.ctmscan.io | https://testnet.ctmscan.io/api | https://public-testnet-evm.c8ntinuum.link |
API keys
CTMScan verification can be submitted anonymously, and anonymous flow is the supported path today - no signup URL exists. Anonymous traffic is rate-limited to3 r/s on both mainnet and testnet, which is sufficient for typical Hardhat verification jobs. The Hardhat Etherscan plugin still requires an apiKey field to be present in config; use the placeholder value shown below to keep the plugin configuration valid. If CTMScan exposes per-account API keys later, replace the placeholder with process.env.CTMSCAN_API_KEY.
Published scope
This guide documents the Hardhat Etherscan-compatible verification flow against CTMScan. The supported source format is Solidity Standard JSON. Flattened source, proxy verification, and library-linking behavior should be confirmed against CTMScan before relying on them in release automation. The testnet verifier API mirrors mainnet athttps://testnet.ctmscan.io/api.
Configure Verification
Add the explorer configuration tohardhat.config.js:
Verify on mainnet
With Constructor Arguments
Testnet status
| Item | Status | Source |
|---|---|---|
| Testnet chain ID | Available now | Network Information - Testnet |
| Public testnet EVM RPC | Available now | Network Information - Testnet |
| Testnet explorer | Available now | Block Explorers |
| Testnet verifier API | Available now | https://testnet.ctmscan.io/api - see Block Explorers |