> For the complete documentation index, see [llms.txt](https://docs.silverbackdefi.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silverbackdefi.app/usdback-token/tokenomics.md).

# Tokenomics

$BACK token supply, distribution, and economic design.

***

## Token Details

| Property        | Value              |
| --------------- | ------------------ |
| Token Name      | Silverback         |
| Ticker          | $BACK              |
| Launch Platform | Virtuals Protocol  |
| Model           | Unicorn Tokenomics |
| Network         | Base               |

***

## Launch via Virtuals Protocol

$BACK launches through Virtuals Protocol's **Unicorn** tokenomics model, which provides:

* Fair launch mechanics
* Built-in liquidity
* Transparent distribution
* AI agent integration

***

## Supply Mechanics

### No Inflationary Rewards

Unlike many DeFi tokens, $BACK does not mint new tokens for rewards. Instead:

1. Protocol generates revenue (fees, trading profits)
2. Revenue is used to **buy back** $BACK from the market
3. Bought tokens fill the **staking reward pool**
4. Stakers earn from this pool

This creates:

* **Sustainable yield** — Rewards backed by real revenue
* **Buy pressure** — Continuous market purchases
* **No dilution** — Supply doesn't increase

***

## Revenue Sources

The protocol generates revenue from multiple sources:

| Source                | Description                                |
| --------------------- | ------------------------------------------ |
| DEX Swap Fees         | Portion of 0.3% fees from all swaps        |
| Anchor Pool Fees      | Revenue from Keeta anchor operations       |
| Treasury Trading      | Profits from AI agent's systematic trading |
| Cross-Chain Arbitrage | Returns from multi-network opportunities   |

All revenue streams contribute to the buyback mechanism.

***

## Economic Flywheel

```
Revenue Generated
       ↓
   Buybacks
       ↓
 Staking Rewards
       ↓
  More Staking
       ↓
 Reduced Selling
       ↓
 Price Support
       ↓
More Users/Volume
       ↓
More Revenue...
```

The model creates a self-reinforcing cycle where protocol success benefits token holders.

***

## Why This Model?

### Problem with Inflationary Rewards

Many DeFi protocols:

* Mint tokens for rewards → Dilutes holders
* Creates constant sell pressure
* Unsustainable long-term
* "Farm and dump" culture

### Silverback's Approach

* Rewards come from **real revenue**
* Buybacks create **buy pressure**
* No new supply = **no dilution**
* Sustainable for long-term holders

***

## Token Utility Summary

| Utility       | Description                            |
| ------------- | -------------------------------------- |
| Staking       | Earn share of protocol revenue         |
| Governance    | Vote on protocol decisions             |
| Fee Discounts | Reduced fees for holders (future)      |
| Access        | Priority features for stakers (future) |

***

## Contract Information

See [Contract Addresses](/resources/contract-addresses.md) for verified contract details.

> **Always verify** contract addresses before interacting. Only use official links from this documentation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://docs.silverbackdefi.app/usdback-token/tokenomics.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.