# DBT Utility

DBT is the coordination asset of the Dabba Network.\
It integrates infrastructure incentives, revenue conversion, capital formation, governance, and platform settlement into a single economic framework.

Its utility is multi-layered and anchored to real broadband adoption.

### 1. Infrastructure Incentive Layer

DBT is the primary reward asset for all network participants, including:

* Hotspot Owners
* Local Cable Operators
* Backhaul Providers
* Location Owners
* Hardware Manufacturers

Rewards are distributed per epoch and evolve from a bootstrap UBI model to a performance-weighted structure.

**Utility Outcome:**\
DBT incentivizes physical infrastructure deployment and ongoing network performance.

### 2. Revenue-Linked Demand & Burn Layer

A defined portion of broadband revenue is used to purchase and burn DBT.

Supply evolves as:

$$
S\_{t+1} = S\_t + E\_{t+1} - Burn\_{t+1}
$$

When:

$$
Burn\_t > E\_t
$$

the network becomes net deflationary.

**Utility Outcome:**\
Real-world broadband revenue is converted into token demand and structural supply tightening.

### 3. Capital Formation Layer (Bandwidth Staking)

DBT enables infrastructure-linked staking.

Each deployed hotspot unlocks:

$$
4 \text{ USD worth of staking capacity}
$$

Staking:

* Locks circulating supply
* Provides dynamic yield
* Scales proportionally with infrastructure growth

**Utility Outcome:**\
DBT coordinates capital formation for bandwidth expansion while reducing liquid supply.

### 4. Governance Layer

DBT holders participate in protocol governance, including adjustments to:

* Reward weights
* Staking parameters
* Emission decay
* Treasury usage
* Burn mechanisms

**Utility Outcome:**\
Token ownership confers economic policy influence.

### 5. Platform Settlement & Service Utility Layer

DBT functions as the transactional asset of the Dabba ecosystem.

It may be used for:

* Premium feature access
* Advertising settlement
* **Dabba hardware purchases**
* Software subscriptions
* Developer fees
* Platform service fees
* Transaction fees
* Ownership transfer fees

As platform activity increases:

$$
Burn\_t \propto Usage\_t
$$

Higher usage increases token velocity and burn rates.

**Utility Outcome:**\
Ecosystem growth compounds token demand across multiple service layers.

### Structural Design Principle

DBT utility operates across three reinforcing loops:

1. Infrastructure Growth → Token Rewards
2. Revenue Growth → Buyback & Burn
3. Platform Expansion → Transactional Usage & Burn

This creates a coordinated system where:

* Physical network growth drives issuance
* Revenue growth drives deflationary pressure
* Platform growth drives transactional demand

### Economic Positioning

DBT is not designed as a passive speculative asset.

It functions as:

* An infrastructure incentive token
* A revenue-conversion asset
* A staking coordination mechanism
* A governance instrument
* A platform settlement currency

Its long-term value proposition is structurally tied to broadband deployment, user adoption, and ecosystem activity.

### Summary

DBT integrates:

* Real-world infrastructure
* Real revenue
* Real platform usage

into a unified, supply-disciplined token economy.

As adoption increases, utility compounds across incentive, burn, staking, governance, and settlement layers — creating a demand-anchored economic system.


---

# 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/dbt-utility.md?ask=<question>
```

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.