Overview
Idlecash turns unused computer resources into productive capacity — and directs the resulting revenue toward assets you choose.
The whole product is one loop:
Device → Earnings → Assets
- Device. Your computer has capacity it isn't using: CPU, GPU, storage and bandwidth.
- Earnings. When the conditions you set are met, Idlecash makes that capacity available to supported workloads — from your browser, or later from an optional desktop app. Those workloads pay for what they use.
- Assets. Revenue is paid out to a wallet you control, and you convert it into the assets you picked.
You don't find workloads, configure jobs, run nodes or move rewards around. Idlecash handles the infrastructure; you decide the rules and where the value goes.
What works today
| Part | Status |
|---|---|
| Website: product pages, dashboard, allocation, asset pages | Live |
| Wallet connection on Robinhood Chain | Live |
| Live asset prices and TradingView charts | Live |
| Converting USDG or ETH into your chosen assets, signed in your wallet | Live |
| Earn Mode in the browser (conditions, CPU limit, capacity check) | Live |
| Paid workloads | Not connected yet |
| Desktop app (GPU, storage, bandwidth; runs with no tab open) | Later, optional |
| Idlecash service (workload matching, revenue attribution, payouts) | In development |
| Allocation registry contract | Written, not deployed |
Until paid workloads are connected, the dashboard shows empty earnings. Nothing is estimated or simulated.
Where to go next
- Architecture — how the pieces fit together, and how the repository is organised.
- Earn Mode — the rules a device follows before it contributes anything.
- Earn Mode in the browser — what the browser reads, and how it limits CPU.
- Desktop bridge — the local protocol between the website and the desktop app.
- Assets and conversions — supported assets, prices, charts and how conversions work.
- Security — the security model, stated plainly.
- Risks — what can go wrong, and what Idlecash does not promise.