# $HDS Star Pool Collision

$HDS's Star Pool Collision is a brand new way of token generation, which follows the established issuance curve, based on the smart contract algorithm interest rate casting protocol, which allows the star pool network address to be cast by HDS in the 24h ladder scale.

There are no restrictions on the star pool collision process. You may worry that projects have good ideas and will become more and more cheated, so whitelists are hard to balance the interests between users and the platform. We decided to allow users to participate in starpool collisions without restriction, so everyone could buy $HDS, a true belief in the real metacverse.

Assuming that the number of $HDS issued by the Starpool collision is X, the number of $HDS added for the first liquidity is 0.35X, 0.01X for marketing budget and vacancies, and the total supply of $HDS is X \* 1.36.

Here are some rules:

1 \ There is no limit on the number of star-pool collisions, but for a duration of 11 days, with an initial price of 1 USDT or equivalent FILCOIN. Participate in the star pool collision through the Honingdas official website

2 \ quota fixed value for single address 100USDT (maximum purchase)

3 \ To participate in the star pool collision, you need to fill in the star pool address to confirm the recommended relationship.

**You can also get rewards from the collision process.**

If you invite someone directly, you will receive a 5% token reward of the number of invitations, and 3% of the number of second-order user collisions if your invitation invites someone else.

The eg: You invite me, you invite me when you succeed. If I consume the 100 USDT in the collision, then you can automatically get the 5 USDT from the contract. If he hits 100 USDT, you can get 3 USDT as the so-called "Star Pool" reward.

Invite 10 users to participate in the collision, and you can get 1 equity NFT as a reward. For every 10 valid recommendations, you can get 1 NFT. There are no limitations to this process, for example, you might get 100 valid recommendations if you get 10 NFT's.

Seventy percent of the funds raised by the collision will be added to the LP and locked up for one year (35% is the first addition and 35% is repurchased in the secondary market)

After you start $HDS on PancakeSwap, you can receive the unlocked $HDS on your website.

**Colliding ratio**

The collision protocol is a coin protocol in Honingdas Network based on the smart contract algorithm rate, which allows star pool network addresses to be HDS in a 24h step scale, as follows:

&#x20;

| **date** | **Colliding ratio** |
| -------- | ------------------- |
| D1       | 100USDT=100HDS      |
| D2       | 105USDT=100HDS      |
| D3       | 110USDT=100HDS      |
| D4       | 115USDT=100HDS      |
| D5       | 120USDT=100HDS      |
| D6       | 125USDT=100HDS      |
| D7       | 130USDT=100HDS      |
| D8       | 135USDT=100HDS      |
| D9       | 140USDT=100HDS      |
| D10      | 145USDT=100HDS      |
| D11      | 150USDT=100HDS      |

&#x20;

&#x20;

**How to get the HDS-DAO NFT**

HDS-DAO NFT is a core asset and equity certificate of the Honingdas ecosystem. The HDS-DAO NFT is only cast for free during the collision phase, so his number is fixed.

How to get the HDS-DAO NFT?

Invite 10 users to participate in the collision with 1 NFT. For every 10 valid recommendations, you can get 1 NFT. There are no limitations to this process, for example, you might get 100 valid recommendations if you get 10 NFT's.

HDS-DAO NFT Equity:

The Honingdas DAO NFT is a core signal of the HDS ecosystem. Bear the core commission dividend in the system, the details can refer to the "transaction tax".


---

# 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://honingdas.gitbook.io/honingdas.net/usdhds-star-pool-collision.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.
