# Townhall #22 Date: February 20, 2026 Focus: Full onchain architecture, token infrastructure & security framework ahead of TGE {% embed url="" %} Townhall #22 covered all on-chain updates. It focused on NFT architecture that represents every stakeholder. It also covered token mint, staking, registry, and security frameworks. Everything is designed to be publicly verifiable on-chain. *** ### The 5 Solana Programs Dabba’s on-chain structure consists of: * Identity NFT programs (all stakeholders) * Bandwidth program (daily Merkle tree storage) * Token mint contract (DBT creation + emission controls) * Staking program (lock logic + reward tracking) * Wallet registry program (global on-chain index of stakeholders) Together, these allow public verification of: * Network activity * Token supply and emissions * Stake positions * Stakeholder legitimacy ### Onchain Onboarding Update Every hotspot owner will need to complete onboarding on-chain. The flow: * Mint Hotspot Owner NFT in your wallet * Bind to Hotspot Device NFT which represents a live connection on ground * Claim rewards generated from every claimed location * Swap to a different location in case of subscriber churn ### Token Mint & Emission * Pre-mint placeholder: 4B DBT (final numbers pending) * Mint authority revoked after 10B hard cap is emitted * Admin roles (Admin, Config, Daily Minter, Burn) protected by multisig + circuit breakers * Security audit in progress; report will be published before TGE *** ### Closing Notes & Takeaway This architecture provides the infrastructure backbone for a transparent, scalable, telecom-grade DePIN. On-chain updates are wrapped. Next townhalls move into tokenomics-focused discussion. --- # 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-22.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.