# Singularity Mining
Overview
Singularity is minted at a 1:1 ratio with HORIZON. Each mint uses equal value in HORIZON and ETH. Users pay in ETH only, and the protocol buys the required HORIZON on their behalf.
Each miner has a fixed 100 day duration and accrues at a rate of 1% per day until claimed. Early claims are allowed, but any unaccrued portion is forfeited and sent to the Treasury. Late claims carry no penalty.
Example: Minting 10 Singularity requires 10 HORIZON plus an equal value of ETH. A claim made on Day 10 receives 10% of the miner’s total amount, while the remaining 90% is forfeited.
***
Token Distribution:
**ETH and HORIZON value are allocated as follows:**
* **28%** → Staking Payouts → ETH paid to stakers
* **28%** → Buy and Burn → buys and burns Singularity over time
* **28%** → Buy and Stake → buys HORIZON and Singularity then stakes them both forever
* **8%** → The Reserve → supports future HORIZON auctions
* **8%** → Buy and Grow → adds liquidity to the Singularity/HORIZON vault
LP Formation
* The LP is created when the first $5,000 enters virtual mining, matched with an equal dollar value of newly minted Singularity.
* The main LP pair will be Singularity/HORIZON
***
Buy and Burn Mechanism
**28%** of the HORIZON from mining is allocated to the **Buy and Burn**. This HORIZON is used to purchase Singularity from the Singularity/HORIZON LP. The Singularity acquired is then fully burned.
Buy and Burn
Daily Allocation:
* 15% of the Buy and Burn balance is utilized each day.
* The daily balance is divided into 288 parts, released every 5 minutes.
* Unused portions will accumulate.
This approach introduces unpredictability and allows for fluctuating buy and burn amounts, with some days experiencing slightly larger burns. This all done in a fully decentralised and predicable way.
Buy and Grow
**8%** of the HORIZON from virtual mining goes to **Buy and Grow**.
Once the above threshold is reached:
* buy **Singularity**
* deposit both into the **Singularity/HORIZON Liquidity Vault**
Each allocation adds to the same position, and trading fees are compounded back into it.
**NOVAE emissions** are routed as follows:
**NOVAE → TitanX → X28 → HORIZON**
The HORIZON acquired is added to the **Singularity buy and burn balance**.
***
Buy and Stake
**28% of the ETH from Singularity Mining is used to buy HORIZON and Singularity from the market and stake it for 3500 days.**
The HORIZON purchased through this route is staked by the contract for the maximum duration.\
When these stakes mature, the contract ends and restakes the returned HORIZON for 3500 days again. To avoid creating large numbers of very small stakes, the contract does **not** stake each purchase immediately. Instead, the accumulated HORIZON balance becomes available to be staked **the day before ETH payouts**.
This creates a permanent staking base inside the protocol.
### ETH rewards from protocol-owned HORIZON stakes
ETH rewards generated by these protocol-owned HORIZON and Singularity stakes are distributed as follows:
* **44.5%** → used to buy and stake more **HORIZON and Singularity**
* **44.5%** → used to buy and burn **Singularity**
* **3%** → sent to the caller
* **8%** → sent to Treasury
***
Singularity Staking (Earn ETH)
Stake Singularity for **28 to 3500 days** to earn recurring **ETH payouts**.
When you start a stake, you receive **shares**. Your shares determine your share of the ETH payout pool while the stake is active.
If you own **1% of total global shares**, you receive **1% of each ETH payout cycle** during your staking period.
When the stake ends, your **Singularity is returned**, subject to the stake rules and any penalties.
Once a stake reaches maturity, it no longer counts toward global shares and no longer earns ETH payouts.
ETH payout cycles
ETH payouts run across four rolling cycles:
* **30%** → every 8 days
* **30%** → every 28 days
* **25%** → every 90 days
* **15%** → every 365 days
This keeps regular short-term payouts while still reserving value for longer-term participants.
Share bonuses
Longer and larger stakes receive more shares.
* **Longer Pays More**: longer stakes earn more shares, up to a **+350% bonus at 2888 days**
The more shares you have compared with everyone else, the larger your share of ETH payouts.
Inactive shares
If you do not claim ETH payouts for **28 days**:
* your shares become inactive
* inactive shares stop earning ETH
* inactive shares are removed from global shares
If you claim later, your shares are reactivated and begin earning again.
This stops inactive users from diluting active users and keeps ETH flowing to participants who remain engaged.
Stake end rules
You choose your end date when you create the stake.
* You should end the stake on that date
* You get a **7 day grace period** with no penalty
* Stakes cannot be ended before **50% maturity**
If a stake is ended after **50% maturity** but before full maturity:
* **50% of the staked Singularity is returned**
* **50% of the staked Singularity is burned**
If a stake is ended at full maturity and within the 7-day grace period:
* **100% of the staked Singularity is returned**
If the stake is not ended within 7 days after maturity:
* you lose **1% of staked Singularity per day**
* penalties continue until up to **99% is lost after 100 days**
***
Summary
Singularity Staking follows the same core rules as Horizon Staking, but uses **Singularity** instead of **HORIZON**.
You stake Singularity, receive shares, earn ETH based on your share of the pool, and get your Singularity back at the end if you follow the stake rules. Longer and larger stakes earn more shares, while inactivity and late exits reduce returns.
---
# 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://trader-li.gitbook.io/horizon-protocol/build-on-horizon/singularity-mining.md?ask=
```
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.