> 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/user-guides/claiming-vested-tokens.md). # Claiming Vested Tokens This guide is for **beneficiaries** — addresses that received a vesting allocation from a project's launch plan (team, advisors, ecosystem reserve, investor groups, etc.). For Launchpad sale claims, see [Participating in a Token Sale](/user-guides/participating-in-token-sale.md) instead. ## What You Need * A **Hathor wallet** connected to Dozer Tools, holding the exact address that received the allocation * A small amount of **HTR** for the claim transaction fee ## Where Vesting Lives Each project's vesting plan is published on its **public token page** at `/tokens/`, in a section called **Token Vesting**. You can reach it via: * **Explore → All Tokens** → click the project * A direct link the project shared with you Token Vesting section on a public token page ## Reading the Token Vesting Section Three tabs: | Tab | What it shows | | -------------------- | ------------------------------------------------------------------- | | **Allocations** | Per-beneficiary rows with claim status, next unlock, and % unlocked | | **Distribution** | Visualisation of how the total supply is split | | **Vesting Schedule** | Timeline of unlocks across the full plan | The **Allocations** tab is where you claim. Each row shows: * **Name** (e.g. Team, Advisors, Ecosystem) * **Beneficiary** (a truncated address) * **Next unlock** — amount and date of the next release * **Status badge** (see below) * **% Unlocked** so far * **Total** tokens in this allocation Find the row whose Beneficiary matches your connected wallet address. If you don't see your address, the project may have used a different one — confirm with the project team. ## Status Badges | Badge | What it means | | ------------------------- | ----------------------------------------------------------------- | | 🔒 **Cliff Period** | Initial lock; no tokens vested yet. Cliff end date is shown. | | ⏳ **Vesting in Progress** | Tokens unlocking linearly. Next unlock date and amount shown. | | 🟢 **Available to Claim** | One or more unlocks are ready. The Claim button is active. | | ✅ **Fully Claimed** | Everything is already withdrawn for this allocation. | | ➖ **Nothing to Claim** | Vesting is active but nothing has unlocked since your last claim. | ## How to Claim When a row shows **Available to Claim**: 1. Click the row's **Claim** button. 2. Approve the transaction in your wallet, enter PIN. 3. After confirmation, the tokens appear in your wallet and the row's progress bar updates. Each beneficiary row is claimed independently. If you have multiple allocations across different projects, you claim them per project, per row. ## When Not to Claim Claiming has a small HTR fee. If you only have a tiny amount available, it may be more efficient to **wait and batch** — claim once a month or once a quarter rather than every time a sliver unlocks. The **Allocations** tab is safe to use as a read-only monitor between claims: * Bookmark the token page * Status badges and next-unlock dates update automatically * Use the **Vesting Schedule** tab to plan around upcoming unlocks ## Adding the Token to Your Wallet After claiming, the token might not appear automatically in your wallet's token list. **Option A — Add from the dapp** (when supported): * Click **Add to Wallet** in the top right of the token's public page header. **Option B — Manual registration:** 1. Copy the **token contract address** from the public token page header. 2. In Hathor wallet: **QR icon → Manual → Register Token**. 3. Paste the address and confirm. ## Troubleshooting | Symptom | Fix | | -------------------------------------- | ------------------------------------------------------------------- | | Your address not in any allocation row | Confirm with the project team which address was registered | | Claim button missing on your row | Status is Cliff, or nothing has unlocked since your last claim | | Transaction fails | Top up HTR for the fee; reconnect the wallet if the session expired | | Tokens claimed but not in wallet | Wait for the next block, then register the token manually if needed | | Wrong amount shown | Contact the project team — beneficiary addresses cannot be changed | ## Security * **Verify the token contract** against the project's official channels before claiming. * **Never share your seed phrase or PIN.** Dozer staff will never ask. * For **large allocations**, claim into a hardware-backed wallet and consider moving the tokens to cold storage immediately after. * **Beware look-alike pages.** Always navigate from the project's official link or `testnet.tools.dozer.finance` directly. ## Related * [Wallet Setup](/user-guides/wallet-setup.md) — install and connect a Hathor wallet * [Participating in a Token Sale](/user-guides/participating-in-token-sale.md) — claim Launchpad purchases (different flow) * [Staking Tokens](/user-guides/staking-tokens.md) — what to do with your claimed tokens --- # 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: ``` GET https://docs.dozer.finance/user-guides/claiming-vested-tokens.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.