# FAQ

#### 1. What’s the difference between a vesting strategy and an allocation?

A **vesting strategy** defines the rules for unlocks:

* Start date / TGE date
* Cliff
* Duration
* Distribution type (linear, interval, monthly)
* Initial unlock % (optional)
* Whether it’s been locked (immutable) or not

An **allocation** is:

* A wallet address
* A token amount

All allocations in a strategy follow the **same schedule**.

***

#### 2. Can I edit a vesting strategy after I create it?

It depends on the state:

* **Draft (before start/cliff):**
  * ✅ You can edit everything:
    * Schedule (dates, duration, type, TGE %)
    * Wallet allocations and amounts
* **Active (after start/cliff):**
  * ❌ You cannot edit terms or allocations.
  * ✅ You can **Disable / Enable** (pause/resume) the strategy.
  * ✅ You can **Lock** it to make the schedule immutable.
* **Locked:**
  * ❌ You cannot change terms or allocations.
  * ✅ You can still **Disable / Enable** claims for operational reasons.

There is no “hard delete” once a strategy is onchain and started; you only pause (disable) or commit (lock).

***

#### 3. What does “locking” a strategy do?

Locking a strategy makes the **schedule and allocations immutable**:

* You **cannot**:
  * Change dates, type, initial unlock, or duration.
  * Add/remove/change wallet allocations.
* You **can still**:
  * Disable/enable claims if your admin UI exposes that option.

Locking is your way to say:

> “These vesting rules and allocations are final. No one can change them.”

Use it for major commitments (team, investors, etc.) once you’ve double-checked everything.

***

#### 4. What does disabling a strategy do?

Disabling a strategy effectively **pauses it from the user’s point of view**:

* Users **cannot claim** from that strategy while it is disabled.
* The underlying vesting math continues over time (tokens keep “unlocking” according to schedule).
* When you **re-enable** the strategy:
  * Users can claim again.
  * Any tokens that should have vested during the pause become claimable.

If you want to **stop** a strategy in practice:

> Disable it and never re-enable.\
> All remaining tokens stay in the contract; users can no longer claim.

This is the closest equivalent to “cancelling” a strategy.

***

#### 5. Can I permanently stop a vesting strategy?

There is no permanent “Cancel & delete” function, but you can:

* **Disable** the strategy and **never re-enable** it.

The effect is:

* No one can claim further tokens from that strategy.
* Any unclaimed tokens remain in the vesting contract.

The strategy still exists as a record (for auditing and history), but it’s effectively shut down.

***

#### 6. Can I change or remove a single wallet once vesting has started?

No.

Once a strategy has **started (Active)**:

* You cannot:
  * Add new wallets.
  * Remove existing wallets.
  * Change allocation amounts.

Your options are:

* Let the strategy continue as is.
* Lock it (immutable).
* Disable it (pause all claims; potentially permanently).

If you need to fix a specific wallet:

* Do it while the strategy is still **in Draft**, **before** the start date/cliff.
* Or, if already started and the error is critical:
  * Disable the existing strategy.
  * Create a **new** strategy with the corrected allocation, and communicate clearly to affected users.

***

#### 7. Do unclaimed tokens get lost if users don’t claim on time?

No, not by default.

As long as the strategy is:

* **Enabled**, and
* In **Active** or **Locked** state,

then:

* Vested-but-unclaimed tokens **accumulate over time**.
* If a user waits 3 months to claim, their claim includes all tokens vested during that period.

If you **disable** a strategy:

* Users cannot claim while it’s disabled.
* Once you re-enable it, any tokens that should have vested are available again.

If you disable and **never re-enable**:

* Remaining tokens stay in the contract.
* Users will never be able to claim them.

***

#### 8. Who pays gas for vesting and claims?

* **Admin/Manager** pays gas to:
  * Deploy vesting strategies.
  * Upload/update allocations (if these actions touch the chain).
* **Beneficiaries** (users) pay gas to:
  * Claim tokens from the Vesting & Claim Portal.

You may want to tell users they’ll need a small amount of the network’s native token (e.g. ETH, BNB) to perform a claim transaction.

***

#### 9. Can a wallet be in multiple strategies?

Yes.

A single wallet can appear in multiple strategies, for example:

* Seed allocation in “Seed Round” strategy.
* Team allocation in “Team 4-Year” strategy.

In the Vesting & Claim Portal, the user will see all allocations tied to their wallet, grouped by strategy or category.

***

#### 10. How many wallets can I add to one strategy?

Current defaults (as you mentioned):

* Up to **150 wallets per CSV upload**.
* Up to **1,200 wallets per strategy** total.

For larger distributions:

* Break them into multiple strategies (e.g. “Community Round 1”, “Community Round 2”), or
* Batch uploads within these limits for each strategy (as supported by your implementation).

***

#### 11. Can I test my vesting setup before going live?

Yes — and you should.

Set up a **testnet environment** and:

* Create a strategy with the same settings as your planned mainnet strategy.
* Add a few test wallets and allocations.
* Use the Vesting & Claim Portal on testnet to:
  * Connect a test wallet.
  * Check that vesting behaves as expected.
  * Claim tokens.

Only after that should you replicate the configuration on **mainnet**.

***

#### 12. What do users see if they’re not part of any strategy?

If a wallet has **no allocations**:

* The portal will show a message like:

  > “No vesting allocations found for this wallet.”
* They will see no claimable tokens or schedules.

This is normal for addresses not included in your vesting uploads.

***

#### 13. Can I hide internal strategy names from users?

Yes, to an extent.

* Strategy **names** are primarily for you in the admin interface.
* What users see is typically:
  * Human-friendly labels and categories (Team, Investors, Community, etc.).
  * Any custom text you configure in the portal’s content/branding settings.

If you don’t want internal names exposed, use neutral or descriptive names and rely on **categories + portal copy** to shape what users see.

***

#### 14. What’s the safest way to run major strategies (team, investors)?

Recommended pattern:

1. **Design and test** the strategy on testnet.
2. Deploy it on mainnet as a **Draft** (future start date) and add allocations.
3. Double-check:
   * Dates, cliffs, durations.
   * Total tokens vs tokenomics.
   * Sample wallets.
4. Let it become **Active**, monitor early behavior.
5. When you’re completely confident and have communicated it:
   * **Lock** the strategy (immutable).

Optionally:

* Keep the ability to **Disable** as an emergency pause, but only use it with clear communication if absolutely necessary.


---

# 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://tms-finance.gitbook.io/tms.finance/vesting-and-lockups/faq.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.