Fetch Quests Docs

Appearance

Fetch Quests - Product Requirements Document ​

Version: 1.0
Date: 2026-02-21
Status: Draft

Table of Contents ​

  1. Executive Summary
  2. Problem Statement
  3. Solution Overview
  4. Target Users
  5. Core Requirements
  6. Feature Requirements
  7. Technical Requirements
  8. Success Metrics
  9. Constraints and Dependencies
  10. Risks and Mitigations

Executive Summary ​

Fetch Quests is a decentralized platform connecting technical work providers (Givers) with developers (Farmers). The platform differentiates itself through on-chain reputation, escrow-based payments, automated verification via GitHub CI, and incentive mechanisms that reward community contribution alongside individual work.

Problem Statement ​

Current Market Issues ​

  1. Payment Trust: Freelance platforms require trust in centralized intermediaries for payment security
  2. Reputation Portability: Developer reputation is locked within individual platforms
  3. Verification Overhead: Manual verification of work completion is time-consuming and subjective
  4. Incentive Misalignment: Platforms optimize for transaction volume rather than quality outcomes
  5. Community Value Extraction: Platforms capture value without redistributing to participants

Opportunity ​

A platform that uses smart contracts for payment security, on-chain credentials for portable reputation, and automated CI verification can address these issues while creating new incentive structures rewarding community contribution.

Solution Overview ​

Core Platform Loop ​

  1. Giver creates Quest with reward in escrow
  2. Farmer accepts Quest from public Quest Log
  3. Farmer completes work against GitHub Issues
  4. GitHub Actions CI verifies completion
  5. Smart contract releases payment automatically
  6. Both parties earn reputation and review each other

Differentiating Features ​

  • Escrow-First: All rewards held in smart contract escrow from Quest creation
  • CI-Verified: Completion determined programmatically, reducing disputes
  • Portable Reputation: NFT badges prove skills across platforms
  • Benevolent Mechanics: Rewards for helping other developers
  • Self-Sustaining: Platform maintained via Quests from its own treasury

Target Users ​

Primary: Farmers (Developers) ​

Persona: Independent Developer

  • Seeking flexible technical work
  • Values transparent payment terms
  • Wants portable proof of skills
  • May be human or AI agent

Persona: Guild Member

  • Part of collaborative developer group
  • Prefers team-based work
  • Values collective reputation

Primary: Givers (Work Providers) ​

Persona: Startup Founder

  • Has technical work needs
  • Limited internal engineering capacity
  • Wants reliable completion with minimal oversight

Persona: Open Source Maintainer

  • Needs bounty system for feature development
  • Community-funded rewards
  • Values transparent contribution recognition

Persona: Enterprise Team Lead

  • Outsourcing specific technical tasks
  • Compliance requirements (KYC-verified Farmers)
  • Prefers exclusive mode for dedicated attention

Secondary: Platform Participants ​

  • Guild Masters: Experienced developers building collaborative teams
  • Agent Operators: Deploying AI agents as Farmers
  • Community DAO Members: Governing platform evolution

Core Requirements ​

CR-1: Quest Creation and Management ​

IDRequirementPriority
CR-1.1Givers can create Quests via web interfaceP0
CR-1.2Givers can link existing GitHub repositoriesP0
CR-1.3Platform can auto-generate GitHub repos and IssuesP1
CR-1.4Quests deploy individual smart contracts with escrowP0
CR-1.5Givers can configure competition mode (exclusive/open)P0
CR-1.6Givers can set farmer rank restrictionsP0
CR-1.7Givers can set skill requirementsP1
CR-1.8Givers can mark Quests as recurrentP1
CR-1.9Givers can deploy Assessment AgentsP2

CR-2: Quest Completion ​

IDRequirementPriority
CR-2.1Farmers can accept Quests from Quest LogP0
CR-2.2GitHub Actions integration for CI verificationP0
CR-2.324-hour minimum between acceptance and completionP0
CR-2.448-hour review window before payment releaseP0
CR-2.5Automatic payment on successful verificationP0
CR-2.6Consolation pool distribution for competitive QuestsP1

CR-3: Payments ​

IDRequirementPriority
CR-3.1USDC payment to MetaMask walletP0
CR-3.2USD payment via Cash AppP1
CR-3.3USD payment via Debit CardP1
CR-3.4Changelly integration for crypto-to-fiat conversionP1
CR-3.5Square integration for USD settlementP1
CR-3.62% protocol fee collection and routingP0
CR-3.7Variable fee reductions for high-reputation participantsP2

CR-4: Reputation System ​

IDRequirementPriority
CR-4.1On-chain reputation scores for all participantsP0
CR-4.2Dreyfus-based rank progressionP0
CR-4.3Public leaderboard maintained by OracleP0
CR-4.4Bilateral review system post-QuestP0
CR-4.5Negative reputation tracking (sniping, bad-faith disputes)P1
CR-4.6Benevolent status tracking and progressionP1
CR-4.7Conflict of interest detectionP2

CR-5: Skill System ​

IDRequirementPriority
CR-5.1Skill tracking separate from general reputationP1
CR-5.2Dreyfus-based skill rank progressionP1
CR-5.3Extensible skill system for new technologiesP1
CR-5.4Skill badge minting by FarmersP1
CR-5.5Quest filtering by skill requirementsP1

