Map Improvement Proposal 9 (MIP-9)

MIP-9 was written and sponsored by Josh Kauffman, community moderator

4/2 UPDATE: We are still working on the Request for Proposals and expect to publish it in early April. Stay tuned.

2/28 UPDATE: MIP-9 has been finalized as proposed. As a next step, we will publish a Request for Proposals. Thank you to everyone who shared ideas and feedback during the comment period.

Summary

This MIP is designed to promote greater transparency within the Hivemapper ecosystem by empowering Hivemapper users and HONEY token holders with high-quality data dashboards. It proposes that the Hivemapper Foundation create a Data Fund with an annual grant program of 300,000 HONEY per year, divided among as many as 10 proposals approved by the Hivemapper Foundation. If finalized, the Hivemapper Foundation would publish a formal Request for Proposal.

Background

At the time of writing, there have been more than 50,000 Hivemapper accounts created, and more than 13 million transactions executed on the Solana blockchain to reward Hivemapper ecosystem participants. But with vast amounts of data, making sense of it all can be a challenge.

We have identified at least 4 personas within the community, each with their own unique data needs.

1. Mappers: People who drive with a Hivemapper compatible camera and submit map data
2. AI Trainers: People who perform tasks to train Hivemapper’s AI models
3. Fleet Managers: People who provide cameras to other drivers in exchange for a share of rewards
4. Token Holders: People who have purchased HONEY and support the project

Some examples of things that can be built (this is a non-exhaustive list):

Dashboards with general HONEY token data

• Provide information on token minting, burning, movements
• Active accounts within the ecosystem
• Rewards by type: map coverage, AI trainers, Foundation rewards, Operational rewards
• Leaderboards
• Trading info

Dashboards with fleet data

• Fleet and driver counts
• Reward reports for fleet owners
• Fleet leaderboards

Documentation for all relevant Hivemapper data

• List of all relevant Hivemapper smart contracts and addresses, and their functions
• Decoding of the Hivemapper smart contracts

Infrastructure to support analysts

• Collaboration with Solana and analytics platforms (Dune, Flipside) to improve parsing of transactions or addition of data tables for ease of querying

Personas

Expanding on each of the personas listed above, here is a sampling of things that we’ve seen asked for within the Hivemapper community that would be relevant to each. We welcome feedback on additional data points and types of resources that would be useful.

Mappers

Users who operate a Hivemapper Dash Camera have requested to have better access to the following information.

• Total amount of HONEY rewarded each week
• Amount of HONEY burned each week
• Breakdown of rewards each week: Map Coverage, AI Trainers, Bounties, Foundation Rewards
• Amount of addresses that received rewards each week, overall and by type
• Amount of mappers that were part of a fleet versus independent drivers
• Leaderboard for rewards per address, for each week (should not include fleet owner accounts)
• Historical price feed
• Income reporting tool (input wallet address and output all rewards, timestamped, with price at that moment)

AI Trainers

Users who train the AI models have requested to have better access to the following information.

• Total amount of HONEY rewarded each week
• Amount of addresses that received AI Training rewards each week
• Leaderboard for rewards per address, for each week
• Income reporting tool (input wallet address and output all rewards, timestamped, with price at that moment)

Fleet Owners

Users who operate a Hivemapper Fleet have requested to have better access to the following information.

• Breakdown of HONEY rewarded each week to the network versus fleets
• Breakdown of their fleet’s rewards each week — in aggregate, and per driver
• Income reporting tool (input wallet address and output all rewards, timestamped, with price at that moment)
• Income reporting tool that can take as input any 3-way splits that Fleets may have in place
• Leaderboard for rewards per address within their fleet, for each week
• Leaderboard for rewards per fleet owner address, for each week

Token Holders

Users who hold the HONEY token have requested to have better access to the following information.

• Total amount of HONEY rewarded each week
• Amount of HONEY burned each week
• Breakdown of rewards each week: Map Coverage, AI Trainers, Bounties, Foundation Rewards
• Amount of addresses that received rewards each week, overall and by type
• Amount of mappers that were part of a fleet versus independent drivers
• Leaderboard for rewards per address, for each week (should not include fleet owner accounts)
• Historical price feed
• DEX volume and amount of active addresses, per week
• CEX volume, per week

Input on the proposal

The comment period was 14 days, running from Tuesday, Feb. 13, 2024 until Tuesday, Feb. 27, 2024. We are thankful for all the thoughtful feedback to help ensure we use the resources of the Hivemapper Foundation to promote a vibrant and well informed community.

Key feedback included:

• The need for APIs to provide access to off-chain network data
• The importance of transparency, and doing due diligence to ensure that analysts and developers are well qualified
• The desire for a more accurate region rewards estimator
• The concern that market volatility could result in a HONEY grant that is insufficient to maintain developer interest. We consider this data infrastructure to be key to the health of the Hivemapper Network, and as such, we do not see this 300,000 HONEY allocation as a ceiling. We will remain in close contact with developers and analysts to ensure that we are providing a fair reward for valuable contributions.