How a Prysm pool answers.

1. Launch. The launchpad deploys a plain ERC-20 (1B supply), writes your rules into PrysmHook, opens a Uniswap v4 ETH pool and puts the whole supply into it as one position that is never withdrawn.
2. Swap. On every swap the hook takes the fee on the ETH side. Before the swap when ETH is the amount you typed, after it when ETH is what comes out. The fee is high at launch and falls to the steady fee.
3. Split. The protocol share goes aside for the $PRYSM vault. The rest goes to up to three cuts and a burn pot, exactly as your rules say.
4. Settle. Cuts are claimed in ETH. The burn pot is spent buying the token from its own pool and burning it, by anyone, for a bounty. Nothing needs a keeper.

The protocol share is set per pool at launch (max 30%, default 20%) and cannot change for that pool afterwards.

• Withdraw the pool's liquidity. The launchpad holds the only position and has no function to remove it.
• Add other liquidity. The hook refuses any LP except the launchpad.
• Mint more tokens, blacklist, or tax transfers. The token is a plain ERC-20 with no owner.
• Edit a pool's rules after launch, including the owner.

The contracts are in contracts/src. PrysmHook is one file: fork it, change _feeBps or _accrue, deploy it with the bundled HookFactory (it mines an address with the right v4 permission bits) and point a launchpad at it.

cd contracts
forge test
forge script script/Deploy.s.sol --rpc-url robinhood_testnet --broadcast

Uniswap v4 PoolManager on Robinhood Chain mainnet: 0x8366a39cc670b4001a1121b8f6a443a643e40951