> For the complete documentation index, see [llms.txt](https://docs.strikebit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.strikebit.io/role-of-usdstrike-vs-usdhub.md).

# Role of $STRIKE vs $HUB

### 🧠 Two Tokens, Two Tracks — One Unified Ecosystem

StrikeBit uses a **dual-token model** to optimize scalability and clarity between protocol ownership and operational liquidity. Both tokens are essential — but they serve **distinct purposes** across two deployment flows:

* **$STRIKE** → Native agents launched directly on StrikeBit
* **$HUB** → Migrated agents and liquidity layers (e.g. from Virtuals)

This architecture ensures a **sustainable economic model** while aligning incentives across new builders, migrating projects, and active users.

***

### 🔑 Role of $STRIKE

$STRIKE is the **core protocol and governance token**. It governs StrikeBit’s native ecosystem and supports value accrual from marketplace activity, agent deployment, and staking infrastructure.

#### 🔹 Key Functions:

* Governance over protocol-level decisions
* Native agent deployment (built directly within StrikeBit’s MAP)
* Staking via $rSTRIKE earned from Radiant AI Miners
* Treasury control, proposal voting, emissions management
* Alignment with long-term protocol health and TGE structure

***

### 🔵 Role of $HUB

$HUB is the **agent-native utility token**, used as the gas layer for **migrated agents** (e.g. from Virtuals) and agent-level operations such as mining, upgrading, and fusions.

#### 🔹 Key Functions:

* Migrated agent deployment (via AgentHub)
* Virtual hashrate boosting for Radiant AI Miners
* Fusion, skin upgrades, modular boosts
* Marketplace activity for migrated NFTs and tools
* Cross-platform utility between Virtuals ↔ StrikeBit

***

### 🔁 Updated Functional Comparison

| Use Case                                 | $STRIKE                    | $HUB                            |
| ---------------------------------------- | -------------------------- | ------------------------------- |
| Governance & voting                      | ✅                          | ❌                               |
| **Native agent deployment**              | ✅ (MAP deployment)         | ❌                               |
| **Migrated agent deployment** (AgentHub) | ❌                          | ✅                               |
| Radiant Miner rewards                    | Earn via $rSTRIKE          | Boost with $HUB                 |
| Fusion & upgrades                        | ❌                          | ✅                               |
| NFT marketplace liquidity (ERC721)       | ❌                          | ✅                               |
| Cross-chain liquidity utility            | ❌                          | ✅ (Virtuals → StrikeBit bridge) |
| Airdrop/INO eligibility                  | Tiered by $rSTRIKE staking | Boosted via $HUB usage          |

***

### 🌉 Why This Structure Works

* $STRIKE powers the **backbone** of StrikeBit’s Modular Agent Protocol
* $HUB powers the **adapters and liquidity bridges** from other ecosystems
* Builders choose their track: native (deeper integration) or migrated (faster onboarding)
* This dual-layer model **reduces dilution**, improves UX, and drives protocol usage

***

### 🧠 Final Summary

| Token       | Layer           | Role                                    |
| ----------- | --------------- | --------------------------------------- |
| **$STRIKE** | Protocol Core   | Governance, native deployment, staking  |
| **$HUB**    | Utility Surface | Mining, migrated deployment, operations |


---

# 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.strikebit.io/role-of-usdstrike-vs-usdhub.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.