Benchmark IDLE compute
before it earns.
Run one command on your machine. IdleBench checks your GPU, CUDA, Docker, Network and Score — then publishes a signed trust score buyers can verify before routing workloads.
npx idlebench runHow it works
Run the benchmark
where the hardware lives.
Install and run
Install Node.js 18+ from nodejs.org, then run npx idlebench run. The CLI prompts for your wallet address, resource name, and type — then starts checking your hardware.
Local verification
IdleBench inspects your GPU, VRAM, CUDA, Docker runtime, CPU cores, RAM, and network latency. All checks run on your machine. Nothing is simulated.
Score and publish
Your machine receives a final score out of 100 and a grade. The signed report uploads and creates a public verification page tied to your IDLE endpoint.
What gets checked
Your GPU score
should not be
a screenshot.
Every check runs locally on your hardware. If something cannot be detected, it is marked unknown — not assumed.
Detects GPU model and VRAM via nvidia-smi. Scores based on known performance profiles. Marks unknown if undetectable — no fabrication.
Verifies Docker is installed and running. Tests GPU passthrough via docker run --gpus all. CUDA version checked independently.
Runs lightweight CPU hash workloads and matrix calculations. GPU container tests when Docker GPU runtime is available.
Round-trip latency to IdleBench and IDLE gateway servers. Lower latency = faster response times for buyers routing workloads.
CPU core count, total RAM, and system uptime. A machine under high load scores lower on stability.
Live Leaderboard
Top verified resources.
| # | Resource | Score | Grade |
|---|---|---|---|
| 1 | Node 1 Fdv3EQ...vQzZbM | 60 | Risky |
| 2 | node-n1 7ns4fT...bgdQmP | 54 | Poor |
Output
Local checks. Public proof.
RTX 4090 Training Node
7xKXtg2CW87d...gAsU · GPU
IDLE Integration
Attach a verified
score to your IDLE
endpoint.
Buyers need proof before they route workloads. A verified score is that proof — backed by a local hardware check, not a self-reported claim.
Attach your IdleBench grade to any IDLE listing. Buyers see your score before they pay.
List resource on IDLE Protocol
earnidle.com
Run idlebench on your machine
npx idlebench run
Score published to IdleBench
Public verification page created
Badge attached to your listing
Embeddable SVG badge
Buyers verify before routing
Proof before payment
Get started
Before idle compute
earns, it needs proof.
Run one command. Prove your machine. Publish a trust score buyers can verify before they route workloads.
npx idlebench runRequires Node.js 18+ · No account · Free and open
Does IdleBench run anything without my consent?
No. Every check is interactive. IdleBench runs lightweight local commands only — GPU detection, Docker checks, CPU benchmarks. Nothing leaves your machine except the structured report you review before uploading.
What if my machine has no GPU?
CPU-only machines are handled gracefully. GPU checks report as unavailable, and the score reflects your actual configuration. CPU resources are a valid type on IDLE.
Is IdleBench affiliated with IDLE Protocol?
No. IdleBench is an independent verification layer built for the IDLE ecosystem. It produces reports that buyers and providers can trust — but it is not a product of IDLE Protocol.
How is the final score calculated?
GPU capability (30%) + Docker/CUDA readiness (20%) + benchmark performance (20%) + network latency (15%) + system stability (15%). The same formula runs in the CLI and on the server.
Can I benchmark a cloud VM?
Yes. Cloud VMs score on what they actually have. The score reflects reality — buyers know exactly what they are getting.
How long does a benchmark take?
Most benchmarks finish in 60–120 seconds. Docker GPU tests take longer on first run if the nvidia/cuda container needs to be pulled.