Static after launch
Tokens today are usually static once they are live. Whatever was set at launch is what they do forever.
Nothing changes when the token trades, and nothing changes when it hits a milestone.
Programmable launchpad
Launch tokens
with any rule.
A launchpad for tokens with programmable behavior. You define IF → THEN rules that control what the token does after it launches.
A rule on Rulepad
IFsomeone buys
THENroute part of the fees into liquidity
IFfees are generated
THENdistribute a percentage to holders
IFmarket cap reaches $100K
THENburn part of the supply
IFvolume reaches a milestone
THENunlock a new rule
IFfees are generated
THENuse a percentage to buy another supported asset
IFa milestone is reached
THENchange how future fees are split
Trigger + action. That is the whole rule.
- 8kinds of rule
- IF → THENone line per rule
- Livethe builder is open
The core primitive
Every rule is one line:IF something happens → THEN do something.
The trigger defines when the rule activates. The action defines what happens next. Pick one of each, set the amount or destination, and the token launches with that behavior already written in.
IF
THEN
route part of the fees into liquidity
distribute a percentage to holders
burn part of the supply
unlock a new rule
use a percentage to buy another supported asset
change how future fees are split
Preview
IF someone buys → THEN route part of the fees into liquidity
Liquidity
Why now
A token stops being yours the moment it launches.
Tokens today are usually static after launch unless developers build custom infrastructure around them. Everything interesting a token could do is decided somewhere other than the launch flow.
Behavior means building
Anything more than the defaults means developers building custom infrastructure around the token.
Every mechanic is a bespoke contract, written and audited before a single trade happens.
Only the surface competes
So launches compete on names, memes, branding and distribution — because that is all that is left to choose.
The one thing a token actually does is the one thing creators cannot change.
What you are actually building
Three choices, and the token has behavior.
The rule builder
Pick a trigger. Pick an action.
Every rule has two parts. The trigger defines when the rule activates; the action defines what happens next. You choose both from a list, set the amount or destination, and that is the whole rule.
Rule stacks
A token does not have to use only one rule.
Combine compatible rules into a stack: part of the fees to liquidity, part to holders, part to a treasury, plus a milestone rule that switches on a burn later. Two tokens built in the same interface can behave completely differently.
The preview step
See exactly what it will do, before it does it.
Before launching, the rule is read back to you in plain words. No contract to read, no parameters to decode — just the sentence the token will live by.
Rule categories
Eight kinds of rule. One interface.
Fees, rewards, burns, buybacks, liquidity, treasuries, milestones and conditions. Every rule is one category, one trigger and one action — and compatible rules combine.
Buyback rules
Route fees toward buying a selected supported asset or token.
Burn rules
Reduce supply when a chosen condition is met.
Reward rules
Route generated value to holders.
Liquidity rules
Send part of fees back into liquidity.
Treasury rules
Accumulate selected assets in a treasury.
Split rules
Divide fees between multiple destinations.
Milestone rules
Activate new behavior at market cap, volume, holder, or other defined thresholds.
Conditional rules
Change how the token behaves only when a chosen condition becomes true.
How a launch works
Seven steps, and five of them are new.
The experience should feel as simple as a normal launchpad. The complexity stays underneath the product while you see a straightforward IF → THEN interface.
01
Create the token
Name, ticker, supply — the same first screen as any launchpad. Nothing new to learn yet.
02
Choose your rules
Pick one or more compatible rules from the eight categories. One is enough; several stack.
03
Select the trigger
The trigger defines when a rule activates: a buy, fees being generated, a milestone being reached.
04
Select the action
The action defines what happens next: buy back, burn, reward, add liquidity, split, unlock.
05
Set the amount
The percentage, amount, destination, or milestone. This is where a rule stops being generic.
06
Preview the rule
Read back exactly what the rule will do, in plain words, before anything is live.
07
Launch the token
The token goes out with its behavior already written in. No custom code, no second deploy.
Rule stacks
A token does not have to use only one rule.
Compatible rules combine into a stack. Two tokens launched from Rulepad can have completely different behavior even if they were created through the same interface.
IF fees are generated
One fee flow
- THEN Liquiditypart of the fees back into the pool
- THEN Holderspart distributed as rewards
- THEN Treasurypart accumulated in selected assets
And one rule that is not on yet
IF the token reaches a defined market-cap threshold → THEN activate a new burn mechanic.
A milestone rule sits in the stack from launch and switches on when its condition becomes true. The behavior changes; nothing needs redeploying.
Why Rulepad is different
Most launchpads customize what a token starts with.
Everywhere else
You choose what the token starts with.
- Name, ticker, supply
- Launch settings
- Then it is fixed
On Rulepad
You choose what the token does after it launches.
- What should trigger a rule
- What should happen, and how much
- Where value should go
- When the behavior should change
That makes behavior itself part of the creative surface. Tokens can compete on mechanics, not only names, memes, branding, or distribution — and none of it turns Rulepad into a developer dashboard. The smart-contract complexity stays hidden; what is exposed is a list of simple choices.
FAQ
Frequently asked questions
Eight questions, short answers.
A launchpad for tokens with programmable behavior. Instead of only choosing a name, ticker, supply and launch settings, you also define rules that control what the token does when it is traded or when certain conditions are met.
A trigger plus an action: IF something happens → THEN do something. The trigger defines when the rule activates. The action defines what happens next. You set the amount, percentage or destination, preview it, and launch.
No. Rulepad turns advanced token mechanics into a rule builder, so you do not need to write custom logic for every launch. The smart-contract complexity stays underneath the product; what you see is a list of choices.
Yes. Compatible rules combine into a rule stack — a launch could route part of its fees to liquidity, part to holders and part to a treasury, with a separate milestone rule that activates a burn once it reaches a defined market cap.
Eight categories: buyback, burn, reward, liquidity, treasury, split, milestone and conditional. Between them they cover fees, rewards, burns, buybacks, liquidity, treasuries and threshold-triggered changes.
Most launchpads let you customize what a token starts with. Rulepad lets you customize what it does after it launches. That makes behavior itself part of the creative surface — tokens can compete on mechanics, not only on names, memes, branding, or distribution.
That is what milestone and conditional rules are for. A milestone rule activates new behavior at a market cap, volume, holder or other defined threshold; a conditional rule changes how the token behaves only when a chosen condition becomes true.
Yes — the builder is linked from the top of this page.
A launchpad lets you pair a token with a name.
Rulepad lets you make a token do anything.