Skip to content
OnchainProbe Docs

Create a Chain

A chain is the top-level container for endpoints, suites, wallets, and dashboards.

Why chain setup matters

Section titled “Why chain setup matters”

Chain metadata is used across tests and reporting:

  • chain_id helps validate RPC network identity
  • ticker appears in wallet and result views
  • explorer_url is used for quick drill-down in failures

If chain values are wrong, suites may run with incorrect assumptions.

Create a chain in the UI

Section titled “Create a chain in the UI”
  1. Navigate to Chains (/chains).
  2. Click Create Chain .
  3. Fill required fields.
  4. Save and open the chain details page.

Field reference

Section titled “Field reference”

Here’s what each field does and why it matters.

  • Name (required): human-readable name, e.g. L2 Staging
  • Chain ID (required): EVM chain ID integer
  • Ticker (optional): native token symbol, e.g. ETH
  • Explorer URL (optional): block explorer base URL. When set, run results link directly to transactions and blocks on the explorer so you can quickly verify on-chain state.

Validation checklist

Section titled “Validation checklist”

Before moving on to endpoints, make sure these are correct. Fixing them later means re-running suites.

  • Chain ID matches eth_chainId from your RPC endpoint
  • Explorer URL resolves correctly (if set)
  • Team members can access the chain page

Troubleshooting

Section titled “Troubleshooting”

If chain creation fails, here are the common causes.

  • 409 duplicate name/slug: choose a unique chain name
  • 400 invalid chain ID: pass a string representing the chain ID used by your network
  • 401/403 auth error: verify token scope and tenant access

Chain naming conventions

Section titled “Chain naming conventions”

A consistent naming scheme pays off as you add more chains. Use a pattern so suites and dashboards stay searchable:

  • <network>-<env> for example ethereum-mainnet, l2-staging
  • add region only when chain resources are region-specific
  • avoid generic names like test or prod without chain context

Sanity check with endpoint RPC

Section titled “Sanity check with endpoint RPC”

You can double-check that your chain ID is correct by querying any endpoint directly. After chain creation, verify the expected chain ID:

Terminal window
curl -sS -X POST "https://rpc.example" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'

Compare the returned hex value to your configured chain ID.

Section titled “Related operational pages”

What to do next

Section titled “What to do next”
  1. Add at least one endpoint: Add Endpoints
  2. Create your first suite: Configure Suites
  3. Learn suite model details: Test Suites