Customize your token launch with your own rules.
The difference
Most launches run on promises. Yours can run on rules.
A promise lives in a tweet. A rule lives in the token’s contract and is checked on every single transfer, by the chain, not by a moderator.
Wallets are capped.Said in a tweet
Team tokens are locked.Shown in a screenshot
It’s a fair launch.Until the bots arrive
We burn on every trade.When someone remembers
Holders get rewards.From a wallet someone controls
Anatomy of a transfer
Every move runs the gauntlet.
- 01
A trade arrives
A wallet buys, sells or sends your token. It could be a person or a bot. The token does not care, it just asks the rules.
- 02
The token asks every hook
Before a single balance changes, the transfer function calls its sealed rule set. Each hook sees the sender, receiver, amount, gas price and the clock.
- 03
One “no” reverts the trade
If any hook refuses, the whole transfer reverts. Nothing moves, and the reason is right there in the transaction.
- 04
Everyone else settles, fees routed
Allowed transfers settle in the same block, and fees go exactly where the rules say: burn, liquidity, rewards.
The library
Six families of rules.
Combine as many as you like, or none of them. Every hook has plain-English rules, adjustable numbers, and a note about what it cannot do.
Family
Access
Who can hold or receive
Decide who is allowed to buy, hold or receive. Lists, gates and invites, enforced by the token.
Family
Launch shield
A fair opening
Protect the first minutes. Block-level quotas, gas ceilings and cooldowns that make sniping unprofitable.
Family
Limits
How much
Cap wallets, buys and sells. Static caps, rising caps, or caps that react to price.
Family
Timing
When it trades
Open and close the market on a schedule counted in blocks, hours or vesting time.
Family
Rewards
Who gets paid
Route a slice of every trade to holders: crowns, draws, dividends and lifelines.
Family
Burn & liquidity
Where fees go
Send fees to burns, buybacks and deeper liquidity so supply and depth move in your favour.
Start from a preset
Pick a starting point. Change anything.
Each preset is a handful of hooks that work well together. Start from one, then add, remove or retune rules in the builder.
Why BNB Chain
Fast enough for rules that count blocks.
Rules are only useful if they are cheap to check and easy to read. BNB Chain gives both, and it already has the liquidity.
Blocks that keep up with your rules.
BNB Chain produces blocks in well under a second, so a hook can count in blocks without a keeper, and an opening window ends when it should.
Pool hooks on PancakeSwap Infinity
Four hooks run inside the pool itself: Router Gate, Sinking Fee, Depth Fee and Fee Share. Token-level hooks cover everything else.
Readable on BscScan
Every launched token ships with verified source and a rules() view that prints its hooks in order.
A normal BEP-20 underneath
Wallets, explorers and routers recognise it. A refused transfer shows its reason in the transaction, not a mystery error.
Verify, don’t trust
Read the rules before you buy.
A rule you cannot read is just another promise. Every token launched with 4HOOK carries three things you can check yourself in under a minute.
- 01
Sealed rule set
The hook list is fixed at deploy. There is no function that edits it, and no owner key that could.
- 02
Verified source
The token and each hook are verified on BscScan, with parameters stored as immutable values.
- 03
A plain-English readout
The token’s page prints its rules in sentences, generated from the same parameters the contract uses.
$4HOOK
Every launch feeds a burn.
A small protocol fee on launched tokens buys $4HOOK on the open market and burns it. Every burn is a transaction you can open on BscScan.
The fee split is published in the docs before the first launch. Burns appear on-chain once the contracts are live.
$4HOOK
Roadmap
What gets built, in order.
What is a hook?
A small piece of contract logic that runs on every transfer of your token. It can allow the transfer, refuse it, or take a fee. 4HOOK ships a library of them in six families, and you choose which ones your token carries.
Can the rules be changed after launch?
No. The rule set is sealed when the token is deployed. Nobody can edit, remove or add hooks afterwards, including the 4HOOK team. If you want different rules, you launch a new token.
Does a rule stop a determined bot?
Rules raise the cost of specific behaviour. They do not make attacks impossible: a holder can split across wallets, and block builders can still order transactions. Every hook lists its own limits so you know what it does and does not cover.
Which chain is this on?
BNB Smart Chain. Tokens are BEP-20 underneath, so wallets, explorers and routers recognise them. Blocks are fast, so time-based rules are counted in blocks or seconds, whichever reads better.
Where do tokens trade?
Token-level hooks work anywhere the token trades. Pool-level hooks (Router Gate, Sinking Fee, Depth Fee and Fee Share) need a PancakeSwap Infinity pool. Each hook is marked so you can see which is which.
What does $4HOOK do?
A share of protocol fees buys $4HOOK on the open market and burns it. The exact split is published in the docs before the first launch.
Is it audited?
The Security page shows audit status and updates when a report is published. Until a report is linked there, the answer is no, and you should read the source yourself.
What can go wrong?
Every hook adds gas to each transfer, a rule can be configured badly, and rules do nothing about market risk. The builder estimates gas, warns about conflicting hooks and lets you test transfers before you commit to a rule set.
Ready when you are
Your token. Your rules.
Choose your hooks, read every rule in plain English, and know exactly what your token will enforce before you launch.