Quickstart

This quickstart gets you from account creation to a successful run in about 10 minutes.

Prerequisites

• One chain you want to test (mainnet, testnet, staging, or devnet)
• At least one working HTTP/HTTPS RPC endpoint URL
• Optional: a second endpoint if you want comparison verdicts

Tip

Use a non-production endpoint first. You can validate setup and suite behavior before adding production traffic paths.

Step 1: Sign up and complete onboarding

Visit dashboard.onchainprobe.com and create an account. After sign-up, a three-step onboarding wizard walks you through initial setup:

Setup (step 1)

• Team name: pre-filled from your name, optional to change.
• Chain name: the blockchain you are testing (e.g. My Testnet).
• Endpoints: paste at least one RPC URL. The wizard checks connectivity, detects the chain ID, and measures latency automatically.

Tip

Add a second endpoint to unlock cross-endpoint comparisons.

Test suites (step 2)

• Pick which test suites to run. Read-only suites are pre-selected. Pro unlocks write suites that require wallets.
• Optionally enable a public dashboard to share a status page with your team.

Note

Public dashboards are accessible to anyone with the link and are indexable by search engines. Only enable this if you want the data to be publicly visible.

Done (step 3)

The wizard creates your chain, endpoints, suites, and triggers initial test runs. Click Go to Dashboard to see results.

For details on adding more chains, endpoints, or suites after onboarding, see:

• Create a Chain
• Add Endpoints
• Configure Suites

Step 2: Confirm your first green run

A successful first run means:

• Run status is success
• Endpoint-level tests are pass/skip (no fail)
• Comparison verdict (if multi-endpoint) is pass or expected warn

If this is your first run, read Reading Results to interpret latency and assertion outputs.

Common first-run failures

• Invalid endpoint URL or DNS issue
• Upstream endpoint requires auth but credentials are missing
• Chain ID mismatch between chain config and endpoint network
• Suite parameters incompatible with your network state

Caution

If an endpoint fails continuously for 24 hours, the observer auto-disables it. Re-enable from endpoint actions after fixing root cause.

Suggested next steps

1. Add a second endpoint and enable comparison mode: Multi-Endpoint Comparison
2. Add scheduled runs: Scheduling
3. Add deployment gates from CI: CI Integration
4. Configure alerts (Pro): Alerting Setup