# Chirp's DePIN Network ## What is Chirp's DePIN Network? Chirp is a Decentralized Physical Infrastructure Network (DePIN) designed to unify the fragmented IoT landscape by enabling seamless connectivity between devices across multiple radio standards. Unlike traditional, centralized IoT networks, Chirp is community-powered, rewarding users for expanding coverage, providing real-world data, and contributing to a geolocation database. At its core, Chirp’s DePIN operates on a mesh network of Blackbird gateways—low-power terrestrial gateways deployed by individuals (Keepers) who earn CHIRP tokens for maintaining the network. These gateways support multiple wireless radio protocols, allowing businesses and developers to connect, manage, and automate IoT devices without vendor lock-in. Geopositioning is a key part of Chirp’s IoT infrastructure, enabling indoor wayfinding, power-efficient tracking, and real-world asset (RWA) applications. To accelerate the expansion of this geolocation database, Chirp gamifies network growth through Kage, a Walk, Scan, and Earn experience that incentivizes users to map wireless networks (Wi-Fi, BLE, and cell towers). By rewarding participants for collecting real-world signal data, Kage strengthens Chirp’s positioning capabilities, unlocking new use cases for automation, smart environments, and decentralized applications (DApps). The Chirp ecosystem is powered by the CHIRP token, which fuels network operations, data transactions, and governance. With built-in Data Credits (DC), every interaction within Chirp—whether registering a device, accessing network services, or claiming rewards—drives token movement and ensures sustainable network growth. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.chirptoken.io/chirp-network/chirp-iot-network.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.