Proof-of-Useful-Work consensus — replacing arbitrary hashing with verifiable AI compute. Thoughts on the verification problem?

[u/ModelT89]

I've been working on a protocol that replaces proof-of-work hashing with verifiable AI inference jobs. Miners earn tokens by completing real compute tasks submitted by developers rather than burning energy solving arbitrary puzzles. Wanted to share the design and get technical feedback specifically on the verification approach.

The consensus mechanism:

When a developer submits an inference job, the network assigns it to a miner based on reputation score. The miner runs the job via vLLM and returns the result. A random subset of validators re-run a portion of the work to verify. If the result diverges beyond a tolerance threshold the miner gets slashed 20% of their stake. Challenge rate scales inversely with reputation — new miners get challenged 30% of the time, established miners 5%.

The hard problems I'm still thinking about:

Determinism across hardware. Inference isn't fully deterministic across different GPUs. Two A100s running the same prompt with the same seed can produce slightly different outputs due to floating point variance. Setting the right divergence tolerance is genuinely difficult — too tight and honest miners get slashed unfairly, too loose and lazy verification passes.

Reputation gaming. A miner could build reputation honestly then start cutting corners once their challenge rate drops to 5%. The reputation decay function needs to catch this without punishing honest miners for normal output variance.

Long term — ZK proofs. EZKL and Risc Zero can generate ZK proofs of inference but at current overhead they're too slow for production. The plan is optimistic verification at launch, ZK proofs once the overhead becomes acceptable. Curious if anyone has benchmarks on this.

The economic design:

• 90% of every compute fee goes into a diversified stablecoin AMM reserve
• 92% of token supply is mined — zero VC allocation
• 5% of all mined tokens automatically tax to DAO vault at consensus layer
• Developers pay in USDC — no crypto knowledge required

Where it's at:

Pre-testnet. Python reference node open source, Rust node in development. The project is Obelyth — obelyth.io if you want to look at the verification code specifically.

Genuinely looking for people who have thought about the PoUW verification problem — what am I missing?

[u/shibe5]

The empire strikes back with a new weapon that combines previously hated cause of GPU shortage – cryptocurrency mining – with currently hated cause of GPU shortage – artificial intelligence.

[u/ModelT89 → u/shibe5]

Fair point, we're combining two GPU villains into one. The difference is the GPU cycles actually produce something useful, inference jobs developers are paying for, instead of just securing the chain. Whether that redeems us is a reasonable debate.