Boss BoostPad

Demo

About

Boss BoostPad turns a token the creator already holds into a boss raid on Uniswap v4. A normal pool lets people trade, but it gives them nothing to defeat and no shared prize. In Boss BoostPad, the creator opens the blacksmith, pastes that token, and sets three things: how many tokens go into the pool, the MockUSD volume the raid must reach, and what share of the deposit becomes the prize. Every boss has three fixed stages and the same default portraits. There is no expiry and no way for the creator to cancel the raid. Fighters enter from the garden hub and attack on the battle screen. An attack is a swap through that boss's pools. Each confirmed attack adds to that boss's eligible swap volume. A trade made in some other pool does not count. Holding the token, or sending it to someone else, does not count either. The volume target is three goals, sized 1, then 2, then 3. A 60 MockUSD target means stage goals of 10, 20, and 30. Clearing the first stage starts a shared 60-second cooldown. Clearing the second starts a shared 120-second cooldown. While the cooldown is running, the next attack waits. The sale tokens are already in the pool when the boss launches, and the price follows the pool as people buy. Clearing a stage starts the cooldown. It does not open a second hidden inventory, refill the pool, or reset the price. After the third stage, eligible fighters share the creator-funded prize, paid in the same token. They keep every token they bought during the fight. The claim is a separate reward credit, earned only by that fighter's attacks on that boss. Sending tokens to another wallet does not move that credit. The creator funds the prize up front and cannot take it back. The creator can later add or remove a separate liquidity position to change how deep the pool is. That position sits above the locked launch liquidity, and those changes do not count as attacks or prize credit. The garden hub, the blacksmith workshop, and the battle all run in the browser.

How it's made

Each Factory boss has a dedicated Uniswap v4 pool with its own BossHook. PoolManager invokes the Hook during boss-pool swaps, so the raid rules apply regardless of which website submits the attack. BossHook accepts swaps only from that boss’s dedicated BossRouter. Other interfaces can use the Router, but cannot bypass its checks. If an attack fails a check, both swaps and all resulting raid credit revert together. Trading the same token in another pool does not earn raid credit. Once the fighter has approved MockUSD, an attack executes in one transaction and one PoolManager unlock. It performs two swaps. The fighter first buys Attack Token in the shared MockUSD supply pool, then spends that Attack Token in the boss pool to buy the creator’s existing token. The Router returns unused MockUSD and Attack Token to the fighter. At launch, BossFactory deploys the boss’s Router, Hook, and collectible contract, takes the creator’s token deposit, escrows the prize in the Hook, and activates the full sale liquidity. Before the boss swap, BossHook verifies the authorized route, current stage, and shared cooldown. After the swap, it records the actual boss-token output, eligible MockUSD volume, and the fighter’s reward credit. Eligible volume counts the share of MockUSD spending attributable to Attack Token used in the boss swap: eligible volume = floor(MockUSD spent × Attack Token spent / Attack Token bought) The boss-token output determines damage and reward credit. No token is burned, and the fighter receives the purchased tokens. The creator’s volume target splits into three additional stage goals in a 1:2:3 ratio. For a 60 MockUSD target, fighters must contribute 10 MockUSD in stage one, another 20 in stage two, and another 30 in stage three. Clearing stage one starts a shared 60-second cooldown. Clearing stage two starts a 120-second cooldown. These pauses give the community time to regroup between phases. The Hook stores the reopening timestamp and rejects attack quotes and execution until that time. All sale liquidity is active from launch. Stage transitions preserve the pool’s price and liquidity, with no additional token allocation or price reset. Cooldowns control raid pacing without guaranteeing equal participation or preventing bots. The documented Boss deployment charges a 0.3% LP fee on each swap. The supply swap charges its fee in MockUSD, and the boss swap charges its fee in Attack Token. Both fees are included in the quoted output. For fully spent inputs, ignoring price impact and rounding, the combined fee-only output reduction is approximately 0.5991%: 1 − 0.997 × 0.997 = 0.005991 Actual output also depends on both pools’ prices, liquidity, execution limits, and unused-input refunds. ETH gas is separate and can still be charged when a submitted transaction reverts. Swap fees accrue to the LP positions. BossFactory charges no launch fee, and the creator funds the prize separately. Boss uses fixed fees and has no fee controller. The optional local demo uses an owner-controlled mock reference to adjust only the boss-pool LP fee. When the pool price is below the reference, the controller raises the fee to make discounted purchases more expensive. When the pool price is above the reference, the fee decreases and can reach zero. The supply-pool fee remains 0.3%. This demonstrates reference-based purchase pricing. It does not track a trustworthy live market oracle, reset the AMM price, or guarantee protection from arbitrage. The browser app uses Next.js and Phaser. Phaser runs the walkable garden hub. At /boostpad, creators inspect token metadata and balances, request a funding quote, approve the deposit, and launch a boss. Before launch, the SDK finds a CREATE2 salt that produces a Hook address with the required Uniswap v4 permission bits. The battle page reads contract state and submits attacks through viem on Base Sepolia. Confirmed contract execution determines whether an attack counts, and the browser displays that result. Factory prize rights are nontransferable credit recorded for each fighter by BossHook. After victory, a claim consumes that credit and pays a proportional share of the creator-funded prize in the creator’s token. The share depends on credited boss-token output, rather than MockUSD spending. Claiming requires no token approval or surrender of purchased tokens. Those tokens remain in the fighter’s wallet, and transferring them does not transfer prize credit. The older standalone demo uses transferable reward-bearing tokens and a MockUSD prize. Factory bosses use per-player credit.