
$GPUFILES
$GPUFILES does two things in the pool: it pays for embedding when burned, and it raises what a miner's notes pay out.
Burn to embed
- Send $GPUFILES to
0x000000000000000000000000000000000000dEaDfrom your wallet. The app does it in one click on the payment step. - Sign the message
GpuFiles burn <tx hash>with the same wallet and send both, base64 JSON, in theX-GpuFiles-Burnheader of a job submission. - The pool reads the transaction receipt, sums the $GPUFILES transfers to the dead address, checks the signature against the sender, and credits 2,000 $GPUFILES per 1,000 fragments. That rate is a parameter set below the USDG price; it is published at
/api/v1/params. - A burn is recorded by its hash. Its unused credit carries over to later jobs that present the same burn; nobody else can use it without the burner's signature.
Holders earn more per note
When a batch settles, a payout address holding 100,000 $GPUFILES or more is paid 1.25 times the face value of each note. The balance is read at settlement, on the address being paid, so mining itself stays unlinked from any wallet.
Where the fees go
Creator fees from $GPUFILES are sent to the pool vault, the same wallet that receives USDG from clients and pays miners. The ledger shows every batch the vault has paid out.
Both mechanisms switch on when the token address is set; until then the pool runs on USDG alone.