Venues
Where a token actually trades, and how the console works it out.
A token's venue is the contract that will execute a trade in it. The console never assumes one. It asks the chain, because the answer changes over a token's life and differs per launchpad.
The phases of a token
- On a curve. The token is still on its launchpad. Buys and sells go through that launchpad's own contract. There is no pool and no pair anywhere, so routing such a token to a DEX quotes zero and sells nothing.
- Graduated. Enough supply sold, and the launchpad moved the liquidity into a real pool: PancakeSwap V2 on BNB Smart Chain, Uniswap V2 or a Uniswap V4 pool on Robinhood Chain.
- Neither. A token this console did not launch, or one whose pool it has no first-party path to. These go to an aggregator, which finds a route if one exists.
The venue names
| Key | Shown as | What it is |
|---|---|---|
curve | OneMeme curve | OneMeme's Core, pre-graduation |
fourmeme | Four.meme curve | four.meme's TokenManager |
flap | Flap curve | Flap's Portal |
pons | PONS curve | The token's own PONS curve contract |
v3 | V3 pool (Core) | A OneMeme VLP launch, priced through the Core |
pancake | PancakeSwap V2, or Uniswap V2 | A plain V2 pair, graduated or never launched here |
aggregator | Uniswap V4 pool, or Aggregator | KyberSwap, for a pool with no first-party path |
Every screen that names a venue prints the name that chain uses. If a screen says PancakeSwap, you are on BNB Smart Chain.
How resolution works
Given a token address, the console asks each launchpad on the chain whether it knows it, in order, and takes the first real answer. Only when none of them does, and no plain pair exists, does the aggregator get the question.
This matters more than it sounds. On a chain with several launchpads, "the native one has never heard of it" does not mean "it trades on a pair". It usually means it belongs to one of the others, and sending the trade to a router would quote zero.
The resolution is redone on every refresh, so a position that graduates between one look and the next simply changes venue on the page.
Reading depth
Selling needs more than a venue: it needs to know how deep that venue is, because that is what sets a shared minimum for a bundled sale. The console reads it where the shape allows:
| Venue | Depth read from |
|---|---|
pancake | The pair's token reserve |
curve, flap | Virtual supply left on the curve |
fourmeme | The manager's current virtual token reserve |
pons, v3, aggregator | Not readable as a single number |
Where it cannot be read, sales go one at a time rather than in a bundle, and the log says which. See Tokens.
Forcing one
A few tools let you pick a venue instead of resolving it, and the Bundler requires it. Picking one that does not match the token is refused with a sentence naming the right one, rather than silently traded somewhere else.
On a PONS chain the venue is always read off the token: the token itself knows whether it is on its curve or in its pool, so a forced choice there is checked against the token and refused if it disagrees.