Setup Desk
Volume console

Walkthroughs: the whole run, step by step

Three pages that cover a run from an empty panel to a finished report. Read them in order the first time; after that, each one stands on its own and answers a single question about what happens at that stage.

01 Setting up a run Setting up a run means filling one form: a token, a venue, a wallet count, a swap size, a budget cap and a duration, then reading the confirmation screen before anything is signed. The full sequence from an empty panel to a running job, with a reference table for every field on the form and the arithmetic behind a first small run. Open Walkthrough 01 02 Connecting a wallet A panel touches your wallet in one of three ways, and only one of them is safe to do casually: connect and sign, deposit to an address, or hand over a key you should never hand over. The three custody patterns behind a connect button, how to read a signature request before approving it, and the requests that are always a theft attempt. Open Walkthrough 02 03 Reading the report A run report has three parts: header totals, a per-transaction log with a status on every line, and a cost breakdown; the status column is the part worth reading first. Every line of a finished run explained, why attempted and landed volume differ, and how to check the panel against a block explorer without trusting either. Open Walkthrough 03

How a walkthrough here is put together

Every walkthrough follows the same shape, because the shape is what makes it usable while you are actually looking at a screen. It opens with the one sentence that answers its own title, so you can leave immediately if that is all you needed. Then a numbered sequence, where each step names the action and the consequence together. Then a reference table, because the sequence describes the happy path and the table covers the fields you meet in a different order on a different tool.

What you will not find is a claim about any particular product's screens. Layouts move between releases and vendors rename fields, so a walkthrough tied to one build goes stale within weeks and is worse than useless once it does. These pages describe what a field is for, which is stable, and leave you to find where your own panel put it.

The order that works

Setting up a run comes first because it is the map: the whole sequence in nine steps, with the arithmetic for a small first run worked out in full. Connecting a wallet comes second even though you do it earlier in practice, because it is the step where an irreversible mistake is possible and it deserves reading before clicking rather than while clicking. Reading the report comes last because it is the only page that tells you whether the estimates in the first two were right.

If you are mid-form and stuck on one specific box, the field guides in the settings section are the faster route. They take one field at a time and go deeper on the consequence: what depth does to swap size, what a wallet count costs before any trading happens, and what a budget cap actually counts.

What these pages refuse to do

No walkthrough here asks you to reveal a seed phrase, a private key or a keypair file, and none suggests a workaround that involves one. Where a real workflow would require handing over a key, the page says why that is the end of the conversation rather than describing how to do it carefully.

None of them promises an outcome either. A panel can produce transactions and a report can tell you what those transactions cost. Whether the activity is noticed, counted or rewarded is decided by other people's software, and a setup guide that pretends otherwise has stopped being a setup guide.