GpuFiles
Where the pool runs

Overview

GpuFiles is the GPU mining that lets you sell your files secretly. Sellers shred and embed their own data on their own GPU and list it with no identity; miners lend their GPU to embed and check fragments; buyers pay in USDG. Everyone who earns is paid in blind notes, so nobody can tell who sold or mined what. The same pool also embeds a client's own files for private search.

SHUFFLEDPULLRESULTSCLIENT TABTEXT → FRAGMENTSSCRUB · LANES · DECOYSMAP STAYS HEREPOOLFRAGMENTS BY IDNO ORDER · NO SOURCEDELETED ON DELIVERYMINERSONE LANE EACHWEBGPU · MINILMVECTORS BY IDCLIENT TABVECTORS → INDEXQUERY EMBEDDED HERESEARCH HERE
FIG. 5 · THE PATH OF A DOCUMENT

Three roles

  • Sellers list fragments of their own data, embedded on their own GPU, and earn when buyers pay. See Selling data.
  • Miners embed client jobs and re-check sellers' vectors in a browser tab. See Mining and checks.
  • Buyers pay per fragment through x402. See Buying data.

An embedding job, step by step

  • Your browser turns each file into sentence-sized fragments, scrubs obvious identifiers if you ask it to, adds decoy fragments and shuffles everything. The map from fragment to document never leaves your browser.
  • Every fragment carries a lane, one of 6, chosen so that two neighbours never share one. The pool gives a miner one lane of a job and at most 12 of its fragments.
  • Miners run Xenova/all-MiniLM-L6-v2 in a browser tab on WebGPU. Canary fragments with known vectors and random double assignments check their work.
  • Your browser collects the vectors, rebuilds the index locally and asks the pool to delete the job. Queries are embedded and searched in your tab.
  • Every 100 verified fragments earn a miner one blind note worth 0.004 USDG. Notes are redeemed from any wallet and paid in hourly batches through an on-chain ledger.

Who sees what

PartySeesNever sees
Client browserEverything about its own filesWho mined its fragments
PoolFragment texts while a job is open, their lanes, a hash of the job secretOrder, source document, file names, the map, who redeems which session's notes
A minerUp to 12 non-adjacent fragments of a job, shuffled with decoys and canariesAny passage, the order, the document, the client
Anyone on-chainBatch roots, payout addresses and amountsWhich mining session earned a payout

Fragments are held in the pool's database while a job runs, because a miner has to read them; they are deleted when the client collects its vectors, and in any case after 24 hours. A single fragment is a sentence or two, which is why the scrub and the lane rule exist.

Prices

Clients pay 0.05 USDG per 1,000 fragments through x402, or burn $GPUFILES once it exists, or use the daily free tier. Miners receive 80 % of the USDG price of the work they do, as notes. See Parameters.