Launchpad (design)

Hook marketplace

Anyone can write a module and be paid when other people's tokens use it.

An open catalogue#

EVERYNTH does not need to invent every behaviour a token might want, and should not try. The catalogue is open: any developer can write a hook, publish it, and be paid when other people's tokens use it.

                   HOOK MARKETPLACE
                          │
        ┌─────────────────┼─────────────────┐
        ↓                 ↓                 ↓
     REWARDS           TRADING           PRIVACY
        │                 │                 │
        ↓                 ↓                 ↓
  Stock rewards        Buyback         Access rules
  SOL rewards          Burn            Transfer rules
  Lottery              LP rewards      Compliance
  Referral             Dynamic fee     Attestations

This is the same shape as the product marketplace that already runs: someone builds something useful, someone else pays to use it, and the platform takes a small cut without standing in the middle of the value.

How a hook developer is paid#

A hook carries a royalty, set by its developer within bounds the protocol enforces. Every token that uses the hook pays it out of the revenue the hook itself generates — never out of the creator's pocket and never out of holders' balances.

a token using a paid hook

  protocol revenue
        ↓
  ┌─────┴──────────────┬──────────────────┐
  ↓                    ↓                  ↓
creator's token    hook developer     protocol treasury
economics          royalty

So the incentive points the right way. A hook that is used by many tokens and generates real volume earns continuously. A hook nobody uses earns nothing, however clever it is.

How a hook earns trust#

A module that runs on every transfer of someone else's token is as dangerous as it is useful. A hook that can fail a transfer can freeze a market; a hook with a bug can lock holders out of their own balances. The catalogue therefore has to be a gate, not a shelf.