Schedules
A schedule is a scripted sequence of timed trades: exactly which wallet does what, and when, measured from the moment of launch. Use it for a snipe wave, a staggered entry, or a precise exit you can rehearse before firing.
Entries
Each row in the schedule is one trade.
- t, the time offset from the start, in seconds.
t = 0is the moment the dev buy confirms when run as a launch task, or when you start it on the desk. - Wallet, which wallet makes the trade (resolved at run time).
- Side, buy or sell.
- Amount. For a buy, the SOL to spend. For a sell, the percent of that wallet's token balance to sell (0 to 100).
+ Add row appends a step, Clear empties the table, and each row has a remove button. The editor preserves partial typing such as 0. so values are not clobbered while you edit.
Live preview
As you build, Winko simulates the schedule against the pump.fun bonding curve, tracking each wallet's holdings so sells unload realistic amounts, and draws the candles it would print with launch, peak and final market-cap readouts. You see the exact shape before you commit.
Warnings
- A buy that would exceed a wallet's SOL balance is flagged up front, so a step cannot fail silently on-chain.
- Sells show a pending state until their realized SOL output is known on the feed.
Saving and running
Saving sorts the entries by time and stores the schedule. Saved schedules appear in the Deploy task picker and the Winko desk + Task menu, summarized by entry count, total buy SOL and duration. When it runs, entries fire in time order and you see each one's status (queued, then fired, or skipped with a reason).