v0.1 · draft · updated Nov 17, 2026

Idlex whitepaper

A GPU supply network on Robinhood Chain: idle consumer GPUs run AI jobs, every result is checked, and every payment and reward settles onchain in 6-hour epochs.

01 · Overview

Abstract

Most gaming GPUs sit idle for most of the day while apps and AI agents pay data-center prices for compute. Idlex links those idle GPUs into one network. Builders send image and text jobs through one API and pay per job. Nodes run the jobs in the hours their owners choose, a second node checks a share of the results, and the payment leaves escrow only after the check passes.

Settlement happens on Robinhood Chain in 6-hour epochs. Each epoch seals a Merkle root of its work receipts, credits nodes $IDLEX for verified work, moves every job payment into the Holder Vault, and sends tokenized NVDA from the Holder Vault to $IDLEX holders.

02 · Overview

The problem

  • Consumer GPUs (RTX 30 and 40 series) are powerful enough for image generation and small language models, yet sit unused most hours of the day.
  • Builders and agents pay cloud rates and minimum commitments even for small, bursty workloads.
  • Open compute markets struggle with trust: a node can return a fake result and still ask to be paid.

03 · Design

Network design

PartRole
Node agentRuns on the owner's PC. Detects the GPU, runs jobs in sandboxed runtimes, signs receipts with its own node key.
SchedulerMatches jobs to nodes by VRAM, model, reputation and availability. Assigns spot-checks and closes epochs.
ContractsCheck node access, hold builder balances, rewards and the Holder Vault. Enforce every limit the scheduler works within.
Proof ledgerOne Merkle root of work receipts per epoch, written once onchain.

The node agent never holds the owner's wallet key. The owner links the node key to a wallet with one signature; the wallet holds the $IDLEX, collects its $IDLEX rewards and receives NVDA. One wallet can link one GPU, and one GPU one wallet.

04 · Design

Jobs and verification

v1 jobs are image generation (Stable Diffusion 1.5) and text generation (Qwen2.5 3B / 7B). Settings are fixed by the scheduler: the seed for images, greedy decoding for text, so another honest GPU produces a near-identical result.

  • Every job of a new node, and a random share of jobs after that, runs again on a second node.
  • Images match when their 64-bit perceptual hashes differ in at most 12 bits; text matches at 90% edit-distance similarity or more.
  • If the two disagree, a third node breaks the tie. The node in the minority earns nothing for the job and is banned; with no majority the job is disputed and the builder refunded.
  • When no other node takes a check within an hour (only one node online), the job is accepted on its own result once the output matches its signed receipt and passes a basic server check (an image of the asked size, or non-empty text). It is marked unchecked, doesn't count toward a new node's first checked jobs, and normal checks apply again as soon as a second node is online. A tiebreak with no third node in that hour ends the job as disputed.
  • Each node signs an EIP-712 receipt for every result; the receipt and the uploaded output must match.

05 · Design

Epochs and settlement

An epoch closes at 00:00, 06:00, 12:00 and 18:00 UTC. At each close the scheduler runs these steps onchain; each is idempotent and retried until it lands.

  1. 1Seal the epoch's receipt root in ProofLedger.
  2. 2Charge builders for verified jobs in ComputeCredits; the whole payment goes to the Holder Vault.
  3. 3Credit nodes their job rewards in NodeRewards: a random 100–1,000 $IDLEX per verified job, drawn from the sealed root.
  4. 4Swap the vault's USDG and $IDLEX into tokenized NVDA and pay holders their share.

06 · Economics

$IDLEX

Fixed supply of 1,000,000,000. No mint, no transfer tax, no owner.

AllocationShare
Growth reserve (use announced before launch)40%
Treasury & ecosystem15%
Liquidity ($IDLEX/USDG on Uniswap)15%
Team (12-month cliff, 24-month vesting)15%
Community & airdrop10%
Early backers (vested)5%

