Roadmap (design)
Hook marketplace
Anyone can write an on-chain 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 AttestationsThis 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 royaltyHow a hook earns trust#
| Stage | What it means |
|---|---|
| Source published | The program's source is public and the deployed bytecode matches it. No closed-source hook is listed, ever. |
| Bounded by review | A hook declares the accounts it touches and the maximum share of fees it can take. A hook that asks for more than its category allows is refused. |
| Immutable or declared | Either the program is non-upgradeable, or its upgrade authority is shown on every token that uses it. |
| Audited for the risky tier | Hooks that can block transfers or move value need an audit before listing. Hooks that only read and emit do not. |
| Record in public | Usage, volume, revenue and failure rate per hook are published. |