WQC Testnet
Client workspaceOverviewGuideSubmit TaskTask HistoryLedger

Start dash

Connect your PC in three steps

No programming required. Follow the steps below and your machine can start earning test $WQC within minutes.

  1. Step 1Create an account and claim faucet tokens
  2. Step 2Download wqc-miner for your OS
  3. Step 3Paste your Node Key, set a memory cap, start mining

Step 1 — Prepare on this site

  1. Create an account (or log in). You get a session wallet and a Node Key — no seed phrase to manage for testnet.
  2. Open Faucet and claim once per day (typically 1 test $WQC). Use this for activation and experimentation.
  3. Copy your Node Key from Node Key — you will paste it into the miner in step 3.
Create accountOpen faucetNode Key

Step 2 — Download the miner

Pick the build for your OS. Full list and attestation verify steps are on the downloads page.

Advanced: source builds and Docker — see world-qc/wqc-miner and world-qc/wqc-node.

All downloads + verify

Step 3 — Configure and start

  1. Launch wqc-miner from the unzipped folder or Applications.
  2. On first run, paste the Node Key from step 1 so the miner can authenticate to the swarm.
  3. Set a memory budget (UI slider or settings.toml). By default the app reserves OS headroom (1 GiB if host RAM < 16 GiB, else 2 GiB) and uses the rest as the upper bound — tighten further if you want more headroom for games or work.
  4. Press Start mining. The node joins the swarm and waits for tasks.

After you connect

  1. 01 Idle

    Detect researcher jobs or scheduled keepalive tasks

  2. 02 Bid

    Auto-bid within your memory budget

  3. 03 Compute

    GPU / unified memory runs the circuit in the background

  4. 04 Reward

    Ledger balance updates on this dashboard

Once mining is on, the cycle runs without further clicks.

Check balances and contribution history anytime under Account and Node rewards.

Troubleshooting

Node never picks up work

Your memory cap may be too low for current tasks — raise it slightly, or wait for the next keepalive / smaller slice.

I closed the app

State is saved locally. Restarting resumes where you left off; in-flight work is not thrown away.

← Back to worker guide