USERS
Send an inference request with a prompt and model.
AI inference meets GPU supply
Run AI models on shared GPU resources, or contribute your hardware. PoCC is designed to reward both available capacity and completed work.
What it is
MIRASET connects people who need AI inference with operators who provide GPU power. Submit a prompt, select a model, and receive a response from a worker running it on real hardware. Workers report usage through signed receipts for accounting and planned on-chain settlement.
Proof of Compute & Capacity (PoCC) is MIRASET's protocol for rewarding two contributions: keeping GPU resources available and completing inference jobs. Capacity incentives support available supply; compute incentives reward the work that users request. Public rewards and settlement remain under development.
How it works
Proof of Compute & Capacity (PoCC) is MIRASET's protocol for capacity and compute incentives. Workers run inference; signed receipts support usage accounting, not proof of correct AI output. Public rewards and settlement remain under development.
Send an inference request with a prompt and model.
Matches the request to a capable worker.
Run inference on GPUs and return a signed usage receipt.
Record job usage and worker attribution for accounting.
Check signatures and usage; resolve disputes before settlement.
PoCC is designed to reward available capacity and completed work.
Why use it
Use shared GPU resources for AI inference instead of buying dedicated hardware. Actual cost depends on the model, usage, and available workers.
Connect inference requests with GPU operators. Scheduling is coordinated in the MVP; decentralized scheduling is a future goal.
Contribute compatible GPUs to run inference jobs. PoCC is designed to reward available capacity and completed work; earnings are not guaranteed.
Track worker attribution and reported usage through signed receipts. Receipts do not prove output correctness or hide prompts from worker operators.
Explore models and shared compute for research, education, and open-source projects. Model access depends on worker availability.
Explore inference without owning a GPU fleet. Production availability, privacy protections, and service terms must be confirmed before deployment.

Reference wallet
The MIRASET Wallet is the reference desktop client. It connects to the RPC, runs a worker, manages accounts, and submits inference jobs — all from the same control panel.
Roadmap
Follow development from the demo toward reliable job delivery, usage accounting, and settlement. Public rewards, payments, and open worker access require separate release checks.
2 active4 upcoming
Test job submission, worker execution, and signed usage receipts.
Manage accounts, connect to the network, control a worker, and submit jobs.
Connect usage accounting, receipt batches, disputes, and settlement.
Standardize signed receipts and test challenge and dispute handling.
Evolve from the permissioned coordinator toward full decentralization.
Review payments, rewards, recovery, and security before public launch.
answers on
Quick answers to the most common questions.
For partnership, integration, validator questions, or anything that does not fit a GitHub issue, reach the Miraset team directly. Bug reports and feature requests stay on the issue tracker.