> For the complete documentation index, see [llms.txt](https://chain.gavedu.com/gavedu-by-bhumitat/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://chain.gavedu.com/gavedu-by-bhumitat/readme.md).

# Gavedu (GVDT)

Gavedu is a **DePIN** — a Decentralized Physical Infrastructure Network — being built to close India's digital divide with public Wi-Fi hardware operating under the Government of India's official **PM-WANI** framework.

The network's economics are designed around **GVDT**, a utility token on the **Base** Ethereum Layer-2 network. The design combines physical Wi-Fi nodes, localized advertising revenue, and on-chain staking.

> **Most of that design is not yet built.** Read [**Implementation Status**](/gavedu-by-bhumitat/implementation-status.md) before anything else in this paper. It states, as of a given date, exactly what exists and what does not. As of 21 August 2026: no nodes are online, no ad revenue has ever been collected, and no staking contract or vesting vault has been deployed.

Gavedu is built by **Bhumitat Technologies**, a registered PM-WANI **PDOA** (Public Data Office Aggregator) under India's Department of Telecommunications (registration `PMWANI-GUJ-364290-PDOA000004`).

## Verify, don't trust

Every material claim in this paper is checkable on-chain:

* **GVDT token:** `0x231fABEf034df3465cDA908a1cab9F942e46cB07` on Base — inspect supply, holders, and transfers on any Base scanner.
* **Node registry:** `0x45e88Bb55C77B088EF37F66A7a3eB2514D18c8C2` on Base — call `totalNodes()` yourself. Read that number for what it is: a count of **registration records written to the contract**, not a count of nodes powered on and serving traffic. See [Implementation Status](/gavedu-by-bhumitat/implementation-status.md) for the operational position.

This paper quotes **no fixed node count** in its body text; the contract read and the Implementation Status page together are the current truth.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://chain.gavedu.com/gavedu-by-bhumitat/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.