LogoLogo
  • welcome
    • Introduction
    • Explain Like I’m Five
    • Data Protection and Privacy
    • Network Governance
      • MIP-1
      • MIP-2
      • MIP-3
      • MIP-4
      • MIP-5
      • MIP-6
      • MIP-7
      • MIP-8
      • MIP-9
      • MIP-10
      • MIP-11
      • MIP-12
      • MIP-13
      • MIP-14
      • MIP-15
      • MIP-16
      • MIP-17
      • MIP-18
      • MIP-19
      • MIP-20
  • Contribute
    • Map With Hivemapper
      • Device Models
      • Creating a Guild
        • Adding a New Driver
        • Token Splits
        • Access Control List
        • Giving Access to Locked Devices
        • Hivemapper Guild Resources
      • Authorized Resellers
      • Accessories
      • Driver FAQs
    • Train the Map AI
      • Landmark Label
      • Position
      • Azimuth
      • Merge
      • Confirm Position & Azimuth
      • Dashcam View
      • Dashcam Tilt
      • Speed Limit
      • Speed Type
      • Turn Restrictions - No Turns 1
      • Turn Restrictions - No Turns 2
      • Confirm Attribute
      • Confirm Class
      • Stop Sign
      • Traffic Light
      • Highway Exit Signs
      • Highway Exit Info
      • Confirm Clarity of View: Interior vs Exterior
      • Confirm Clarity of View: Forward-Facing vs Side-Facing
      • Confirm Roadwork
      • Classify Roadwork
  • Use Map Data
    • Hivemapper App Developers
  • NETWORK PROTOCOL
    • Map Data Structure and Verification
    • What Is HONEY?
    • HONEY Burn and Mint
    • HONEY Token Restrictions
    • Earning HONEY
      • Reward Types
      • Global Map Progress
      • Individual Reward Factors
        • Map Tile Saturation
        • Usable Imagery
        • Clarity of View
      • Beware of Scam Airdrops
  • CAMERAS
    • Open Camera
    • HDC & HDC-S
      • Install an HDC
      • Install an HDC-S
      • Connect Dashcam to Hivemapper Companion App
      • Start Driving and Mapping - HDC/HDC-S
      • Upload Your Contributions - HDC/HDC-S
Powered by GitBook
On this page
  • Summary
  • Timeline
  • Detailed Changes
  1. welcome
  2. Network Governance

MIP-13

Map Improvement Proposal 13: Reallocating Operational Rewards Due To Edge Computing

PreviousMIP-12NextMIP-14

Last updated 2 days ago

Summary

MIP-13 established triggers for transferring 30% of the Operational Reward currently allocated to the network operator (i.e., 3% of the total weekly rewards pool) to map contributors as the edge computing power of the network increases due to the rollout of the next-generation Bee camera.

Timeline

Detailed Changes

MIP-13 established triggers for transferring 30% of the Operational Reward currently allocated to the network operator (i.e., 3% of the total weekly rewards pool) to map contributors.

The initial 5% of the Operational Reward allocated to the network operator (i.e., 0.5% of the total rewards pool) was reallocated to map contributors when the proposal was finalized.

An additional 10% (or 1% of the total rewards pool) was scheduled to be reallocated to contributors when half of weekly active cameras were next-generation models capable of generating map features on the edge. An additional 15% (or 1.5% of the total rewards pool) was scheduled to be reallocated to contributors when 95% of active dashcams are capable of generating map features on the edge.

All in all, this would result in 30% of Operational Reward being redirected to contributors, or 3% of the total reward pool on a weekly basis.

Proposal: Published
Comment Period: Complete
Outcome: Finalized