MIP-26
The full proposal is published on Medium: Map Improvement Proposal 26 (MIP-26).
Overview
Section titled “Overview”This proposal modernizes how the network calculates consumption rewards and charges developers for access. It introduces a demand-driven, hex-based work order infrastructure to match actual demand and distribute consumption rewards more effectively.
Why This Matters
Section titled “Why This Matters”The original reward model hadn’t kept pace with network evolution, including Edge AI workloads and hex-based contribution systems. This update ensures contributors benefit when demand for data increases, while developers pay based on the geographic coverage their applications consume.
How It Works
Section titled “How It Works”Map Credit Gateway
Section titled “Map Credit Gateway”All network access flows through Map Credits, which developers purchase by burning HONEY. Credits are non-transferable and persist until spent.
Hex-Based Work Orders
Section titled “Hex-Based Work Orders”Developers specify target hexes and plugin workloads, setting a priority bid in Map Credits (above network minimums). The bid determines assignment priority when orders overlap, but doesn’t affect pricing. Work orders last one reward epoch (one week).
Key mechanics:
- Developer sets priority bid; pricing remains flat per unique hex
- Minimum of one validated device completion per hex required
- Multiple work orders can overlap; highest bidder gets priority assignment
- Subsequent completions in fulfilled hexes cost developers nothing additional
Overlapping Work Orders
Section titled “Overlapping Work Orders”When multiple work orders target the same hex, the higher-bid order receives validated completions first. Once fulfilled, lower-bid orders activate for the same hex. Each order maintains independent hit counters.
Duration and Auto-Renewal
Section titled “Duration and Auto-Renewal”Work orders default to one-epoch duration but can be flagged for auto-renewal across consecutive epochs, provided the developer maintains sufficient Map Credit balance.
Work Order Pricing
Section titled “Work Order Pricing”Charged once per unique hex fulfilled during the epoch, regardless of how many validated device completions occur in that hex. The rate is approximately 0.011 Map Credit per H3 L12 hex cell, or 0.5 credits per unique kilometer.
Historical Imagery Pricing
Section titled “Historical Imagery Pricing”Historical data (retained one year) uses a hex-based access model. Each Map Credit provides one week’s access to a single hex. Pre-MIP-26 imagery requires a 0.2 HONEY burn per credit consumed.
Consumption Rewards
Section titled “Consumption Rewards”Rewards accrue when Map Credits are consumed and distribute weekly. The total work order consumption reward pool equals 25% of the Map Credits consumed during that period, reminted as HONEY.
Contributors earn proportionally based on validated completions per hex: their share equals completion count in each hex divided by total completions, weighted by credits consumed.
Impact
Section titled “Impact”For Contributors:
- Consumption rewards tie directly to validated work completion
- Higher bids affect assignment priority, not per-hex earnings
- Fair distribution based on device availability and compute work
- Map coverage rewards remain unchanged
For Developers:
- Precise geographic and workload control via hex-based orders
- Priority assignment for higher bids
- Payment only for fulfilled hexes
- Auto-renewal enables persistent regional coverage
- Unused credits retain value
For the Network:
- Real-time demand signaling through work orders
- Extensibility beyond mapping to any compatible compute workload
- Protocol retains control over pricing floors and validation standards
- Map Credits remain the unified gateway currency
Contributor Questions
Section titled “Contributor Questions”Will other rewards change? No — only consumption reward calculation changes. Coverage rewards, operational rewards, and staking remain identical.
How do I earn consumption rewards? Complete validated work in hexes with active work orders. Your reward share reflects proportional validated completions per hex, weighted by consumed credits.
Can I earn from multiple overlapping orders? Yes. Each work order is rewarded independently, so devices completing tasks for multiple overlapping orders in the same hex earn from each.
What if my region lacks active work orders? You continue earning map coverage rewards for availability and geographic participation. Consumption rewards concentrate where developers post paid orders.
Do I need to change how I operate? No. Devices automatically receive plugin assignments when entering targeted hexes. No manual management required.
Developer Questions
Section titled “Developer Questions”How do I request data? Post a work order specifying hexes, plugin workload, and priority bid. Credits consume only upon hex fulfillment.
What happens to unused credits? They remain in your balance for future work orders — no expiration or penalty.
Can I cancel orders or get refunds? Orders can be cancelled. At epoch close, the protocol reconciles consumed and refundable credits, applying a 4% cancellation fee to refundable amounts. Fees support contributor rewards.
How do I maintain continuous coverage? Flag work orders for auto-renewal. They remain active across epochs automatically, as long as your Map Credit balance suffices.