Skip to main content

iTake Vertical

iTake is the first production vertical deployed on Horizon Protocol. It demonstrates the MetaDAO/SubDAO pattern for real-world logistics — specifically food delivery — and serves as the template for all future verticals.

Overview​

iTake targets Lisbon and Porto as its beachhead market, connecting restaurants, drivers, and customers through Horizon's mission-based escrow system. The goal is 50 couriers and 10 restaurants within 30 days of launch.

PropertyValue
TypeMetaDAO (Vertical Platform)
VerticalFood Delivery
MarketsLisbon, Porto (Portugal)
NetworkBase Sepolia (testnet)

MetaDAO / SubDAO Hierarchy​

iTake implements a two-layer DAO hierarchy that separates platform governance from individual business operations.

┌─────────────────────────────────────────────────────────────────┐
│ iTake MetaDAO │
│ (Platform Layer) │
│ │
│ • Platform-wide governance and policies │
│ • Cross-restaurant dispute escalation │
│ • Shared driver pool coordination │
│ • Collects 0.5% MetaDAO fee │
├─────────────────────────────────────────────────────────────────┤
│ Restaurant SubDAOs │
│ │
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
│ │ Restaurant │ │ Restaurant │ │ Restaurant │ ... │
│ │ A (SubDAO) │ │ B (SubDAO) │ │ C (SubDAO) │ │
│ │ │ │ │ │ │ │
│ │ Menu mgmt │ │ Menu mgmt │ │ Menu mgmt │ │
│ │ Staff roles │ │ Staff roles │ │ Staff roles │ │
│ │ Analytics │ │ Analytics │ │ Analytics │ │
│ │ Up to 2% │ │ Up to 2% │ │ Up to 2% │ │
│ │ SubDAO fee │ │ SubDAO fee │ │ SubDAO fee │ │
│ └─────────────┘ └─────────────┘ └─────────────┘ │
└─────────────────────────────────────────────────────────────────┘

MetaDAO Responsibilities​

FunctionDescription
GovernancePlatform-wide policies, quality standards, onboarding rules
Dispute EscalationHandles cross-restaurant and driver-customer disputes
Driver PoolCoordinates the shared delivery network across all restaurants
OnboardingApproves new restaurant SubDAOs
ComplianceEnforces food safety and delivery standards

SubDAO Responsibilities​

Each restaurant operates as an independent SubDAO with full control over:

FunctionDescription
Menu ManagementCreate, update, and price menu items
Order HandlingAccept, prepare, mark orders as ready
Staff RolesManage kitchen staff permissions (owner, manager, kitchen, viewer)
AnalyticsTrack orders, revenue, ratings, popular items
Delivery ZonesConfigure delivery radius and fee structure

Fee Hierarchy​

iTake fees stack on top of the base protocol fees. The total fee is capped at 10%, guaranteeing performers (drivers) receive at least 90% of the delivery reward.

Full Fee Breakdown​

RecipientPercentageType
Driver (Performer)>=90%Guaranteed minimum
Protocol Treasury2.5%Fixed — platform sustainability
Labs Treasury2.5%Fixed — R&D and development
Resolver Pool2%Fixed — dispute resolution fund
iTake MetaDAO0.5%Variable — platform operations
Restaurant SubDAOUp to 2%Variable — set by restaurant governance

Example: EUR 20 Delivery​

Driver: EUR 18.00 (90%)
Protocol: EUR 0.50 (2.5%)
Labs: EUR 0.50 (2.5%)
Resolver: EUR 0.40 (2%)
iTake (MetaDAO): EUR 0.10 (0.5%)
Restaurant: EUR 0.40 (2%)
────────────────────────────────
Total Fees: EUR 2.00 (10%)

Fee Cap Enforcement​

The PaymentRouter contract enforces a hard cap:

  • Base protocol fees: 7% (protocol 2.5% + labs 2.5% + resolver 2%)
  • Hierarchy fees: Up to 3% (MetaDAO + SubDAO combined)
  • Maximum total: 10%
  • If a SubDAO sets its fee above the remaining cap, the contract reverts

Note: Food revenue goes directly to the restaurant. The fee breakdown above applies only to delivery fees processed through mission escrow.


How New Verticals Work​

iTake is a reference implementation. Any new vertical follows the same pattern:

1. Deploy a MetaDAO​

A new vertical deploys its own MetaDAO contract, defining:

  • Vertical-specific governance rules
  • MetaDAO fee percentage (0-1%)
  • Onboarding criteria for SubDAOs
  • Dispute escalation procedures

2. Onboard SubDAOs​

Individual businesses deploy SubDAO contracts under the MetaDAO:

  • Each SubDAO sets its own fee (0-2%)
  • Staff roles and permissions are configured per SubDAO
  • SubDAOs inherit the MetaDAO's governance framework

3. Use the Shared Infrastructure​

All verticals share Horizon's core infrastructure:

  • MissionFactory — creates missions with vertical-specific metadata
  • MissionEscrow — holds funds until completion
  • PaymentRouter — distributes fees according to the hierarchy
  • ReputationAttestations — EAS-based reputation portable across verticals
  • Geofencing — location verification for physical tasks

Planned Verticals​

VerticalTypeStatus
iTakeFood DeliveryDeployed (testnet)
ridesDAORide-sharingR&D
BuildDAOConstruction / Skilled TradesR&D

Deployed Contracts (Base Sepolia)​

ContractAddressPurpose
iTakeMetaDAO0x883B7D8CA234912B82AC9718664c2dF224c98a67Platform governance
LisboaCafe SubDAO0xAA0096E1038449220dB872c19BDF9CD6d619b7BADemo restaurant (Lisbon)
AtobaDAO SubDAO0x85fB5f85FeC3c18a47e21f22AB69A9bBB09d913fDemo restaurant

Network: Base Sepolia (Chain ID 84532). These are testnet deployments for validation.


Resources​