the launchpad
Bracketyour launch.
You shipped your product on wrkr. Now ship its token. Bracket is the launchpad for utility-first projects — the cult ($WRKR holders) pools ETH to back launches that already have something real behind them.
Built first
Wrkr
Product before token
Backed first
Cult
Pooled ETH at launch
Wrkr cut
1%
Of pooled ETH → burns
60-second Bracket explainer — see how the launchpad works
01 · why bracket
The launchpad for products, not promises.
Wrkr's job is roadmap → product. Bracket is the natural next step: product → token launch — backed by a cult that already knows your product is real.
Roadmap
You have a vision. A roadmap. Maybe a whitepaper.
Product
Wrkr turns it into a live product. Real users. Real revenue. Day one.
Bracket
When you launch a token for it, the cult that built your product also coordinates its launch. Pool ETH. First buyer. Pro-rata.
bracket vs everything else
Token-first launchpads
“Trust me, utility is coming Q3.”
- •Token launches first
- •Promise of product
- •Most never ship
- •Holders are gambling on whitepapers
Bracket
“Utility lives at this URL. Trade the token.”
- •Product ships first (on wrkr)
- •Token launches with real users behind it
- •Cult-coordinated first-buy
- •Holders are backing verifiable utility
Other launchpads sell you a promise.
Bracket sells you a product that already ships.
02 · two tracks, one pool
Dev + Cult. Same buy.
Two sources of ETH can pledge into the Bracket pool — the project's own developer, and the $WRKR cult (the holders). Everything gets combined into a single atomic first buy, and tokens distribute pro-rata to every contributor.
tl;dr
Hold $WRKR. Pledge ETH. You're in the first candle, pro-rata.
Dev track
optional · no $WRKR needed
The project's own developer commits ETH from their wallet.
- •Doesn't need to hold $WRKR — they're the builder
- •Effectively replaces Clanker's solo devBuy
- •Gets tokens pro-rata like any other contributor
- •Optional — skip it if you don't want dev tokens
Cult track
$WRKR holders · opt-in per launch
$WRKR holders pledge ETH from many wallets.
- •Must hold $WRKR to participate (tier thresholds)
- •7-day minimum hold (prevents flash buyers)
- •Max 10% of total pool per wallet (prevents whales)
- •Each holder gets tokens pro-rata to their pledge
combined pool → atomic first buy
Dev ETH + Cult ETH → ONE buy at launch
Each contributor
Pro-rata share
Of tokens received
Wrkr cut
1%
Of pooled ETH → burn $WRKR
Project receives
Real demand
First buy at launch price
“The cult” = $WRKR holders. Pool comes from many wallets. Dev adds their own slice. Everyone participates in the same first-buy transaction.
03 · how it works
The atomic first-buy.
PROJECT
built on wrkr · dev can commit ETH
Product already shipped. Launches token on Clanker. Optional: dev commits own ETH to the Bracket pool — no $WRKR needed.
BRACKET
first buyer · 1% of pooled ETH
Pools Dev ETH + Cult ETH. Executes ONE atomic first buy. Distributes tokens pro-rata to every contributor.
$WRKR CULT
pledged ETH · tier ≥ Basic
The cult = $WRKR holders. They pool ETH from many wallets during the commitment window.
Stays with wrkr → buyback & burn $WRKR
Wrkr never holds project tokens or asks the project for an allocation. We only execute the first buy and collect a small ETH fee. More Bracket activity → more burns → more $WRKR value.
// example · dev + cult
- 1. Project X ships its product on wrkr. Plans to launch $X on Clanker at time T.
- 2. Wrkr opens a Bracket window. Two tracks contribute:
- 2 ETH from Project X's own dev (dev track)
- 3 ETH from $WRKR holders across many wallets (cult track)
- Combined pool: 5 ETH
- 3. At time T (atomic): wrkr submits a 4.95 ETH buy on $X — first transaction on the new pool.
- 4. $X received → distributed pro-rata across every contributor:
- Dev gets 40% of $X (contributed 2/5 of the pool)
- Cult holders share 60% pro-rata to their individual pledges
- 5. 0.05 ETH (the 1% cut) → wrkr buys & burns $WRKR.
No reserves. No allocations. Dev and cult both pledge, both eat from the same buy.
04 · the interface
Built. Coming soon.
A preview of what the Bracket interface looks like — for projects, for holders, and during the launch itself.
01 · Project portal (dev side)
Launching
$YOUR · Base · Clanker
02 · Cult pledge (holder side)
Your tier
[Core] · 10× threshold met
Pledge
0.25 ETH
03 · Launch moment
Status
ATOMIC BUY EXECUTED ✓
Mockups, not live yet. The actual interface ships when $WRKR launches.
05 · the honest trade
Bracket isn't free.
It's a fair trade. Decide if it's worth it.
✓ What you gain
- •Coordinated first-buy demand atomic with deploy
- •Engaged early holders (real ETH on the line)
- •Marketing distribution to the $WRKR community
- •Your full Clanker creator fee (1% per swap, forever)
- •Same on-chain ownership — token immutable, LP locked
- •Sniper auction protection (Clanker v4 default)
✕ What you give up
- •Dev-buy tokens go to $WRKR holders, not your wallet
- •Wrkr keeps 1% of pooled ETH (used to burn $WRKR)
- •Pledgers can sell anytime — no lockup. Some early sell pressure is possible.
- •Wrkr signs the Clanker deploy tx (you delegate the click, not control)
Don't want this trade? Deploy via Clanker normally. No coercion, no penalty. Bracket is opt-in.
They build it. Then they back it.
They never gamble on whitepapers.
Two paths.
For project owners
Launch with users, not whitepapers.
Build the product on wrkr. When it has real users, launch its token through Bracket. The cult coordinates first-buy demand because they already know the product is real.
For $WRKR holders
Back utility, not vapor.
Hold $WRKR. Every Bracket launch is a token whose product was already built on wrkr — so your ETH backs verifiable utility, not whitepapers. First in, pro-rata.