Remix royalties

Build from a live hook and your remix records its parent. The original author earns 20% of every royalty the remix earns.

The split

Of every royalty a remix earns: 60% to the remix author, 20% to the author of the hook it was built from, 20% to the $V4M burn reserve. On an 8 bps royalty that is 4.8 bps, 1.6 bps and 1.6 bps of each swap's output. The burn share and the 7 days of vesting are the same as for every hook.

How it is wired

Open a hook in Storefronts and pick Start from this hook. When you list it, the build flow calls the RemixRoyalties registry instead of Storefronts. The registry deploys a small split contract for your remix and lists the hook through it, so Storefronts and the royalty ledger see the split contract as the author. Anyone can call claim(currency) on it: it claims the vested royalties from the ledger and pays 25% of them to the parent's author (20% of the royalty) and 75% to you (60%). You keep the author actions through it: set the royalty, unstake, withdraw the stake, hand the remix to another address. Stakes, failed runs and exploit repayments work as for any hook. Nothing changed in the deployed hook stack or ledger.

The remix tree

Each hook page shows Remixed from and Remixes. A remix of a remix pays its own parent; the line is shown on the page. The tree is read from the registry's Remixed events, at /api/remix?hook=<id>, the MCP tool remix_tree and the SDK method remixTree().

First remix

Hook #9, Large Swap Fee, two tiers, is a remix of hook #5, Large Swap Fee: a swap at or above half the size threshold pays half the large fee, so the fee steps up with size. It is listed with an 8 bps royalty and passed its security check (Safe, 1,000 swaps, 0 failed).