Setup Desk
Volume console

Settings: what each field on the form changes

Three field guides for the boxes people get stuck on. Each takes one part of the form, explains what it accepts, what it changes downstream, and which check catches the mistake before it costs anything.

01 Token and venue The token field wants a mint address copied from an explorer, and the venue field decides which pool or curve every swap in the run is routed through. Pasting the right mint, reading the validation states, and picking between a bonding curve and a pool when the same token trades in more than one place. Open Field guide 01 02 Wallets and swap size Wallet count decides how many separate addresses send the trades and how much SOL is locked up in overheads; swap size decides how much each trade moves the pool. Two numbers that set the cost floor of a run, with the funding arithmetic worked in full and a table of what changes when you move each one. Open Field guide 02 03 Budget caps and duration A budget cap is the amount the panel is allowed to spend before it stops itself, and duration is the window it spreads the work over; whichever limit binds first ends the run. How caps, duration and per-wallet limits interact, what each one counts and ignores, and what actually happens to in-flight transactions when a run stops. Open Field guide 03

Why these three and not the whole form

Most boxes on a setup screen are displays of a decision already made, or defaults that are fine at any sensible value. Three groups are not. The token and venue pickers decide what you are trading and where, and getting either wrong makes every other setting irrelevant. Wallet count and swap size set the cost floor of the run before a single trade lands. Budget cap and duration decide when the whole thing stops, which is the only field group where a misunderstanding can cost more than you intended to spend.

Each guide is written to be read while the form is open. The structure is deliberately repetitive: what the field accepts, what moves when you change it, a worked example with the arithmetic shown, and a short list of checks to run before saving. If you only have a minute, the checks at the bottom of each page are the part to read.

They are meant to be read together

The three interact, and that is the point most guides skip. Venue depth constrains swap size, because impact scales with size relative to reserves. Swap size and wallet count together imply a trade count. The trade count has to fit inside the duration, and the cost of that many trades has to fit inside the cap. Decide them in that order and the numbers agree with each other; decide them in the order the form presents them and you will be back-tracking.

Where the numbers in these pages come from

Two kinds of figure appear. Protocol constants, such as the signature fee, are stated as constants and can be checked against public documentation. Everything else is illustrative arithmetic, with every input named, chosen so you can substitute your own numbers and follow the same shape. Nothing here reports what a real run achieved, because this desk has no way to verify such a claim and no interest in inventing one.

If a field on your panel is not covered by any of these three, it is likely a display, a routing preference or a convenience toggle. Send it to the desk and it will either be answered directly or added, whichever is more useful.