Coins that own
a position.
Perpshood is a launchpad where every coin is backed by a live leveraged perpetual owned by that coin's own on-chain sub-wallet. Trading fees fund the perp; profits buy back and burn supply; drawdowns only add margin. The position never closes and nothing unwinds at graduation.
01Token
Every launch deploys a standard ERC-20 with a fixed 1,000,000,000 supply and no mint function. There is no inflation lever and no blacklist, so the only supply movement possible after launch is downward, through burns the keeper executes on the coin's behalf.
02Curve
Coins trade against a bonding curve from the first block. Every swap pays a flat 1% fee that funds the engine from block one. At a fixed threshold (4.2 ETH raised) the coin graduates into a full liquidity pool.
Graduation migrates liquidity. It does not touch the perp, the sub-wallet or the fee split: a graduated coin is simply a coin whose engine has been running longer.
03Sub-wallet treasuries
Each coin owns a program-derived sub-wallet. Fees claimed for that coin land there, margin for its perp is posted from there, and burns are executed by it. No two coins share a wallet, so no coin can be exposed to another coin's liquidation.
The keeper is the only actor permitted to move a sub-wallet's funds, and it can only move them along the four paths of the keeper loop.
04Market universe
Creators choose from 9 supported markets across two kinds: crypto and tokenized equities. Leverage is capped at 5× platform-wide and enforced at selection, so a launch can never open with a size the keeper would clamp.
Crypto
Max 25×Stocks - Tokenized
Max 25×05Routing
Orders route through a central limit order book, with collateral posted in USDG on Robinhood Chain and settlement built on Pons. A keeper service ticks every 15 seconds; it holds no discretion beyond the loop below.
06Fee split
Every claim divides by the split its creator locks at launch. The default is 30% to perp margin, 30% paid to the coin's holders as dividends in $PONS, 15% to the creator, 15% to the protocol (half to the treasury, half to the $PERPSHOOD buyback), and 10% to the coin's own buyback and burn. On the LP preset, that last slice becomes a liquidity slice that accrues as WETH and deploys into the coin's graduated pool.
A creator can move any slice but the protocol's: perp never drops below 20%, and dividends can go to zero. The proportions are stored per coin in basis points and enforced by a database constraint that requires them to sum to 10,000, so a claim cannot be split any other way.
Every claim, split five ways · The default
- 30%Perp marginThe engine grows with every claim
- 30%HoldersPaid as dividends in $PONS
- 15%CreatorPaid to the coin's creator
- 15%ProtocolHalf to the treasury, half to the $PERPSHOOD buyback
- 10%Buyback and burnThe coin's own buyback and burn
07Keeper loop
The loop is deliberately small. Claim, split, then either take profit or add margin. There is no discretion, no rebalancing, and no path that closes a position at a loss.
Keeper loop · 15s tick
Claim fees
Creator fees are claimed from the curve or the routed sub-wallet.
Split 30/30/15/15/10
30% funds the perp and 30% is paid to holders as dividends. The creator takes 15%, the protocol 15%, and 10% buys the coin back and burns it. The creator can reshape it at launch.
Profit slice
At +25% of collateral the keeper closes a fifth of the position, at most once every six hours. Realised profit goes 50% to holders, 25% to buy-and-burn and 25% to treasury.
Add margin
In drawdown, fees only top up collateral. A top-up only ever improves the seat.
08Position lifecycle
A position opens once $20 of fees have accrued, roughly a $2,500 market cap. Every claim after that adds its perp slice as margin at the current leverage, in profit or in drawdown alike. That is the flywheel, not a decision: fees keep flowing in whatever the mark does.
Separately, whenever floating profit is at or above +25% of collateral, the keeper closes 20% of the position and routes the realised profit half to holders as dividends, a quarter to buy-and-burn (or the LP slice) and a quarter to treasury. On a coin that pays no dividends it is 75% burn and 25% treasury. This happens at most once every six hours, so a position far over the bar steps down one slice at a time. The only time growth stops is a seat that is underwater to zero.
A top-up strictly increases collateral, so it can only improve the seat. The keeper declines to add margin only when the position is already underwater to zero. Adding margin can never itself become the cause of a liquidation.
Position lifecycle
- 01OpensOnce $20 of fees have accrued, at the creator's chosen leverage.$20
- 02Tops upEvery claim adds margin at the same leverage: size grows, leverage does not.+$20
- 03Takes profitWhenever profit is at or above +25% of collateral, close 20% of the position, at most once every six hours. Realised profit goes 50% to holders, 25% to buy-and-burn, 25% to treasury.+25%
- 04Adds marginIn drawdown, fees only add collateral. A top-up only ever improves the seat.Adds only
- ∞Never closesNo code path closes the position at a loss, and graduation does not unwind it.Permanent
09External tokens
A coin that launched elsewhere can attach the same flywheel. Its creator generates a one-use sub-wallet derived from their router and the token contract, then points creator fees at it. From the first claim onward it runs on the same keeper and burn schedule as a native launch, on the classic split: 50% perp, 15% creator, 20% protocol, 15% buyback and burn.
No wallet connection is required to derive the address, so the mechanic can be evaluated in full before anything is granted.
10Security
Zellic reviewed the two contracts Perpshood wrote and deployed itself, the Hookr launcher and the flywheel sweep module, over two person-days at a pinned commit. It returned zero findings at every severity, with one discussion note and no code change requested.
That is two contracts, not the whole platform. The Pons curve and factory, the keeper, holder payouts, and the treasury Safes and key custody were all outside the engagement, the last two as explicit non-goals. Below is what was covered, what was not, and the two weaknesses we found ourselves and accepted.
Critical, high, medium, low and informational: all zero.
In scope
PerpshoodHookrLauncher
Creates a hooked market, takes the payment, settles the coin back to the caller.
0x2Ccec970Efc0EA5FAB104Fd1244DA7B89dfd6561 ↗FlywheelSweepModule
Forwards the fee Safe's ETH to one immutable destination: the coin's engine wallet.
0xCF8B60ABA8D9017cDc2aB83b5A7948F39F1365B2 ↗Not in scope: most of what your money touches
- The Pons curve and factoryThird-party contracts every non-hooked coin launches and trades on.
- The keeperThe off-chain service that claims fees, runs the position and executes buybacks.
- Holder payoutsAnd the fee ledger.
- Treasury Safes and key custodyAn explicit non-goal of the engagement.
- Frontend and infrastructureAlso explicit non-goals.
Known and accepted: found by our own review, disclosed before the audit
The sweep is permissionless, so the fee Safe's ETH sits behind one key
It can only ever send to one immutable address, the coin's engine wallet. But that wallet is a single key, so for native ETH the 3-of-5 is not what protects it. Accepted because the Safe is emptied every tick, making the exposure the float between sweeps rather than a reserve, and the reserve Safe does not have the module enabled.
Anyone can call the launcher with their own fee recipient
feeRecipient is caller-supplied and unchecked, so a stranger can open a Hookr pool that records Perpshood as creator while the LP fees go to them. Accepted because it is not a fund-loss path (they pay our tier), and the keeper never adopts such a coin, so it never gets a perp position.
The audited source is the source that is running: both contracts are verified on the explorer, and their deployed bytecode matches artifacts built from commit 15bb2851, byte-length identical, differing only in constructor immutables and the metadata hash. An audit is a point-in-time review of a fixed commit, not a guarantee about code added after it.