Skip to content

USAGE Miner Beta 0.2.0

Pre-release
Pre-release

Choose a tag to compare

View all tags
@Deniscoke Deniscoke released this 08 Sep 16:50
· 87 commits to main since this release
v0.2.0-beta.1
eed35aa

USAGE Miner Beta — Windows 10/11 (64-bit)

Points the AI tools already on your computer at USAGE, so the compute you were going to use anyway can be verified.

Download → install → sign in → enable mining → use AI. No Node.js required. No npm, no terminal, no token to copy, no base URL, no headers.

Install

Download USAGE-Miner-0.2.0-Setup.exe and open it. It installs for your account only — no administrator rights, no service, no scheduled task, and it does not start with Windows.

Unsigned beta — please read

This build is not code-signed. Windows SmartScreen will warn about an unrecognised publisher, and that warning is correct. Treat every unsigned download with suspicion, including this one.

What you can check instead is the file itself:

certutil -hashfile USAGE-Miner-0.2.0-Setup.exe SHA256

SHA-256

9ed4707e761267b7d09f22eeacad252fa7427984e40ba8821ba8edf8821c994e  USAGE-Miner-0.2.0.exe
61c2a1056645b9dc0fd6d2fa36e18eb44b86e6027ccfea9bfcd7b6991d18c278  USAGE-Miner-0.2.0-Setup.exe

USAGE-Miner-0.2.0.exe is byte-for-byte reproducible: build it yourself from miner/ with npm run package on Node v24.13.1 and you get that exact hash. The installer wrapper is not — the C# compiler that ships inside Windows has no /deterministic switch and stamps a fresh module id into every build.

The same manifest is served at https://usage-ten.vercel.app/api/miner/release

Privacy and credentials

  • Provider credentials remain server-side. Your OpenRouter or Anthropic key never reaches this device. The miner holds one scoped credential of its own, and USAGE talks to the provider on your behalf — that separation is the reason for routing through USAGE rather than around it.
  • USAGE does not store prompts, responses, tool arguments, or source code. It records model, token counts, cost, latency and timing. Nothing else.
  • The miner is not a trusted usage reporter. It cannot submit token counts, cost, generation ids, verification status or points. USAGE measures what it observes; the device only configures routing.
  • The device credential is stored encrypted with Windows DPAPI, scoped to your user account.
  • One exception worth knowing: enabling mining for Claude Code writes the device's miner token into its settings.json in plaintext, because that file takes literal environment values and cannot name a credential held elsewhere. It can spend your own connected provider credit; it cannot reveal a provider key, and you can revoke it at any time from /miners. Codex is unaffected.

What it changes on your machine

Turning on mining edits two settings in the AI tool's own config file, backing up what was there first. Turning mining off puts it back exactly. If a tool already points at a custom endpoint, the app stops and asks rather than overwriting it. Uninstalling offers to restore everything first.

Known limits

  • Windows only. The miner refuses to store a credential in plaintext elsewhere rather than degrade.
  • The Codex adapter is experimental — it has never carried live traffic through USAGE.
  • Free compute is provable but earns nothing, by design.

Full details: docs/MINER.md

Assets 6
Loading