Quiscor — Quiet power. Real pay.

01why_quiscor

Verification-first compute, honestly priced

Lightweight, embarrassingly parallel workloads — not a replacement for AWS or big-model training. That honesty is the point.

[01]module

Proof of useful work

Every task fans out to several independent workers. Results are hashed and compared; hidden honeypot tasks catch fakes. Phase 2+ payouts unlock only when the work checks out — verification is the product, not an afterthought.

[02]module

Idle-device compute

Runs in a browser tab on WASM and WebGPU. No install, no data center. Lightweight, embarrassingly parallel tasks only.

[03]module

Reputation and badges

Honest, verified work raises your score, level, and streak. Climb Bronze to Diamond on a public leaderboard.

[04]module

Rewards from real usage — or nothing

Phase 2+ payouts come from the margin on jobs requesters actually pay for. Zero usage means zero reward, and that is the honest failure mode. No payouts from new-buyer money, ever.

02how_it_works

One pipeline, three actors

A requester submits, the coordinator validates and verifies, browser workers compute. Sample trace below — run it for real on the dashboard.

✓

01 · job validationschema + input checks

≡

02 · task fan-out10 tasks × N workers

◈

03 · verification engineconsensus k-of-N + honeypots

⛓

04 · attestation & creditaccepted result → points

03proof_of_useful_work

How the network trusts a result

redundancy + consensus: The same deterministic task goes to N workers. When at least k agree, the result is accepted. Outliers are rejected before any credit or payout.
honeypot spot-checks: Around 5% of tasks have answers we already know. A worker that fails a honeypot is flagged as cheating and loses reputation.
commit → reveal: Workers commit a hash of their result before revealing it, so nobody can copy another worker and claim credit for work they did not do.
determinism first: The MVP uses deterministic workloads, so the same input gives the same output. Verification is a simple, cheap comparison.

04value_flow

Where real usage revenue goes

Phase 2+ only: a paid job funds escrow first, then accepted work releases value into transparent lanes. Every path is auditable.

USDG01 · requester

Paid compute job

A requester funds a real workload before tasks are released.

locked02 · escrow

Escrow waits for proof

Funds release only after accepted results and attestations — pull-payment, workers claim on-chain themselves.

~85%worker payout

Verified worker

Released only after useful work is accepted by consensus.

~15%protocol margin

Treasury intake

Margin routes to treasury: 50% buyback & burn, 50% staking — funded by usage only.

paid job→escrow→verified worker+protocol margin

05roadmap

Build first, launch later

phase 0Foundationdone
Spec, naming, landing page, and the tokenomics model.
phase 1MVP computedone
Real browser AI, verification by consensus and honeypots, a worker dashboard. Points only, no money.
phase 2On-chain moneyplanned
Solidity escrow for USDG on Robinhood Chain, pull-payment worker claims, wallet integration, on-chain reputation.
phase 3Token and incentivesplanned
$QSC launches only after real usage revenue exists. Staking, treasury, buyback and burn, NFT badges (ERC-721).
phase 4Scale and mobileplanned
Mobile workers (charging only), a public job marketplace, and a gradually decentralized coordinator.