# Virtuals Protocol FAQ

The most frequently asked questions about Virtuals protocol.

{% hint style="info" %}
The FAQ reflects the current system as of May 6, 2026.\
\
Details may evolve over time as the protocol iterates.
{% endhint %}

### Builder Specific FAQ

<details>

<summary>How to launch an agent?</summary>

You can get a full guide on how to launch an agent starting [here](/info-hub/builders-hub/agent-launch-guide.md).

</details>

<details>

<summary>How to get support on my agent launch?</summary>

You can request agent launch support starting [here](/info-hub/builders-hub/agent-launch-support.md).

</details>

<details>

<summary>How are trading taxes tracked and processed on Base?</summary>

To track trading tax flow on Base, there are three methods:<br>

**Option 1: Track from Virtuals Tax Chechker Dashboard**\
\
You can track your agent's trading fee accumulation and distribution status through the official [Virtuals Tax Checker Dashboard](https://dune.com/virtual_protocol/tax-checker). \
\
Scroll down to the section labeled “Virtual not distributed breakdown by project” and sort the table to view pending distributions.

Notes:

* Each agent must first meet a minimum trading volume threshold before fee distribution is triggered. *(Details Above)*

**Option 2: Trace Through Contracts**

1. Token Swap to Tax Swapper\
   \
   Agent token trades that incur a tax will route to the Tax Swapper:\
   \
   0x8e0253dA409Faf5918FE2A15979fd878F4495D0E<br>
2. Swapper Converts to $VIRTUAL → Sent to Tax Manager\
   \
   The Tax Swapper converts taxed tokens to $VIRTUAL, then sends the output to the Tax Manager:\
   \
   0x7e26173192d72fd6d75a759f888d61c2cdbb64b1<br>
3. Tax Manager Distributes Fees in $VIRTUAL\
   \
   The Tax Manager  distributes fees directly in $VIRTUAL to the creator and the platform.

**Option 3: Read from Tax Manager Contract**

Use Function 5 on the Tax Manager proxy contract:

[BaseScan - Tax Manager Contract](https://basescan.org/address/0x7e26173192d72fd6d75a759f888d61c2cdbb64b1#readProxyContract)

This function returns current stats on distribution balances.

</details>

<details>

<summary>How are agent trading taxes tracked and processed on Solana?</summary>

On Solana, tax proceeds are sent directly from the agent wallet to the creator’s distribution wallet.

* If the destination wallet is unknown, creators should contact the Virtuals team for verification.
* Alternatively, distributions can be monitored via the LP fee distribution wallet:

  9WBoFXeAbskmi6aMK5jvyNgXVKeZrcVeFJtDBLikzdnm

</details>

<details>

<summary>How is trading tax processed and distributed?</summary>

Trading tax is processed and distributed based on each agent’s trading volume. Fees are first swapped into $VIRTUAL, and only converted to cbBTC once the system reaches a trading volume threshold equivalent to 1 million agent tokens in total.

</details>

<details>

<summary>How are vested tokens claimed?</summary>

Vested tokens are not auto-distributed.

Recipient wallets must log in to [app.virtuals.io](https://app.virtuals.io) and manually claim any vested tokens.

</details>

<details>

<summary>Why do developer wallets receive staked tokens when a liquidity pool is created?</summary>

When a liquidity pool is launched through Virtuals Protocol, the pool creator is the owner of the LP. To ensure permanence and prevent liquidity extraction, all LP tokens are immediately staked and locked for the long term.

The protocol then transfers the staked LP position back to the creator’s wallet. This means:

* Ownership → the creator retains ownership of the LP
* Locked liquidity → LP tokens are staked for years and cannot be withdrawn
* Ecosystem alignment → liquidity remains permanently secured, while the project retains ownership rights

This mechanism is standardized across Virtuals Protocol. Every pool is designed to be creator-owned but protocol-secured to protect both builders and participants.

</details>


---

# 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://whitepaper.virtuals.io/info-hub/virtuals-protocol-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.