Mining, rewards & use cases
GRID mining means completing coordinator-authorized work and passing verification. A running process or an advertised GPU is not enough: the result must become an accepted receipt before the reward can enter a signed settlement block.
The current rewards are pilot accounting on the Genesis-signed GRID chain. Nothing here guarantees income, market value, liquidity, or an exchange listing.
Operator tracks
| Track | Command | What is verified |
|---|---|---|
| Mine (PoR) | grid mine | Mine-track intent, execution result, and commitment |
| Host | grid host | Authorized useful container job and output |
| Node | grid node | Host and mine tracks in one process |
| Phoenix | grid ember NAME --start | Host, mine, named compute, and registry presence |
Verified reward flow
text
claim job
→ execute authorized payload
→ submit result commitment
→ coordinator verification
→ settlement receipt
→ deterministic PoR allocation
→ Genesis-signed block
→ peer verification
→ native GRID unclaimed balanceCurrent pilot policy
| Control | Current value | Meaning |
|---|---|---|
| Verified job event | 100 GRID | Issued only after accepted pilot work |
| Hourly compute cap | 25,000 GRID | Hard pilot emission ceiling |
| Proportional pool | 90% | Allocated by effective PoR score |
| Class-S inclusion pool | 10% | Reserved for qualifying small nodes |
| Base cluster ceiling | 5% | Limits concentration as independent clusters grow |
Start mining
bash
grid auth keyphrase
grid init --name garage --class S
# Run continuously
grid mine
# Inspect public totals
grid statsMining can be idle when no eligible work is queued. A temporary coordinator failure causes retries; it does not create a reward. Use Explorer to confirm that accepted receipts have reached a signed block.
Builder use cases
| Idea | Public surface | Pilot boundary |
|---|---|---|
| Capacity dashboard | Registry + computes APIs | Discovery only; no public host endpoint |
| Network monitor | Explorer + mesh APIs | Health and coarse presence |
| Useful job launcher | Coordinator protocol | Authorized pilot job types |
| Mesh experience | grid:// realm + registry | Requires claimed and active realm |
| Wallet dashboard | Phoenix / CLI | Genesis-signed native GRID |
What not to build
- Scrapers that try to recover IPs from the globe (coords are coarse by design)
- Clients that demand private keys to “verify” a name
- Interfaces that label pilot balances as cash or guaranteed earnings
- Services that re-publish webhook secrets to browsers
- Fake registries that impersonate grid-compute.com without TLS identity