# Mint, Buyback & Burn

### Overview

The Dabba Network implements a structured revenue allocation framework designed to:

• Reduce circulating DBT supply\
• Align incentives across infrastructure contributors\
• Maintain operational sustainability\
• Introduce predictable token demand driven by real revenue

All buybacks are funded exclusively through fiat revenue generated from broadband service operations.

### Revenue Allocation Framework

Let:

Rₜ = Total fiat revenue generated in month t

Revenue is allocated across stakeholder categories according to fixed minimum thresholds.

The allocation structure is as follows:

| Category                           | Allocation % | Treatment                  |
| ---------------------------------- | ------------ | -------------------------- |
| LCO Buyback (P2)                   | ≥ 45%        | Tokens bought and burned   |
| Bandwidth Provider Settlement (P1) | ≥ 30%        | Tokens acquired and burned |
| Hotspot Owner Reserve (P4)         | 5%           | Tokens bought, not burned  |
| Operating Company (Dabba Inc) (P3) | 20%          | Retained for operations    |

Total allocation:

Rₜ = R\_LCO + R\_BW + R\_HO + R\_INC

Where:

R\_LCO ≥ 0.45 Rₜ\
R\_BW ≥ 0.30 Rₜ\
R\_HO = 0.05 Rₜ\
R\_INC = 0.20 Rₜ

#### Revenue-Backed Buyback Commitment for LCO and Bandwidth Providers

In every epoch, 37% of total DBT emissions are allocated to infrastructure operators, including Local Cable Operators (LCOs) and Bandwidth Providers. These participants are essential to the physical expansion and maintenance of the network.

To align token economics with real-world revenue, the protocol commits a minimum of 75% of all fiat revenue generated from broadband operations to purchasing DBT from these operator categories.

This commitment is revenue-based, not token-based.

The number of tokens repurchased each epoch depends on:

* Total revenue generated
* The prevailing market price of DBT

**How It Works**

If revenue is strong relative to token price, the protocol may absorb the entire 37% allocation issued to LCOs and Bandwidth Providers in that epoch. In such cases, all acquired tokens are burned, creating meaningful supply reduction.

If revenue is insufficient to absorb the full 37%, the protocol still deploys 75% of revenue toward buybacks. Any remaining tokens not purchased remain with operators, who may retain them or sell them on the open market.

This design ensures:

* A structural, revenue-backed floor of token demand
* Predictable buy pressure independent of market sentiment
* Operator flexibility under varying economic conditions
* Long-term alignment between network growth and token supply

As revenue scales and emissions decline over time, the system naturally increases its capacity to absorb operator allocations, strengthening supply discipline.

This mechanism directly links broadband adoption to token demand, creating a closed-loop economic model grounded in real-world usage.

**Working formula**

Let:

* E\_t = total DBT emitted in epoch t
* R\_t = total fiat revenue in epoch t
* P\_t = epoch-average DBT price

The total DBT allocated to LCO and Bandwidth Providers is:

$$
T\_{LBW,t} = 0.37 , E\_t
$$

The protocol’s minimum buyback budget for these categories is:

$$
R\_{buy,t} = 0.75 , R\_t
$$

The maximum quantity of DBT that can be purchased using this budget is:

$$
B\_{LBW,t} = \frac{0.75 , R\_t}{P\_t}
$$

**Buyback Outcomes**

**Full Absorption**

If:

$$
B\_{LBW,t} \ge T\_{LBW,t}
$$

the protocol can absorb the entire LCO and Bandwidth allocation. Tokens acquired under this mechanism are burned.

**Partial Absorption**

If:

$$
B\_{LBW,t} < T\_{LBW,t}
$$

the unpurchased balance remains with operators:

$$
U\_t = T\_{LBW,t} - B\_{LBW,t}
$$

This remaining balance may be retained or sold on secondary markets by LCOs and Bandwidth Providers. This mechanism ensures a revenue-backed minimum level of token demand while maintaining operator flexibility under varying revenue and token price conditions.

#### Why This Structure Is Strong

• Buyback is revenue-driven, not token-driven\
• As revenue grows, absorption approaches or exceeds 37%\
• As emissions decay 10% annually, required revenue to absorb 37% declines\
• Long-term, revenue can exceed emission supply

It creates:

Revenue floor → Buy pressure floor → Supply discipline

### Hotspot Owner Liquidity Pool (5% Revenue Allocation)

In addition to the LCO and Bandwidth buyback commitments, the protocol allocates **5% of monthly fiat revenue** to a dedicated Hotspot Owner (HO) liquidity pool.

This pool is designed to provide predictable, revenue-backed liquidity to hotspot operators.

#### Structure

Let:

* R\_t = total fiat revenue in epoch t

The monthly Hotspot Owner liquidity allocation is:

$$
R\_{HO,t} = 0.05 , R\_t
$$

These funds are used by the Foundation to purchase DBT from Hotspot Owners at prevailing market prices.

The quantity of tokens that can be absorbed in epoch t is:

$$
B\_{HO,t} = \frac{0.05 , R\_t}{P\_t}
$$

Where:

* P\_t = average DBT market price during the epoch

***

### Liquidity Function

This 5% of revenue is allocated for liquidity functions as a **recurring protocol-sponsored liquidity pool.**

### Operating Allocation (20% Revenue Retained by Dabba Inc)

To ensure long-term operational sustainability, **20% of total fiat revenue** generated each epoch is retained by Dabba Inc.

This allocation is not used for token buybacks and does not directly affect circulating DBT supply.

#### Structure

Let:

* R\_t = total fiat revenue in epoch t

The operating allocation is:

$$
R\_{INC,t} = 0.20 , R\_t
$$

These funds are retained in fiat and used exclusively to support network operations and growth.

### Purpose of the Operating Allocation

The 20% operating pool funds:

* Network monitoring and maintenance
* Engineering and product development
* Regulatory compliance
* Hardware logistics and support
* Administrative and infrastructure costs
* Market expansion and deployment operations

This ensures the network can scale without relying on token emissions to fund real-world expenses.

### Economic Rationale

The Dabba model is designed so that:

* 75% of revenue creates token demand (LCO + Bandwidth buybacks)
* 5% of revenue creates structured liquidity for Hotspot Owners
* 20% of revenue sustains operational infrastructure

This creates a self-funded operating structure tied directly to broadband adoption.

Unlike many token networks that rely on treasury token sales to fund operations, Dabba Inc is revenue-backed.

### Long-Term Sustainability

Because this allocation scales linearly with revenue:

* Operational funding increases as the network grows
* Token emissions are not required to subsidize expenses
* The protocol avoids structural dependency on token inflation

This design separates:

* Revenue-based business sustainability
* Token-based incentive coordination

The result is a system where real-world cash flow supports operational growth, while token mechanisms coordinate infrastructure incentives.