Choose a task, claim the bounty, and earn SPARE™ rewards. Every contribution is cryptographically verified.
Draft a comprehensive technical whitepaper explaining the Verifiable System Emergence (VSE) architecture, its cryptographic proof chains, and the 'Three Sisters' synchronization protocol.
Conduct a thorough security audit and penetration test on all public API and authentication endpoints. Identify potential vulnerabilities like SQLi, XSS, or broken access control.
Build the frontend component for the Parallel Dispatch system. It must allow users to select multiple engines, compare outputs side-by-side, and visualize the consensus confidence scores in real-time.
Develop a complete visual identity for the Forge Engine, including a logo, color palette, and iconography that reflects its role as the 'heart of creation' in the AGI ecosystem.
Patch the integration gap where the public Factory board renders from spare_tasks while the claim endpoint mutates the separate bounties collection, causing launch cards to drift out of sync after real usage.
Secure the evidence ledger by implementing HMAC signature verification for all incoming telemetry webhooks. Ensure that only authenticated engines can write to the hash chain.
Build a robust end-to-end test suite using Playwright that covers the entire SpareTokens checkout and redemption flow, including edge cases like network timeouts and balance errors.
Migrate the heavy LandingPageClassic component to React Server Components where possible to improve LCP and reduce client-side bundle size by at least 40%.
Design a touch-optimized, space-efficient navigation system for the SpareTokens mobile terminal. Must handle complex wallet operations and task switching with minimal taps.
Tighten spacing, information hierarchy, and small-screen behavior across the Factory project cards and Parallel Dispatch panel so the launch page reads as production-ready on desktop and mobile.
Improve the current placeholder loading shells and generic error boundaries so Factory routes fail more gracefully and give contributors a clearer retry path when Firestore or API calls time out.
Develop and test 10 prompt templates specifically optimized for the CAD engine. Templates should cover common architectural patterns and mechanical engineering constraints.
Add targeted tests around the Factory live-data normalization path so the bounty board stays stable when Firestore returns missing fields, mixed timestamp shapes, or unexpected status values.
Bring the Factory bounty endpoints into the maintained API docs so contributors can understand the read, create, claim, submit, and review surfaces without digging through route handlers first.
Create a tighter icon treatment for Factory launch messaging, including variations that can sit next to cards, skill tags, or supporting marketing modules without clashing with the existing icon pack.
Create clear, concise documentation for developers on how to synchronize data and state across AGI-HIVE, SpareTokens, and the Factory using the new bridge API.
Draft a ship-ready blog post that explains what the Factory is, how SPARE-funded bounties work, and why the launch board is grounded in real repo work instead of demo-only tasks.
Write a concise tutorial that walks a new contributor from cloning the repo through picking a bounty, validating changes locally, and preparing a reviewable submission package.
Replace the current generic skeleton feel on the Factory and Factory Bounties routes with lightweight launch illustrations that reinforce the assembly-line metaphor without slowing the pages down.
Tighten the changelog so launch visitors can quickly see the Factory, SPARE, and contributor-flow milestones without wading through duplicate entries or outdated phrasing.
Pick a project or consult the collective before choosing a bounty.