Uses: holding $IDLEX worth at least 100 USD opens a node and the Holder Vault's NVDA; builders can pay for jobs in $IDLEX at a 10% lower rate; holders receive tokenized NVDA from the Holder Vault.

07 · Economics

Rewards

WhoWhat, and how often
NodesA random 100–1,000 $IDLEX for every verified job, from a pool the team funds with market buys; $IDLEX only leaves the pool as node rewards. Balances build up and become claimable when the team triggers the network close onchain. Plus NVDA for the $IDLEX they hold. No USDG: job payments fill the Holder Vault.
$IDLEX holdersTokenized NVDA from the Holder Vault every epoch, split by balance and time held. Pools, contracts and the burn address don't count.
Team devicesUp to 10 whitelisted devices, public onchain. They run jobs and earn node rewards without holding $IDLEX, and share in the Holder Vault.

The Holder Vault fills from every job payment (the whole price), slashed stakes and team buys. What comes in is swapped to tokenized NVDA on Uniswap; one epoch pays out at most 20% of the vault's NVDA. The vault is closed: nothing can be withdrawn from it.

08 · Economics

Holding

  • A wallet needs $IDLEX worth about 100 USD (in the wallet or staked). $IDLEX launches on Pons, so at first the minimum is a token amount that follows the market price to stay near 100 USD: a keeper reads DexScreener and GeckoTerminal (they must agree within 10%) and may move it at most 20% per hour, and the admin can override it; the current amount is readable onchain; once a pool with a 30-minute TWAP exists, the contracts switch to that USD price, never the spot price. That one rule opens a node and NVDA from the Holder Vault.
  • If the price falls or tokens move out and the holding drops under 100 USD, the node pauses until it tops up.
  • For NVDA the holding must stay at 100 USD or more for the whole epoch. Under 100 USD gets no NVDA.
  • Faked results get the node banned. Staking is optional; staked $IDLEX counts as held and can be slashed to the Holder Vault.

09 · Security

Contracts and control

ContractHolds or does
NodeStakingNode access by holding 100 USD, optional staking, bans, whitelist (max 10)
ComputeCreditsBuilder balances, job settlement, refunds
NodeRewardsNode reward pool funded with team market buys. Pays out only to nodes; credited rewards are claimable at the network close.
HolderVaultPays NVDA to holders every epoch. Closed: nothing can be withdrawn
ProofLedgerOne receipt root per epoch
UniswapV3TwapOracle30-minute TWAP price of $IDLEX in USDG

Every admin role sits with a multisig. The scheduler's wallet works inside hard caps: at most 1,000 USD per job, each builder's own spend cap per epoch, one reward credit per ended epoch within the hourly reward budget, 20% of the vault per epoch. Builders can always refund, nodes can always move their own $IDLEX, and after the network close node rewards can be claimed even while other contracts are paused. The node reward pool has no withdraw function: $IDLEX leaves it only as node rewards. The Holder Vault and the node reward pool are closed: nothing can be withdrawn from either. The contracts get an external audit before mainnet.

10 · Security

Roadmap

  1. 1Launch (now): $IDLEX live on Robinhood Chain, contracts deployed and source-verified, network online, node client for Windows + NVIDIA.
  2. 2Jobs: real jobs from epoch 0 (18 Nov, 00:00 UTC), proof ledger, node rewards, Holder Vault payouts.
  3. 3Builders: public API, Linux client, audit, multisig admin.
  4. 4Open market: node pricing, reputation tiers, stronger proofs, agent toolkit.

11 · Security

Risks

  • Rewards are paid in $IDLEX; their value depends on the market price and can fall.
  • Holder Vault payouts depend on network usage and are not guaranteed.
  • Verification is probabilistic: a cheater can go unchecked on some jobs before being caught.
  • Smart contracts can have bugs despite tests and audits.
  • Rules on tokens differ by country. Nothing in this paper is financial advice.

This is a draft. Numbers and mechanics can change before launch.

Read nextThe docs: run a node, rewards, contracts