General FAQ for Builders
How are trading taxes tracked and processed on Base?
To track trading tax flow on Base, there are three methods:
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. 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
Token Swap to Tax Swapper Agent token trades that incur a tax will route to the Tax Swapper: 0x8e0253dA409Faf5918FE2A15979fd878F4495D0E
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
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
This function returns current stats on distribution balances.
How are agent trading taxes tracked and processed on Solana?
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
How is trading tax processed and distributed?
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.
How are vested tokens claimed?
Vested tokens are not auto-distributed.
Eligible wallets must log in to app.virtuals.io and manually claim any vested tokens.
Why do developer wallets receive staked tokens when a liquidity pool is created?
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.
Last updated