> For the complete documentation index, see [llms.txt](https://hashly.gitbook.io/hashly-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hashly.gitbook.io/hashly-docs/markets/forever-mint.md). # Forever Mint [Forever Mint](https://hash-ly.com/forever-mint) tracks every live Forever Mint pool on Hedera in one table: how many NFTs each pool holds, what one costs, who is minting and what the teams behind the pools hold and spend. *** ## ❓ What Is a Forever Mint? A Forever Mint is a **custody pool**. Holders deposit NFTs from an existing collection into a pool account, and a buyer pays the mint price to take one out. The NFTs come from depositors, so nothing new is minted, the collection's supply doesn't change and the mint has no end date. In the mint transactions Hashly checked on the mirror node, almost all of the price went to whoever deposited the NFT, the rest to the collection's royalty recipients, and nothing to the pool account. That's why the page reports what sits in each pool and who takes it out. *** ## 📊 The Overview The header sums up every pool: | Figure | What it means | | -------------- | --------------------------------------------------------------------------- | | **Pools open** | Forever Mint pools live right now | | **Mints** | Every purchase Hashly has recorded, with the date the record starts | | **Volume** | HBAR paid across those mints, and how many were minted in the last 24 hours | | **Collectors** | Distinct wallets that minted from any pool (a wallet counts once) | Beside it, a chart shows mints per day across every pool. *** ## 📋 The Pool Table | Column | What it shows | | ------------ | ------------------------------------------------------------------------------------------------ | | **Pool** | Collection name, linked to its own page, with a seal when the project has published team wallets | | **In pool** | NFTs available to mint | | **Price** | The mint price in HBAR | | **To clear** | What it would cost to mint every NFT in the pool (price × NFTs in pool) | | **24h** | Mints in the last 24 hours | | **30 days** | Mints per day over the last 30 days | The table opens sorted by **24h**. You can also sort by In pool, Price or To clear, always highest first. Click a row to open the pool in place. *** ## 🔍 Inside a Pool An open pool shows the collection art with **in the pool**, **each** and **to clear**, a **Mint on SentX** button while it isn't sold out, and a link to the pool account on HashScan. One **Window** control (24h, 7d, 30d or all, starting on 7d) drives everything below it. ### 🏊 The Pool * **Mints**, **Volume** (at the price actually paid) and **Collectors** in the window * **Minted per hour** (24h) or **per day** (longer windows) * **Who is taking from it** — up to six wallets that minted most in the window, with their share of the mints * **Latest out of this pool** — the 12 most recent purchases ### 🛡️ The Team Shown only when the project has published wallets as its own. Hashly never guesses which wallets belong to a team. | Figure | What it means | | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------- | | **Held** | HBAR in the team's wallets now, and the change over the window | | **Of these mints** | Share of the recorded mints taken by team wallets | | **Of secondary** | What team wallets spent buying the collection on the open market, against all of the collection's market volume in the same window | A chart of the HBAR held across team wallets over time sits beside the mint chart, and **The N wallets** lists each wallet with its balance, its share of what the team holds and its share of the mints. Team wallets are marked wherever they appear. *** ## 🔗 Pool Pages Each pool has its own address, `hash-ly.com/forever-mint/`. It's the same scanner with that pool already open, so it can be shared or bookmarked. *** ## 📡 Data and Freshness * 🟢 **Pools, prices and purchases** come from SentX. While the page is open and in view, it checks for new mints every **15 seconds**, and a background job records them every **15 minutes** as well. * 🗓️ **Totals have a start date.** SentX serves only about 16 days of launchpad history, so anything older exists on Hashly only because it was recorded at the time. Every total says the date it counts from. * ⛓️ **Wallet balances and transfers** come from the Hedera mirror node, which also provides the history behind the team balance chart. *** ## 📅 Forever Mints on the Calendar Forever mints also appear on the [Calendar](/hashly-docs/discover/events-calendar.md) as events marked **Always Live**. Find them with **More filters** → **Type** → **Forever Mints**, and star them like any other event. See [Voting System](/hashly-docs/discover/voting-system.md). > ⚠️ **Data, not advice.** Pool data comes from SentX and the Hedera mirror node and can be incomplete, out of date or wrong. Nothing on this page is financial advice or a recommendation to mint, buy or sell, and Hashly doesn't vouch for the collections listed. See the [Terms of Use](https://hash-ly.com/terms). *** ## 💡 Tips * 🛡️ **Check the team panel.** A team feeding its own pool and a pool being drained by others look the same in a plain mint count. * 🗓️ **Read the start date** under each total before comparing pools. * 🔗 **Share a pool** with its own page link, so it opens with that pool already expanded. --- # 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://hashly.gitbook.io/hashly-docs/markets/forever-mint.md?ask=&goal= ``` `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.