Automation
Automation and non-custodial design look incompatible: to trade while you are away, someone has to sign while you are away.
The product’s answer is that the server never signs. Volume Bot is on screen and does not run in this build. This page states the rule the feature is built on, not a claim that a plan is executing.
Division of responsibility
Section titled “Division of responsibility”Server Browser────────────────────────── ────────────────────────Decides "what to do now" Decides "whether and how"Keeps plans, budgets, clocks Reads pricesEmits an intent Builds, sets slippage, signs, submitsThe server never holds keys. What it emits is an intent (“wallet 3 buys 0.04 now”), not a signed transaction. Construction and signing happen in the browser.
Consequence: a compromised server can emit intents that nobody executes. It cannot move funds.
The cost
Section titled “The cost”The page must remain open.
There is no way to sign on your behalf while you are away, because the platform never has signing material. That is not a missing feature. It is the custody model.
Intended protocol, for when plans run:
- If the client stops polling past a threshold, the task marks itself stalled
- A stalled task does not replay its backlog on resume — an hour of missed trades at once is not the cadence you configured
- State is queryable; you should not have to guess whether it is running
A scheduled task that silently stops is worse than one that never starts. With the former, you believe it is running.
Volume plans — not enabled
Section titled “Volume plans — not enabled”Maintain trading activity for a token. Two phases: on the launchpad curve before graduation, and through a DEX router after.
Configurable, on the form: wallet count, total budget, trade-size range, sell ratio, sell size as a percentage of balance, interval, jitter, duration.
Design choices the form is built around (still not running):
- Trade size is computed against the remaining budget, so the last fill cannot overspend
- Interval jitter is symmetric, so the mean interval does not drift
- No sells before any buys
- No catch-up after a disconnect
Where to find the form: Launch (Tools → Volume Bot). Submit is disabled.
Telegram bot — not available
Section titled “Telegram bot — not available”There is no bot to add. If one ships, trade commands will return a deep link into the app rather than signing inside the chat. The extra click is the same custody split as above.
Not built
Section titled “Not built”Condition-triggered automation — “buy when a new address appears,” “sell in tranches at a multiple” — is not available. Clock-based volume plans are the only automation the product is built for, and they are not enabled. See Limitations.