VVVX Coins paired with VVV on Base

Transparency

Every address, every number that decides where money goes, and the limits that no amount of code removes. Everything below the first table is read from Base in your browser when this page loads — if it disagrees with anything we have written elsewhere, the chain is right.

Contracts

WhatAddressCan it be changed?

What the chain says right now

SettingValueWhere it comes from

Second-pair whitelist, and how each asset is priced

AssetAddressPrice sourceFeed, and what it reads
Reading the registry…

Who controls what

The fee lock has no owner at all. No pause, no upgrade path, no function that moves a position, no decreaseLiquidity. That is not a policy, it is the absence of code.

The split cannot be changed. It is three constants in the lock contract with no setter. Changing it would mean deploying a new lock and a new factory; coins already launched keep the terms they were launched under.

The platform address, the keeper, the router and the VVV feed are immutable — set once at deployment and readable in the table above. There is no function that rewrites any of them. Replacing one means deploying a new lock, which existing coins would not be moved to.

The pair-asset whitelist has an owner who can list and delist assets. Delisting stops new launches against an asset; it does not touch a coin that already exists, its pool, or its fees.

What the keeper can and cannot do

A coin’s second pool earns its fees in the pair asset, not in VVV. Somebody has to swap them, and that somebody is the keeper — the address in the table above, the only one convert() accepts.

It cannot touch the liquidity or the principal. convert() can only spend from accrued[coin][asset], which is fee income that has already been collected. There is no path from it to an LP position.

It cannot choose where the money goes. The swap output must be VVV, the router is fixed at deployment, the allowance granted is exactly the amount being swapped and is reset to zero afterwards, and the VVV that comes back is split by the same constants as every other fee. A keeper cannot send itself anything.

The worst it can do is accept a bad price. A compromised keeper could set a low minOut and lose part of one conversion to slippage, bounded by the fees accrued in that single call. That is the whole of the trust placed in it.

What we cannot prove to you

That a launched coin is worth anything. Locked liquidity is not a floor, a promise, or a reason to buy. See the risks.

That nobody front-runs a collection. collect is deliberately permissionless, which means a buyer can buy, collect and claim in one transaction and take a share of a dividend they held the coin for seconds to earn. It is a known trade-off, stated in full in the risks.