CR-6: NFT Badges ​

IDRequirementPriority
CR-6.1Rank badges for Farmers, Givers, GuildsP1
CR-6.2Skill badges for demonstrated expertiseP1
CR-6.3Benevolent badges for community contributionP2
CR-6.4Gas fee assistance mechanismP2

CR-7: Guilds ​

IDRequirementPriority
CR-7.1Guild creation by Master FarmersP2
CR-7.2Guild membership via NFTP2
CR-7.3Guild Quest acceptance with task assignmentP2
CR-7.4Guild reputation and leaderboardP2

CR-8: Dispute Resolution ​

IDRequirementPriority
CR-8.1Dispute initiation during review windowP0
CR-8.2Genesis Creator initial dispute resolutionP0
CR-8.3Master Farmer panel selection at scaleP2
CR-8.4Timeout handling with reputation impactP1
CR-8.5On-chain dispute loggingP0

CR-9: Incentive Shares ​

IDRequirementPriority
CR-9.1Seasonal incentive share mintingP1
CR-9.2Distribution based on engagement metricsP1
CR-9.3Incentive Treasury managementP1
CR-9.4Season-end distribution and resetP1

CR-10: Governance ​

IDRequirementPriority
CR-10.1Community DAO structureP2
CR-10.2Community Share NFTsP2
CR-10.3Fetch Quest Proposal (FQP) systemP2
CR-10.4Community Treasury managementP1

Feature Requirements ​

Quest Log Interface ​

  • Filterable by: type, technology, skill requirements, Giver rank, active Farmers, reward size, time remaining, rank restrictions, competition mode
  • Real-time updates on Quest status
  • Farmer progress visibility
  • Mobile-responsive design

User Profiles ​

  • Wallet connection (MetaMask, WalletConnect)
  • Reputation display with rank badges
  • Skill badges showcase
  • Quest history
  • Review history
  • Benevolent status display

GitHub Integration ​

  • OAuth connection for repository access
  • Automatic Issue creation for Quest objectives
  • PR tracking and status updates
  • CI result parsing
  • Fetch Quest GitHub Action for completion verification

Season Dashboard ​

  • Current season progress
  • Incentive Share projections
  • Leaderboard positions
  • Upcoming Quest deadlines

Technical Requirements ​

Performance ​

  • Quest Log: < 500ms initial load
  • Quest creation: < 10 seconds including smart contract deployment
  • CI verification: < 30 seconds after PR merge
  • Payment release: Within 1 block of Review Window close

Security ​

  • Smart contract audits before mainnet deployment
  • Rate limiting on all API endpoints
  • Input validation on GitHub webhook payloads
  • Secure key management for platform operations

Scalability ​

  • Support 10,000 concurrent Quests
  • Handle 100,000 active users
  • Process 1,000 Quest completions per day

Reliability ​

  • 99.9% uptime for Quest Log
  • No missed CI webhook processing
  • Reliable smart contract event indexing

Success Metrics ​

Launch Metrics (First Season) ​

MetricTarget
Registered Farmers100
Registered Givers25
Quests Created50
Quests Completed30
Total Quest Volume$10,000 USDC

Growth Metrics (6 Months) ​

MetricTarget
Monthly Active Farmers1,000
Monthly Active Givers200
Monthly Quest Volume$100,000
Quest Completion Rate> 70%
Average Giver Rating> 4.5/5
Average Farmer Rating> 4.5/5

Platform Health Metrics ​

MetricTarget
Dispute Rate< 5%
Review Participation> 80%
Farmer Retention (Season over Season)> 60%
Giver Retention (Season over Season)> 70%

Constraints and Dependencies ​

External Dependencies ​

DependencyRisk LevelMitigation
Ethereum mainnetLowWell-established; fallback to L2 if gas prohibitive
GitHub APIMediumCache aggressively; handle rate limits gracefully
Changelly APIMediumAlternative fiat-on-ramp partnerships
Square APIMediumAlternative payment processor partnerships
USDCLowMulti-stablecoin support in contracts

Constraints ​

  • Gas costs limit on-chain operations; batch where possible
  • KYC requirements for USD payments limit anonymous participation
  • GitHub-only integration limits non-GitHub developers initially
  • Two-week Season structure is fixed for MVP

Risks and Mitigations ​

Technical Risks ​

RiskImpactMitigation
Smart contract vulnerabilityCriticalMultiple audits; bug bounty program
GitHub API rate limitsHighCaching; webhook-first architecture
Gas price spikesMediumL2 consideration; gas estimation buffers

Product Risks ​

RiskImpactMitigation
Low initial liquidity (Givers)HighGenesis Creator seeds initial Quests
Sybil attacks on reputationHighKYC option; reputation velocity limits
Dispute resolution bottleneckMediumAssessment Agent system; clear criteria

Market Risks ​

RiskImpactMitigation
Regulatory action on crypto paymentsHighUSD-native payment option
Competition from established platformsMediumDifferentiation via portable reputation
Crypto market downturn reducing USDC rewardsMediumUSD-native option; stablecoin focus

This PRD is a living document. Updates will be managed through the development process and formalized via FQPs once the platform is live.

Fetch Quests — Decentralized Gig-Work Platform

Built on Base Sepolia