Protocol Overview
Horizon Protocol is a decentralized coordination system that connects task posters with performers through blockchain-backed escrow, location verification, and guild-based coordination. Built natively on Base L2, it provides trustless, gasless coordination for real-world tasks.
Core Actors
Posters
Users who create missions by:
- Defining task requirements and deadlines
- Depositing USDC rewards in escrow
- Optionally associating missions with guilds
- Approving completion and releasing funds
Performers
Users who execute missions by:
- Browsing available missions on the map
- Accepting missions within their capability
- Completing tasks and submitting proof
- Earning rewards, XP, and reputation
Guilds
Coordination groups that:
- Curate mission boards for members
- Maintain reputation standards
- Earn fee share on member completions
- Provide community and support
Resolvers
Trusted arbitrators who:
- Handle mission disputes
- Review evidence from both parties
- Make binding decisions on fund distribution
- Earn fees from the dispute resolution pool
Mission Lifecycle
┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ Open │────▶│ Accepted │────▶│ Submitted │
└──────────────┘ └──────────────┘ └──────────────┘
│ │ │
│ │ ▼
│ │ ┌──────────────┐
│ │ │ Completed │
│ │ └──────────────┘
│ │ │
▼ ▼ ▼
┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ Cancelled │ │ Disputed │◀────│ (or) │
└──────────────┘ └──────────────┘ └──────────────┘
State Transitions
| From | To | Trigger | Actor |
|---|---|---|---|
| Open | Accepted | acceptMission() | Performer |
| Open | Cancelled | cancelMission() | Poster |
| Open | Expired | Auto (time) | System |
| Accepted | Submitted | submitProof() | Performer |
| Submitted | Completed | approveCompletion() | Poster |
| Submitted | Disputed | raiseDispute() | Either |
| Disputed | Resolved | resolveDispute() | Resolver |
Fee Structure
When a mission completes successfully, fees are distributed to support the protocol ecosystem:
Platform Fees
| Recipient | Description |
|---|---|
| Protocol Treasury | Platform sustainability |
| Labs Treasury | R&D and development |
| Resolver Pool | Dispute resolution fund |
Guild Fees (Variable)
Guilds can earn a fee share on missions curated to their board. The fee is set by guild governance.
Performer Earnings
Performers receive the majority of the mission reward (minimum 90%), minus any applicable guild fees.
Dispute Resolution
DDR (Dynamic Dispute Reserve)
A deposit required from both parties when a dispute is raised:
- Ensures commitment from both disputing parties
- Returned to the winning party
- Partial distribution to resolver
LPP (Loser-Pays Penalty)
Additional penalty on the losing party to discourage frivolous disputes.
Security & Privacy
On-Chain Guarantees
- Reward Immutability: Mission rewards cannot change after creation
- Performer Lock: Performer address cannot change after acceptance
- Non-Custodial: Protocol cannot unilaterally modify escrow state
Privacy Features
- Location data purged after 30 days
- Live tracking requires explicit opt-in
- Encrypted data vault for user data
Technical Stack
| Component | Technology |
|---|---|
| Blockchain | Base L2 (EVM-compatible) |
| Smart Contracts | Solidity + Foundry |
| Stablecoin | USDC |
| Identity | ENS, Basenames |
| Reputation | EAS Attestations |
Deployments
Testnet (Base Sepolia)
| Contract | Address |
|---|---|
| MissionFactory | 0xee9234954b134c39c17a75482da78e46b16f466c |
| PaymentRouter | 0x94fb7908257ec36f701d2605b51eefed4326ddf5 |
| GuildFactory | 0xfeae3538a4a1801e47b6d16104aa8586edb55f00 |
| ReputationAttestations | 0xedae9682a0fb6fb3c18d6865461f67db7d748002 |
| DisputeResolver | 0xb00ac4278129928aecc72541b0bcd69d94c1691e |
| HorizonAchievements | 0x568e0e3102bfa1f4045d3f62559c0f9823b469bc |
| USDC (testnet) | 0x036CbD53842c5426634e7929541eC2318f3dCF7e |
Next Steps
- Mission Engine - Deep dive into mission mechanics
- Guild System - Learn about guild coordination
- Economics - Understand tokenomics
- Getting Started - Build your first integration