> For the complete documentation index, see [llms.txt](https://docs.dozer.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dozer.finance/project-launch-tools/credits.md).
# Project Credits
Each project has a **Credits** balance — a per-project prepaid pool of HTR and/or DZR used to pay for on-chain operations: creating staking contracts, DAOs, crowdsales, and liquidity pools.
Open the Credits screen at `/admin/credits` (sidebar → **Credits**).
## Why credits exist
Most Project Launch Tools actions are submitted by the project contract, not directly by your wallet. The project needs its own balance to cover those fees. The Credits screen is where you fund and reclaim that balance.
## Current Balance
Two rows: **HTR Balance** and **DZR Balance**. Minimum HTR deposit is **100.00 HTR** — smaller deposits are not accepted.
## Deposit Credits
Add HTR or DZR to the project balance.
1. Pick **Token Type** (HTR or DZR).
2. Enter an **Amount**.
3. Click **Deposit Credits**, confirm in the wallet, sign with PIN.
The deposit goes from your connected wallet to the project's credit pool.
## Withdraw Credits
Reclaim unused HTR or DZR. Each transaction can withdraw **only one token type** — withdraw HTR and DZR separately if needed.
1. Pick **Token Type** (HTR or DZR). The available balance is shown next to each option, and the **Max** link fills the amount field with the full balance.
2. Enter the amount to withdraw.
3. Click **Withdraw Credits**, confirm in the wallet.
The withdrawal goes back to your connected wallet.
## HTR vs DZR — Which to Use?
> DZR credits are preferred over HTR when both are available, as they typically have lower fees.
Practical guidance:
* **HTR**: easier to obtain, especially on testnet (use the **Faucet 100k HTR** button in the sidebar).
* **DZR**: lower per-action cost; keeps your project lean as it scales.
Most projects start with HTR for setup and refill in DZR once they hold some.
## What credits get spent on
Any action that the project contract submits on-chain, including:
* Creating a Liquidity Pool
* Creating a Crowdsale / Launchpad
* Setting up a DAO
* Adding rewards to a Staking pool
* Some token-management actions (when they require contract calls)
Wallet-paid actions — like the initial project creation, vesting deploy, or melt-authority transfer — are paid directly from the user's wallet, not from credits.
## Best Practices
* **Top up before a busy launch week** — pre-fund credits so a wallet hiccup doesn't block a planned action.
* **Use DZR once available** — lower fees mean more operations per credit.
* **Withdraw before sunsetting a project** — credits don't expire, but they're locked to the project until withdrawn.
* **Keep a buffer** — leave at least one full transaction's worth in credits so urgent actions (pausing a sale, for example) don't fail.
## Troubleshooting
| Symptom | Fix |
| ------------------------------------ | ------------------------------------------------------------- |
| Deposit Credits button is disabled | You're below the 100.00 HTR minimum, or amount field is empty |
| "Insufficient balance" on deposit | Top up your wallet HTR or DZR first |
| Action fails with "credits required" | The project pool ran dry — deposit more credits |
| Withdraw button disabled | Selected token's available balance is 0 |
## Related
* [Token Management](/project-launch-tools/token-management.md) — the other admin-only screen for an existing project
* [Project Creation](/project-launch-tools/project-creation.md) — initial setup, paid from wallet (not credits)
* [Vesting Configuration](/project-launch-tools/vesting-configuration.md), [Crowdsale](/project-launch-tools/crowdsale.md), [Staking](/project-launch-tools/staking.md) — features whose deployments consume credits
---
# 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://docs.dozer.finance/project-launch-tools/credits.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.