Skip to main content

Automations

The automations step holds the things a launch does for the creator rather than the things it configures. They are grouped by when they run.

In the deploy transaction​

The dev buy​

Bots watch new coins and buy in the opening block, ahead of anyone reading about them. The dev buy is the counter: the creator buys inside the launch transaction itself, before the coin is reachable by anyone else.

It is optional, entered as a percentage of supply, and the form works out the ETH it will cost. On a curve launch it is a purchase from the curve at the curve's own price; on an instant launch it is the pool's first swap, paying the normal fee.

Standard cap15% of total supply
Hard ceiling25%, not raisable by the protocol team

A dev buy above the cap does not deploy.

It is a purchase, not an allocation: the ETH goes into the raise like any other buy, the trade pays the standard fee, and nothing is carved out of supply. It is also not hidden — the position appears on the coin's Holders tab from the first block, and on the creator's own wallet page.

Pairing it with vesting locks that position on a schedule immediately, before the coin has graduated, which is the one thing that turns "I am not going to sell" into something readable on-chain.

After the launch​

The step also lists the automations that run later rather than at deploy. They are shown on the form before they are available, so the step reads as what it is — room for more — and the app marks each one as it ships:

  • vesting your own supply, scheduled at creation instead of set up afterwards;
  • scheduling a highlight, booking front-page placement ahead of the launch.

More will be added on the same principle: something the creator would otherwise have to remember to do, done by the launch itself. What exists today as a separate tool is documented in Tools.