# Townhall #20 Date: January 16, 2026 Focus: Bringing the network on-chain, growth & upcoming milestones {% embed url="" %} Townhall #20 covered key developments in bringing Dabba’s operational data fully on-chain. It also covered improvements to visibility and tooling, growth impact for LCOs, and upcoming milestones. *** ### Onchain Data & Transparency Goal Publish full network data on-chain. Make it verifiable and queryable by anyone. Iteration 2 of the Open Network Data Layer launched. Initial rollout of on-chain data included: * Hotspot Device NFTs * Compressed NFTs used * Bandwidth tracked per epoch (24-hour period) using Merkle trees * WD number to identify unique hardware * Invoice of customer payments * Each device stores references to all five stakeholders that keep the connection live * LCO Partner NFTs * Compressed NFTs used * Stored fields include company name, GST registration identifier, coordinates, network size, wallet info, and links to connections * Compressed data via Merkle trees and PDAs for efficiency * Network data will be live on Solana testnet, followed by mainnet deployment ### Onchain Playground A new GitBook section captures network data on Solana testnet. It lets the community explore and verify data directly. UI and visualisation improvements are coming. A glossary will clarify technical terms. *** ### Closing Notes and Takeaway * Transparency first: core network data is being brought fully on-chain for independent verification * Structured execution: updates are rolling out in phases to keep on-chain data and tokenomics clear * Real-world impact: success is measured by outcomes for LCOs (subscriber growth, revenue, sustainability) Explore the MVP playground to understand the network with numbers. This will help refine tokenomics together over the upcoming townhalls. --- # 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://gitbook.dabba.network/community-townhall/townhall-20.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.