# Flywheel Model

Honeypot Finance's vision is closely aligned with Berachain, and our unique flywheel model actively supports the growth and dynamism of the Bera community.

### Architecture

Honeypot Finance is building a community-run DeFi Hub on Berachain that integrates a unique AMM model to unite a community-led launchpad and DEX, addressing Defi's low liquidity utilization issues.

<figure><img src="/files/3CXUJ1vwZdArWXkwf8qA" alt=""><figcaption><p>Honeypot Finance Flywheel Model</p></figcaption></figure>

Dreampad, Honeypot DEX, and HiveNode form a comprehensive pathway that supports the introduction, retention, and incentivization of liquidity within Honeypot Finance, enhancing the platform’s positive flywheel effect.

* **Honeypot DEX** caters to all memecoin & long-tail asset enthusiasts, featuring a unique meme-centric approach alongside enhanced incentives and a seamless user experience.
* **Dreampad** supports our innovative Fair Token Offering (FTO) model and both Fjord Foundry's LBP and Fixed Price Sales to ensure successful and sustainable token launches for projects.
* [Pot2Pump](/products/pot2pump.md) is a meme launchpad that combines liquidity-focused meme model with fair launch mechanism at pre-dex phase like [Daos.fun](#introduction).  Early participants will become LPer on [Meteora ](https://meteora.ag/)like Defi army that ensures optimal concentrated liquidity management via ALM (automated liquidity Manager), delivering robust support for liquidity providers.

Plug into the Berachain PoL and start earning. Launch your project through *Dreampad*, with immediate token liquidity and grants. Our innovative *Fair Token Offering (FTO)* model stands apart, providing Liquidity Pool token ownership and plugs users and projects directly into PoL.

### Flywheels

Our flywheel model includes our community-led launchpad Dreampad, as well as a community-driven public validation node. On top of it, we're introducing $HPOT as a governance token, key to Honeypot's leadership within the Berachain ecosystem. Consider this: $BGT and $Honey join forces, creating a dynamic system of three dual-incentive tokens.

**The $HPOT flywheel plays a significant role:**

1. It helps launch projects, stimulate business and incentivize our community.
2. This is an attractive incentive for $BGT, increasing the number of votes and revenues for our BeeHive community nodes.
3. It increases the liquidity depth of $HPOT, creating a robust and appealing financial ecosystem.
4. Node earnings and fees from the protocol will be used as buy back for $HPOT. It aims at perpetually enhancing $HPOT’s value. This strategic approach functions as a powerful catalyst, continually driving $HPOT's market price to new highs.

**The $BGT cycle forms also a substantial flywheel effect:**

1. $BGT holders who delegate to our node receive attractive $HPOT bribes.
2. The bribe mechanism boosts voting rights, increasing the incentives for $HPOT and $Honey token pools to attract more $BGT rewards.
3. $HPOT holders participate in PoL mining, collecting $BGT profits.

**This creates a lucrative income flywheel driven by $BGT and $HPOT:**

1. The revenue from the protocol and community nodes grows.
2. Increased revenues prompt $HPOT buybacks, which significantly elevate its market value.
3. As tokens increase in value, they attract larger bribes and incentives, further stimulating the flywheel of $BGT and intensifying the rise of $HPOT.
4. A boosted $HPOT leads to an increase in the number of nodes and protocol revenues, sustaining a cycle of growth and prosperity.

<figure><img src="/files/QifLOx55VVIdo6mCYGVU" alt=""><figcaption><p>A huge pump turns two flywheels</p></figcaption></figure>


---

# 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://docs.honeypotfinance.xyz/products/flywheels.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.