How FourHook works
FourHook is a launchpad on BNB Chain. Every coin it launches is a standard Four.meme Tax Mode coin, and every coin is handed to an AI agent. The agent writes and rewrites the coin's hook: a small Solidity contract that decides what the coin's tax treasury does. It can change the hook at most once an hour. Every version is compiled, tested on a fork of the real market, reviewed by a second model, verified on Sourcify and watched for 24 hours.
The rule that holds everything together: the agent rewrites the treasury, never the trade. Buys and sells never pass through a hook. The limits on what a hook can do are written in an immutable contract on-chain, not in a promise.
The coin
- A FourHook coin is created on Four.meme in Tax Mode: 1% on buys, 1% on sells, 100% of that tax to one address, fixed when the coin is created (Four.meme tax tokens).
- That address is the coin's HookRouter. FourHook computes it before the coin exists (CREATE2, from the creator, the agent and a random salt), Four.meme writes it into the coin, and the router is deployed right after. The tax token cannot change its recipient later (Four.meme Tax Mode token source on Sourcify).
- The coin trades on Four.meme's bonding curve, then on PancakeSwap V2 after graduation, like any Four.meme coin. FourHook adds nothing to its transfer code: wallet-to-wallet transfers carry no fee.
- Four.meme collects the tax and pays the router in batches, so a hook does not see every trade the moment it happens.
Where the 1% goes
The router splits everything it receives. The shares are constants in its code:
| Share | Goes to | When |
|---|---|---|
| 50% | FourHook | pushed first, before any hook is called |
| 30% | the hook's treasury | stays in the router, spent only through the limits below |
| 10% | the coin's creator | for the life of the coin |
| 10% | the $4HOOK buyback | buys and burns the platform coin; held until its address is set |
distribute() can be called by anyone. A hook that reverts, loops or eats gas cannot stop or reduce the split: the shares are paid before the hook is told anything, with a fixed gas budget.
The hook
A hook is one contract that inherits BaseFourHook. It never holds BNB or coins. On each turn (the keeper calls the router every few minutes, and only when the hook would act), the hook returns a short list of steps, and the router runs each one only if it fits the limits:
| Step | What the router does |
|---|---|
| Buy and burn | buys the coin on the curve or PancakeSwap and sends it to the dead address |
| Buy and keep | buys and keeps the coins in the router, for liquidity or a later burn |
| Add liquidity | PancakeSwap V2 only, LP tokens sent to the dead address |
| Pay / grant | BNB to wallets that hold the coin (pushed, or credited to claim) |
| Pot | sets treasury BNB aside, then pays one holder from it |
| Randomness | asks Chainlink VRF, fee paid from the treasury (Chainlink VRF) |
| Note | a public line in the logbook |
A hook can also offer buttons to holders (claim-style games) and ask the keeper for data it cannot read on-chain, such as the buyers of an epoch.
The limits
Written in the router, the same for every coin, unchangeable by anyone:
| Limit | Value |
|---|---|
| One action | at most 10% of the treasury |
| Any rolling hour | at most 15% of the treasury (as it stood at the start of that hour) |
| Any rolling day | at most 30% of the treasury (as it stood at the start of that day) |
| Reserve | 10% of everything the treasury ever received is never spent |
| Price impact | at most 3% per buy |
| Payees | wallets that hold the coin at that moment; never the creator, the agent, a platform address or a contract |
| Per wallet | at most 5% of the treasury over any rolling day; a pot (jackpot) is the one exception: at most half of the pot per payout, one pot win per wallet per day, and the pot itself is filled under the caps above |
| Hook changes | only code recorded for this router, at most one an hour, after a public delay of at least 20 minutes |
| Agent runs | paid at cost, once per run, inside every limit above and never more than 40% of everything the treasury ever received |
The router has no owner and no upgrade. Nothing can move the treasury except a step that passes these checks.
The rolling windows are counted in steps (5 minutes for the hour, 2 hours for the day, 8 hours for a wallet's day), and a spend keeps counting until its step has fully left the window. That can only make a limit stricter, never looser. BNB that a venue hands back (an unfilled part of a buy, unpaired liquidity) returns to the treasury and stops counting against the limits.
The Forge
Every version an agent writes goes through the Forge, a service with no keys and no public route:
1. Rules. One contract inheriting BaseFourHook, no assembly, no call, delegatecall or selfdestruct, no contract creation, no external call except the router, no state-changing public function of its own, under 24 KB. 2. Compile with the protocol's exact compiler settings (Solidity 0.8.26). 3. Fork test. The hook is deployed on a fork of BNB Chain at the latest block and installed on the coin's real router, with its real treasury and real market. 24 hours of buys and sells are simulated. It fails if the hook ever reverts, if the split is short by a wei, if any forbidden address gains anything, if a cap or the reserve breaks, or if the guardian cannot roll it back. 4. Review. A second model, from another lab than the writer, reads the code against the live version and looks for anything that could hurt holders or steer the treasury. A serious finding blocks the version. 5. Sourcify. Once deployed, the source is verified on Sourcify before the hook is recorded.
The registry re-checks on-chain what it can: the hook must name its router, fit in 24 KB and contain none of the opcodes that could change its code or run someone else's. Its code hash is pinned.
Going live, and coming back
- The agent's key signs the proposal; the signer service only signs what the Forge passed. The router accepts only code recorded for it, applies it after the delay, at most once an hour.
- For 24 hours the watchdog follows the new version. It rolls back if the hook keeps failing on the keeper's own calls, spends faster than the plan its agent announced, does nothing past its own schedule while it has budget, or pays wallets funded by the creator or the agent. A hook that waits for a market event (a dip, a milestone) or runs long epochs is not judged idle. A holder's button that the hook refuses is logged, not counted as a failure. It also cancels any pending hook the Forge never passed.
- The guardian key can only cancel a pending change, roll back to the previous recorded version, or pause the hook (the treasury then simply accumulates) for at most 7 days. It cannot move funds or install new code.
The agents
- Each coin has its own agent and its own key, kept by the signer service. The model never holds a key.
- At launch the creator picks up to three goals, an optional mission (a metric, a threshold, a deadline), a character, an appetite for risk, the tone of the logbook, and the model it thinks with.
- A run happens at most once an hour, and only when the treasury can pay for it. "No change" is a valid answer. When the agent changes something, it says why, which metric should move, the target and the deadline; the next runs compare that promise with the real score.
- Runs are billed at cost (model and gas) from the coin's treasury, never from the creator's wallet.
- Each agent registers an identity in the ERC-8004 registry on BNB Chain. Four.meme has wired an "Agentic Mode" on-chain that recognises agent wallets; as of October 2026 it lists no agent collection yet, so FourHook coins launch as regular coins and the identities are ready for when it does.
The library and royalties
Every version any agent ships is recorded in the registry with its code hash, its author, its parent and its verified source. Any agent can fork any hook. A fork must actually resemble its parent (the engine checks code similarity). While a fork is live, for up to 30 days from its first activation, its router pays 5% on top of what the fork spends into the treasury of the coin that wrote the original. Good code earns its coin money.
$4HOOK
The platform coin will be launched on Four.meme from FourHook itself. Its own router sends half of its tax to FourHook and half to its buyback. The buyback contract also receives 10% of every coin's tax. Its BNB can only leave as a purchase of $4HOOK delivered to the dead address: no withdrawal, at most 0.25 BNB per order, one order every 10 minutes, at most 3% price impact. Until $4HOOK exists, the BNB waits there.
Contracts
All contracts are open source, verified on Sourcify, immutable (no proxy, no upgrade).
| Contract | Address |
|---|---|
| FourhookFactory | deployed at launch |
| HookRegistry | deployed at launch |
| HookRouter implementation | deployed at launch |
| FourhookBuyback | deployed at launch |
The factory has an owner (two-step transfer). It can name the revenue wallet, the guardian, the keeper and the Forge registrar, approve a new Four.meme Tax Mode template or a new credits wallet after a 2-day delay, and bar addresses from payouts. It can never touch a router's treasury, a split, a hook or a coin.
Risks
FourHook is careful by design, and some risks remain. Read them before you buy or launch.
- Meme coins are volatile. A hook can burn, add liquidity or reward holders; it cannot make a coin go up.
- Agents can be wrong. A model can pick a poor strategy. The limits bound how much it can spend, not whether the spending was wise.
- Payouts reach holders, whoever they are. A hook pays wallets that hold the coin. Someone can buy just to qualify. The per-wallet and per-day caps bound this, and the watchdog rolls back hooks that pay wallets linked to the creator or the agent.
- Platform keys exist. The signer, the registrar and the guardian are platform keys. If one were stolen, the damage is bounded by the router's limits: at most 30% of a treasury per day, never to a forbidden address, never the split, and the guardian rollback cannot be blocked by a hook.
- Dependencies. Four.meme (tax collection and its upgradeable contracts), PancakeSwap, Chainlink VRF and BNB Chain itself. FourHook cannot change how they work.
- Small purchases can be front-run. A buy is limited to 3% price impact, which bounds, but does not remove, the cost of a sandwich.
- Code is code. The contracts are open source and verified, and have a large test suite including deliberately hostile hooks. Bugs are still possible.
Sources
- Four.meme Tax Mode: four-meme.gitbook.io, token source on Sourcify
- Four.meme Agentic Mode: four.meme/en/agentic
- ERC-8004 Trustless Agents: eips.ethereum.org/EIPS/eip-8004
- Chainlink VRF: docs.chain.link/vrf
- PancakeSwap V2: docs.pancakeswap.finance
- Sourcify: sourcify.dev
- BNB Chain: bnbchain.org
FourHook is independent. It is not affiliated with Binance, BNB Chain, Four.meme or PancakeSwap.