The console is where a Pons volume bot run gets its shape. You paste a contract, the engine resolves it against the Pons catalogue and against Robinhood Chain over RPC, and it reports back what it found: the token, whether it is still on its bonding curve or has graduated, and how far through graduation it is. Nothing is charged during that step, and nothing is charged if the token turns out not to be a Pons token.
From there a run is defined by a small number of decisions. Volume target sets how much order flow the engine routes, starting at 10 ETH. Maker wallets set how widely that flow is spread, which is what moves the participant count aggregators read. Duration sets the window, and pacing and shape decide whether activity drifts evenly across it or concentrates into peaks. The buy to sell balance keeps both sides present, because flow that only buys reads as a single wallet accumulating rather than as a market.
These controls are linked rather than independent. Edit a swap size range and the maker count re-solves so the totals still add up to your target; move the target and order sizes rebalance underneath it. That is intentional: a configuration that does not reconcile is a configuration that will not execute the way it was drawn on screen. Timing jitter, slippage tolerance and gas priority sit underneath as the execution details, and their defaults are the ones most runs should keep.
Payment is a single transaction covering a flat 1% of the volume you configured, signed from your own wallet to the address printed on screen at that moment. A 10 ETH run costs 0.10 ETH plus your own gas. There is no deposit, no token approval over your supply and no subscription. The receiving address rotates across a pool between sessions, so the only address that is ever correct is the one currently rendered in the console, never one saved from a previous visit or received in a message.
Once the fee confirms on chain, execution opens and orders begin landing as ordinary Robinhood Chain transactions. You can watch them on Robinscan by filtering your contract, without asking anyone here for a report. If something goes wrong, the transaction hash and the paying wallet are enough to trace a run from end to end, which is the first thing the support desk will ask for.
