> For the complete documentation index, see [llms.txt](https://tickideas.gitbook.io/hubble/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tickideas.gitbook.io/hubble/readme.md).

# Introduction to Hubble Protocol

<figure><img src="/files/lF49Nn26GQGdZZAOjGmF" alt=""><figcaption></figcaption></figure>

Hubble Protocol is designed with sustainability at its core, introducing innovative mechanics that differentiate it from traditional tomb forks. The protocol was developed to maintain engaging features while ensuring long-term viability through its unique economic structure. Unlike conventional approaches, Hubble introduces liquid shares before Genesis and emits additional shares rather than the pegged token during Genesis.

Built on Sonic, the fastest EVM-compatible layer-1 blockchain with 10,000 transactions per second and instant finality, Hubble Protocol combines high performance with user-driven governance.

The protocol launched as a stealth launch on [Shadow Exchange](https://www.shadow.so/), a Sonic-native decentralized exchange, providing users with immediate access to its ecosystem. This approach allowed early adopters to participate in the protocol from day one while establishing initial liquidity and market dynamics. The protocol features a well-structured tokenomics model and governance system that empowers stakeholders to guide its development and operations.

Hubble's architecture focuses on balanced emission schedules, strategic locking mechanisms, and dynamic epoch systems that respond to market conditions. This thoughtful design aims to create a self-regulating ecosystem that can withstand market volatility while providing value to participants. Through its multi-token approach, Hubble creates a comprehensive economic system with built-in stabilization mechanisms.

## Core Differentiators

Hubble Protocol distinguishes itself through several key innovations:

* First, shares are made liquid before Genesis, allowing for early price discovery and market participation. This contrasts with traditional approaches where share value is only established after Genesis.&#x20;
* Second, Genesis emissions are directed toward shares ($HUBBLE) rather than the pegged token ($EX), creating a more balanced distribution mechanism.&#x20;
* Third, the protocol implements variable lock durations for $xHUBBLE, starting at 180 days with governance options to adjust this timeframe based on community decisions.

The protocol also features sophisticated epoch mechanics that adapt to market conditions, with neutral, light, and dark epochs creating different emission patterns based on the price of $EX relative to $stS.&#x20;

Special epoch mechanics such as White Hole and Black Hole epochs further enhance stability when the protocol faces specific challenges.&#x20;

These dynamic responses provide Hubble with robust tools to maintain equilibrium under varying market conditions.


---

# 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, and the optional `goal` query parameter:

```
GET https://tickideas.gitbook.io/hubble/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
