> 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/gavedu-by-bhumitat-1/challenges.md).

# Challenges and Opportunities

## Challenges

PM-WANI's rollout faces several real obstacles:

1. **Wi-Fi quality and user experience** — hotspot range, concurrent users per device, bandwidth availability, and data security all shape the end experience.
2. **Security threats** — data leakage, hacking, and malware put user and provider privacy at risk.
3. **Telecom incentives** — affordable public access can pressure the market share of traditional telecom providers.
4. **Rural and remote connectivity** — expanding and maintaining hotspots in low-demand, high-cost areas is logistically and financially hard.
5. **High upfront and operating cost** — hardware and running costs are a barrier for individual hosts.

## How Gavedu's design intends to address them

The mechanisms below are the intended design. Most are unbuilt as of 21 August 2026 — see [Implementation Status](/gavedu-by-bhumitat/gavedu-by-bhumitat-1/implementation-status.md).

* **Cost barrier → uptime-conditioned hardware rewards.** *(Not built.)* The design calls for a PDO buying a hotspot to receive a matching value of GVDT released over 24 months against measured uptime, lowering the upfront-cost barrier to hosting. No vesting vault has been deployed and **no cost recovery or return of capital is promised.**
* **Rural viability → ad-sponsored economics.** *(Not proven.)* The design funds access with ads rather than user recharges, with the intent of keeping hotspots viable in low-income and low-demand areas. **No ad revenue has been collected to date**, so this economics has not yet been demonstrated.
* **Trust and security → verify, don't trust.** *(Partly built.)* A public on-chain registry records node registrations, and the design conditions reward release on measured uptime. The uptime oracle does not exist yet, and the registry count is a record of registrations rather than of nodes currently serving traffic.
* **Expansion → aligned capital.** *(Not built, not open.)* The design contemplates investor staking funding new physical deployments. No staking contract exists.

The intent is that free access for users, a lowered cost barrier for hosts, and verifiable growth for investors turn PM-WANI's hardest problems into the foundation of a self-sustaining network. How much of that intent is implemented today is stated, dated, on the Implementation Status page.