How DePINly estimates Hivemapper driving earnings. Last verified 2026-05-22.
TL;DR
Drivers capture street imagery with a Bee dashcam (WiFi $489 / LTE+WiFi $589) or the phone Drive app, feeding Hivemapper's global map. Buyers burn HONEY for map access; drivers earn HONEY by distance driven × camera quality × area freshness × map demand.
Earning mechanics
- Camera multiplier: phone ≈ 0.25× / Bee WiFi 1.0× / Bee LTE+WiFi ~1.1×.
- Freshness: unmapped/stale areas pay a 2-3× bonus; re-mapping the same place decays.
- Map consumption: in-demand areas pay more.
Formula (sketch)
monthlyHoney ≈ distance × cameraMultiplier × freshnessBonus × consumptionFactor
monthlyUsd = monthlyHoney × HONEY_price ; breakeven = cameraCost ÷ monthlyUsd
Assumptions & confidence
| Assumption | Basis | Confidence |
|---|---|---|
| Bee prices ($489 / $589) | shop.beemaps.com (May 2026; Bee 2/Pro retired) | 🟢 |
| Coverage/consumption multipliers | Hivemapper public docs | 🟡 |
| Phone ≈ 25% of Bee | operator reports | 🟡 ESTIMATE |
| HONEY price | CoinGecko live | 🟢 |
NOT modeled
Exact anti-decay curve, per-region consumption demand, AI-trainer purchase cycles, HONEY volatility, fuel/time cost of driving.
Confidence rating
🟡 — Hardware prices and multiplier mechanics are documented; absolute reward levels are operator-report estimates shown as ranges.
Sources (verified 2026-05-22)
Hivemapper docs (Map Coverage / Consumption) · shop.beemaps.com · r/Hivemapper & community reports · CoinGecko (hivemapper).
Code
src/lib/calculators/hivemapper-rewards.ts · src/components/calculators/hivemapper/HivemapperCalculator.tsx · src/app/calculate/hivemapper/page.tsx
These figures are point estimates inside a wide band and depend on local demand, hardware, uptime and token price. They may be wrong in either direction. Nothing here is financial advice — always do your own research.
Methodology updated 2026-05-22 · View source on GitHub →