> For the complete documentation index, see [llms.txt](https://docs.runnersrh.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.runnersrh.app/resources/faq.md).

# FAQ

<details>

<summary>Do I need to hold ETH to launch by tweet?</summary>

**No.** The platform covers gas for tweet launches.

</details>

<details>

<summary>Why didn't the bot reply to my launch tweet?</summary>

Most often the tweet is **hidden from X search** because the account is new or low-activity. Tweet from an **established account** and follow the **exact command format**.

See [Launch by Tweet (Advanced)](/launching-a-coin/launch-by-tweet.md#troubleshooting) for the full troubleshooting guide.

</details>

<details>

<summary>When can I claim my vested supply?</summary>

After the **90-day cliff**, your allocation releases linearly over **24 months**. You can claim the unlocked portion **anytime**.

</details>

<details>

<summary>Where do my trading fees go?</summary>

To the **creator address stored on-chain at deploy** — **80% of every 1% trade fee**. Claim them from the [dashboard](https://runnersrh.app/dashboard).

</details>

<details>

<summary>Can someone else claim my fees?</summary>

**No.** Even though claiming is permissionless, funds **always** go to the creator address fixed in the contract at deploy time.

</details>

<details>

<summary>What's the difference between claim and withdraw?</summary>

* **Claim** moves fees/vested tokens **from the contract** to your creator address.
* **Withdraw** moves funds **out of a provisioned (X/Telegram) wallet** to any address you choose.
* **Self-custody connected wallets** simply hold their funds directly — no withdraw step needed.

See [Claiming & Fees](/for-creators/claiming-and-fees.md) for the full breakdown.

</details>

<details>

<summary>Is RUNNERS on Base too?</summary>

**Yes.** Base launches use **Clanker v4**. Robinhood Chain uses the **native RUNNERS template**.

See [Robinhood Chain & Base](/networks/robinhood-chain-and-base.md) for a side-by-side comparison.

</details>

<details>

<summary>Can I launch a coin for someone else?</summary>

**Yes.** Point a launch at:

* **An X handle** — a wallet is provisioned for that account.
* **A wallet address** — rewards go straight to that address.

See [Creator Rewards → Launching for someone else](/for-creators/creator-rewards.md#launching-for-someone-else).

</details>

<details>

<summary>How do I verify a coin is legit?</summary>

* Check the **contract address** on [robinhoodchain.blockscout.com](https://robinhoodchain.blockscout.com).
* Verify the **top holders** — you should see the **RunnersVesting** contract and the **liquidity pool** as the two largest holders.
* Cross-check the address against the [official contract list](/resources/contract-addresses.md).

</details>

<details>

<summary>Someone DMed me claiming to be RUNNERS support — is it real?</summary>

**No.** **Admins never DM first.** Anyone reaching out unsolicited is a scammer. Block, report, and move on.

</details>

***

{% hint style="info" %}
**Still stuck?** Ask the [**RUNNERS Assistant**](/resources/the-runners-assistant.md) on X, Telegram, or the dashboard — it can answer live.
{% endhint %}


---

# 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.runnersrh.app/resources/faq.md?ask=<question>&goal=<endgoal>
```

`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.