Wingbits primary sources
Reviewed: 2026-05-13 UTC
Core product framing
- https://wingbits.com/
- Public homepage framing Wingbits as a reward-based flight-tracking network using specialized hardware, cryptographically signed data, and proof-of-location.
- https://docs.wingbits.com/introduction/readme.md
- Best concise official explanation of the project’s core value: a global ADS-B data network that rewards contributors and positions itself against incumbent volunteer-based flight-tracking feeds.
- https://docs.wingbits.com/introduction/for-the-depin-crew.md
- Good short source for the commercial-demand narrative and the claim that supply growth should be constrained by actual data demand.
Spatial control surfaces and reward policy
- https://docs.wingbits.com/project/wingbits-litepaper.md
- Best source for the distinction between station location claims and rewarded coverage hexes, the basic token allocation, and the use of H3 hexes in coverage design.
- https://docs.wingbits.com/project/wingbits-faq.md
- Especially useful for the explicit res6 location-hex versus res3 coverage-hex distinction and the rule that location claims are not themselves part of rewards calculation.
- https://docs.wingbits.com/rewards/how-rewards-work.md
- Best source for the live reward mechanics: 24 WINGS per active coverage hex per day, PageRank-based base rewards, Early Participant Rewards, and low-altitude airport-specific reward pools.
- https://docs.wingbits.com/get-started/how-to-claim-your-station-location.md
- Good source for the non-transferable location reservation flow and the practical rule that one station claims a physical installation area while later relocation outside the reserved hex breaks reward eligibility.
- https://wingbits.com/blog/pagerank-reimagined
- Best source for the actual intuition behind the PageRank adaptation: attention network, coverage network, concentration reduction, and why strategic relevance matters more than raw volume.
Hardware trust and proof-of-location path
- https://docs.wingbits.com/project/wingbits-approved-hardware-program.md
- Best source for the concrete hardware trust assumptions: ADS-B receiver, GNSS chip, cryptographic security chip, on-device client, and manufacturer whitelisting requirements.
- https://docs.wingbits.com/introduction/readme.md?ask=What%20makes%20Wingbits%20data%20cryptographically%20secure%20and%20provably%20accurate%2C%20and%20what%20role%20does%20specialized%20hardware%20play%3F
- Useful doc-query answer summarizing the role of the security chip, GNSS, GeoSigner, and signed location-backed data.
- https://docs.wingbits.com/project/wingbits-litepaper.md?ask=How%20does%20Wingbits%20use%20H3%20hexes%2C%20location%20claims%2C%20proof%20of%20location%2C%20and%20network-score%20or%20PageRank-based%20rewards%20to%20control%20coverage%20and%20data%20quality%3F
- Useful doc-query answer that cleanly summarizes the system-level split between claim one physical spot and reward one shared sky grid.
Main takeaways from this pass
- Wingbits is best understood as an aviation-data network with explicit spatial reward governance, not just as a generic DePIN miner fleet.
- The crucial mechanism split is between physical station admission and rewarded airspace coverage: res6 location hexes control physical duplication, while res3 coverage hexes generate the economic reward pool.
- The PageRank-based reward layer is the main analytical reason the entry belongs in the corpus. It turns flight-tracking rewards into a network-centrality problem rather than a simple box-uptime or raw-throughput contest.
- Hardware admission is unusually important here. Wingbits is not only crowdsourcing data; it is constraining trust through approved hardware, GNSS-backed proofs, secure elements, and backend whitelisting.
- The project is a strong comparison point for GEODNET, Witness Chain, and Offline Protocol because it mixes physical placement policy, hardware trust, and commercialized real-world data, but it does so through aviation observation rather than GNSS corrections or latency-witness proofs.