launchpad mechanism · onchain.wrkr.dev
Bracket your launch.
When a project that built its product on wrkr decides to launch a token, Bracket bundles a coordinated first-buy at deploy — funded by ETH pooled from the project's own dev and the $WRKR community. Single atomic transaction via Clanker SDK. No MEV race. Pro-rata distribution to every contributor.
60-second walkthrough — how the launchpad works.
§01 · why bracket
Token-first launchpads gamble.
Bracket doesn’t.
The crypto space ships tokens before products. Bracket inverts the order: the project ships working product first, with paying customers, then the token launch gets coordinated. The community only backs Bracket launches because the product already exists.
§02 · the dual-track pool
Two tracks. One pool.
Dev track and community track contribute ETH to the same combined pool. At launch time, wrkr signs the Clanker deploy with the full pool as devBuy — guaranteed first-buy in the same atomic transaction as the token deploy.
Dev track
Project owner's own wallet
- ▸No $WRKR required — the dev is the builder
- ▸Optional — can skip and use community track only
- ▸Any ETH amount, no upper cap
Community track
$WRKR holders (many wallets, pooled)
- ▸Tier ≥ Basic threshold (set per event)
- ▸7-day minimum hold — prevents flash buyers
- ▸Max 10% per wallet of total pool — prevents whale domination
§03 · worked example
A 5-ETH pool.
One atomic buy.
§04 · what controls what
Wrkr signs the deploy.
Project keeps the value.
The “deployer” being wrkr does not mean wrkr owns the token. Clanker tokens are immutable with no admin keys; wrkr only signs the deploy transaction. The project keeps the rewardsConfig, the creator fees, and everything that matters.
§05 · the trade-off
What you gain.
What you give up.
▸ what the project gains
- +Coordinated atomic first-buy demand — no MEV race
- +Engaged early holders, not random snipers
- +Marketing distribution to the $WRKR community
- +Same Clanker creator fees: 1% of every swap, forever, 100% to project
- +Same on-chain ownership: token immutable, LP locked
- +Sniper protection via Clanker v4 (80% → 5% over 15s)
▸ what the project gives up
- −Dev-buy tokens go to all contributors (project keeps only the dev-track share)
- −Wrkr keeps 1% of pooled ETH (used to burn $WRKR — never held)
- −Community contributors can sell anytime (no lockup imposed)
- −Wrkr signs the Clanker deploy tx (project delegates the click, not control)
Don't want this trade? Deploy via Clanker normally. Bracket is opt-in. No coercion, no penalty, no hidden cost. The project owns the launchpad decision.
§06 · sniper protection
MEV bots pay the project.
Even with Bracket as the first buyer, Clanker v4 exposes a sniper auction window in the 15 seconds after deploy. Snipers pay heavy fees that flow into the creator's reward stream — turning attempted MEV exploitation into project revenue.
starting fee
80%
ending fee
5%
decay
linear over 15s
creator share
80% to project
Ship product first.
Bracket the launch when you're ready.