TaskVerified is a proof-first micro-work product for small operational jobs that still need a real human in the loop.
The core idea is simple: posters define tightly scoped work with explicit proof requirements, workers submit evidence instead of vague completion claims, posters review against that evidence, and approved work moves into a visible payout release flow on Solana.
One-line pitch: TaskVerified turns micro-work into a proof, review, and poster-released SOL payout loop backed by Solana devnet.
Most lightweight task products are weak at the exact point where trust matters:
- the work is underspecified
- proof is inconsistent
- review is opaque
- payout feels disconnected from the actual decision
TaskVerified is built to make that loop legible.
- A poster creates a task with a USD equivalent reward reference, deadline, and proof requirements.
- A verified worker claims the task.
- The worker submits a proof package: narrative, artifact link, file placeholder, and checklist coverage.
- The poster reviews the submission against the stated proof bar.
- Approved work advances into a poster-released payout state.
- The poster releases the payout with the correct wallet through a native Solana devnet SOL transfer.
- The product writes the result back into visible payout and trust state.
Solana is not the product story. It is the payout infrastructure.
It matters here because the product is about small units of work, and small units of work need:
- low-friction settlement
- explicit wallet custody
- a visible release moment after review
In TaskVerified, Solana shows up where it is actually useful: payout destination, poster release signature, native devnet SOL transfer, and visible completion state.
The current release model is explicit: reward amounts are USD equivalent reference values, the active payout asset is SOL, the network is Solana devnet, and payout release is poster-released after approved proof, controlled by the poster. Escrow is planned for a later release model.
Ika is a future side-track for TaskVerified, not an active integration in this build.
The current active payout rail remains SOL on Solana devnet. A later Ika-enabled release model could let posters fund work from native assets on other chains while Solana enforces the TaskVerified proof, review, and release policy through programmable, policy-bound dWallet signing. That would fit the product's trust model because payout release should remain tied to approved proof, reviewer accountability, wallet identity, and an auditable release trail.
This repo does not claim bridgeless payouts, Ika settlement, cross-chain payout execution, escrow, or 2PC-MPC signing are live today.
The current repo contains a working product loop across these areas:
- public task discovery and product story
- email and Phantom entry points into the app
- role selection and profile setup
- poster task creation
- worker task claiming
- worker proof submission
- poster review decisions
- poster payout release flow backed by Solana
- worker and poster payout visibility
- trust / reputation state updates tied to product behavior
The app is organized into four product areas:
publicworkerpostershared
These are explicit limitations, not hidden production claims:
- Escrow is planned for the next release model.
- USD amounts are reference values only, not fiat payout support.
- Active payout rail: SOL on Solana devnet.
- Release model: poster-released after approved proof.
- Proof history and payout records keep the review trail visible while dispute handling is being formalized.
- Submission artifacts use proof narrative, links, checklist coverage, and file placeholders; durable file storage is not the main claim of this build.
- Reputation is outcome-linked for the verified loop, but it is not a finished anti-fraud scoring system.
- Devnet SOL payout records are used where technical transaction evidence matters.
If you are reviewing the current product, the most important routes are:
//tasks/signin/signup/worker/tasks/worker/submissions/worker/payouts/worker/reputation/poster/tasks/new/poster/reviews/poster/payouts/app/settings
These are the surfaces that show whether the loop reads as credible end to end.
- Install dependencies:
npm install - Start the app:
npm run dev - Run tests:
npm test - Run lint:
npm run lint - Run production build:
npm run build
Required environment variables:
VITE_SUPABASE_URLVITE_SUPABASE_ANON_KEYVITE_SITE_URL
For production, set VITE_SITE_URL to the primary public domain. Browser-initiated magic links use the current app origin for /auth/callback, so every deployed domain that can request email links must also be present in the Supabase redirect allowlist.
Vercel serves TaskVerified as a client-side React app. The root vercel.json rewrites direct client-side routes to /index.html so routes such as /signup, /auth/callback, /worker, and /poster load the app instead of a Vercel 404.
Before a public or Frontier walkthrough, confirm these Supabase dashboard settings:
- Email provider enabled.
- New user signups enabled if email signup is supported.
- Site URL set to
https://taskverified.vercel.app. - Redirect URL includes
https://taskverified.vercel.app/auth/callback. - Production SMTP configured or scheduled before wider public use.
- Magic links opened in the same browser and device where the request started. If a user opens the link somewhere else, request a new link from that browser.
TaskVerified should be judged on whether it makes a trust-sensitive work loop feel operationally real:
- the work is clearly scoped
- the proof bar is explicit
- the review decision has consequence
- payout follows the decision
- Solana is used as infrastructure, not decoration
See docs/frontier-submission-pack.md for the Frontier pitch, demo script, known limitations, evidence checklist, and setup notes.