Add your RPC nodes, run checks from the browser, and compare each endpoint against published proof and its own history — never against unrelated networks.
Add this skill to your AI
Click an agent. Paste in chat — it will save the skill for you. Or open the link and tell it to add that file.
Paste in Cursor chat. Ask it to add this skill — you do not place the file by hand.
~/.cursor/skills/dataproof-rpc-verify/SKILL.md
Test nodes in your browser for a quick one-off check. Or turn on scheduled monitoring and we'll keep checking on the interval you choose — even when the tab is closed.
In your browser
Ad-hoc checks, instant pass/fail grid, free while the tab stays open.
Hosted schedule
Scheduled checks on your interval — no browser tab required.
With a hosted schedule, we watch for failures and mismatches against published proof. When a node regresses or breaks quorum, you get notified — not just a silent cell in the grid.
How verification works
Reproducible balance checks at fixed heights — not oracle claims.
Paste RPC URLs in the browser. Each endpoint is auto-grouped by chain. Keys in the URL never leave your device unless you choose hosted monitoring.
Independent reference seeds query eth_getBalance at fixed historical blocks. The majority non-zero hex is published as proof for that network.
Each of your URLs is checked against the published etalon and its own history. We never compare unrelated providers or different chains.
Proof model
Not uptime pings — structured balance checks at known heights, compared fairly and tracked over time.
Every probe calls eth_getBalance at a pinned historical height. The reference value is quorum-backed and reproducible — not a black-box SLA number.
A node must match published etalon and its previous good result. Catch silent drift on one URL even when the network-wide proof still looks fine.
Paste a mixed list of endpoints — we group columns by chain before any comparison runs. No false fails from cross-network lookups.
Pass/fail per probe row shows which column diverged. History per URL helps you tell an isolated bad node from a wider outage.
Paste your node URLs and run a browser check. Sign in only when you want Cloud monitoring.
Start a free check