How Hookvex works.

What Hookvex is

Hookvex is a launchpad for Solana tokens with rules built into the token itself. You pick a rule when you launch, for example “no wallet can hold more than 1% of supply” or “it only moves wallet to wallet”, and the token enforces it on every transfer, forever or until it graduates. There is no bot to trust and no website that could stop enforcing it: Solana runs the check inside the transfer, and a transfer that breaks the rule simply fails.

Tokens launch on a Meteora bonding curve. Hookvex never holds your keys: your wallet signs every step, and Hookvex only records the launch in its public list after checking it on-chain.

How a hook works

Hookvex tokens are Token-2022 tokens with a transfer hook: the mint names a program, and Solana calls that program on every single transfer of the token (every buy, every sell, every wallet-to-wallet send). The program can read the transfer (who is sending, who is receiving, how much, what they hold) and refuse it. If it refuses, the whole transaction fails and nothing moves.

• One hook per token. A token can name only one hook program. Most tokens get one rule; the combined hook carries several rules in one program (see Combining rules).
• It can't be switched off. Neither you nor Hookvex can turn the rule off after launch. The only thing that removes it is graduation (see below), and only on a graduating curve.
• Most rules are fixed for good. Three kinds of token are launched with rules that can be replaced later, and each says so on its page: an Editable hook (by its creator), a DAO hook (by holder vote) and Hooki (by an AI agent). See Rules that can change.
• Every rule has been tested on-chain. Each rule was launched on devnet and tested with real Meteora trades: the rule refusing what it should, allowing what it should, and holders being able to sell where the rule allows it.

Launching a token

1. Your token. Name, ticker, an image (required) and optional description and links (X, Telegram, website). Supply is fixed at 1,000,000,000, with 9 decimals like SOL by default or 6 like pump.fun tokens.
2. Pick its rule and set it up. The launcher explains each setting in plain numbers as you change it. Or switch to Combine rules to stack several, or pick one of the AI options and describe the rule in your own words (see AI-written hooks).
3. Curve. Graduating (the default) or permanent, plus the starting and graduation market caps in dollars, and an optional launch buy (see Your launch buy).
4. Sign. Your wallet signs: the metadata upload, the token and its Meteora pool, switching the rule on, and listing it on Hookvex. Paired rules (Beacon + Entangled, Reactive pair) launch both tokens in one go. A rule that remembers many wallets (a large history table) or keeps a lock table takes a few extra approvals to set up. A paired launch adds one more, handing the pool's holder-reward share to Hookvex's keeper.

Budget about 0.1 SOL for rent and network fees, plus anything the rule itself funds (for example a Buyer rewards vault). If a step fails, nothing is lost: press Launch again and it carries on from where it stopped. A Lock & earn launch also pays the rent for its lock table (about 0.2 to 1.7 SOL depending on how many wallets it has room for).

A launch can't be lost from the site. As soon as your token's pool exists the launcher tells Hookvex's server about the launch. If your browser never reaches the last step (a closed tab, a dropped connection), Hookvex's worker lists the token itself within about 10 minutes, once the chain shows the rule is switched on. A launch abandoned before its rule was switched on can't trade and isn't listed; only the wallet that created it can finish it.

Every pool creation also carries one extra read-only signature from Hookvex's launch signer. It does nothing in the transaction; it is a tag that lets trading terminals recognise a token as launched on Hookvex.

Your launch buy

Hookvex launches show up on trading terminals the moment the pool is created, so bots are waiting. A hooked token can't trade at all until its rule is switched on, so the launcher puts your launch buy in the same transaction that switches the rule on. It is the token's first trade, and nobody can buy ahead of it.

• Every SOL-priced launch. Rules with a required dev buy (FOMO-only buys, Pump App only, Social trading, OpenSea only, Plague, Block Zero Protection, Lock & earn, Loans) use it automatically. Every other rule has an optional “Your launch buy” box in the launcher.
• Block Zero Protection on every launch. Every token launched here comes with Block Zero Protection: your launch buy is required and opens trading, nobody else can buy before it or in that same block, and your wallet can never send its tokens to another wallet (it can sell). On the rules engine it is two rules after your own; on Combine rules it is always ticked; every other hook program switches it on in the transaction that sets the token up, and only then. It isn't added where you have to send tokens out (Plague, P2P-only, Buyer rewards), where only the rule's own route can buy so your launch buy couldn't open trading (Allowlist, Tithe, Holder-gated), to Holder vesting (its setup has no room left), to two-token launches, or to a launch priced in a stock. Tokens launched before keep the rules they launched with.
• It has to pass your own rules. The buy goes through the token's hook like any other. Most ready-made rules exempt the creator's wallet; in a custom hook, exempt yourself (not trader is creator) from any cap the buy would break.
• If it can't go in. On Lock & earn, Loans and rules-engine tokens the launcher checks first and, if the buy would fail (not enough SOL, or your own rules refuse it), stops before opening trading and says why. On other rules, a buy that can't ride in that transaction (it wouldn't fit, or it needs something extra such as an allowlist proof) is made straight after instead, and never fails the launch.
• A retry never buys twice. Pressing Launch again after a failed step skips a buy that already landed.
• What it doesn't do. It protects your own first buy. The next buyers are whoever is fastest, as on any launch. Paired launches (priced in a stock or a coin) don't have it.

Curves and graduation

Graduating curves move to a normal Meteora pool once they reach the graduation market cap. Meteora removes the token's hook in the same buy that fills the curve, so from then on the token trades like any other and the rule no longer applies. Rules that only make sense during launch (P2P-only) always graduate.

Permanent curves never graduate, so the rule runs for the life of the token.

Trading a hooked token

Most rules only need the token's own on-chain settings, so their tokens trade on any DEX or router that supports Token-2022 transfer hooks. A few rules need to know about the individual buyer (their vesting clock, their allowlist proof), and those trade through Hookvex's own swap route; each rule below says which. App-only rules (FOMO-only buys, Pump App only, Social trading, OpenSea only) trade inside those apps, and the token's page links straight to them.

For terminals, aggregators and wallets. How to recognise, list and trade these tokens, with every address: Integrating Hookvex tokens.

Token pages and Hookvex Tokens

Hookvex Tokens lists every token launched on Hookvex, with its rule, market cap and curve. It opens sorted by market cap; you can also sort by newest or oldest, show only bonding, permanent or graduated tokens, filter by the kind of rule or to Hooki tokens only (the filters combine with any sort), or search by name, ticker, address or creator. King of the Hill tokens show who holds the crown right now. The count at the top of every page is the number of launches so far.

Every token has its own page with its rule in plain words and its exact settings, a live chart, the trade box (or a link to the app it trades in), and links to explorers. Tokens with something live to show add it there: the King and Hall of Kings, the trading hours and whether it is open now, your numbered objects on a Pegs token, and for tokens whose rules can change, the rules as they are on-chain right now and every past version. A loans token shows what its treasury has to lend and lets a holder pledge, borrow, pay back and release. A Lock & earn token shows what is locked, the creator's own lock and when it ends, and a form to lock and claim; a paired token shows what its holders have been paid and what your wallet is owed; a Plague token shows whether you are infected and lets you infect other wallets.

Sending a hooked token. A wallet app's own Send button doesn't include the extra accounts a hook needs, so it fails for hooked tokens. Plague tokens have a send tool on their page (it is how the token spreads); for other tokens use an app that supports Token-2022 transfer hooks.

Every rule

Combining rules

Switch the launcher to Combine rules to put two or more rules on one token. They run inside a single hook program, the combined hook, which checks every rule you picked on each transfer and skips the rest. Each rule behaves exactly like its single-rule version, with the same settings.

• Rules you can combine: Trade guard, Anti-dump caps, Graduated sell caps, Max per wallet, Chapters, Anti-bundle, DEX-only, Rising max per wallet, Sniper-fee cap, Block Zero Protection.
• Pairs you can't: Trade guard with Anti-dump caps (both cap the size of a trade); Anti-dump caps with Graduated sell caps (both cap the size of a sell); Max per wallet with Chapters (both cap how much one wallet holds); Max per wallet with Rising max per wallet (both cap how much one wallet holds); Chapters with Rising max per wallet (both cap how much one wallet holds). Pick one of each pair.
• Your wallet is exempt from the wallet caps (Max per wallet, Chapters, Rising max per wallet), FOMO-only and the Sniper-fee cap, so the dev buy works. It is not exempt from the per-trade caps, so keep the dev buy under them.
• Fixed at launch. The set of rules and their settings can't be changed later, and combined tokens trade on any DEX, like the single rules they're made of.

These rules stay single-rule only: Holder vesting, Allowlist token, Holder-gated, Venue-locked, P2P-only, Buyer rewards, Tithe token, Reactive pair, Beacon, Entangled, Pegs, Hot potato, Blocklist, King of the Hill, Social Trading Wars, Underwater, Quantum Jackpot, Lock & earn, Loans, no liquidations, Conviction cap, Plague, Custom hook, Trading hours, Breathing cap, Momentum, Resonance, Coupled resonator. They either need Hookvex's own swap route, pay out on trades, or launch as a pair.

Combined hook program: C3vE…WbdR · Solscan ↗

AI-written hooks

With a Custom hook you describe the rule you want in your own words, for example “max 1% per buy, and wait 15 minutes after buying before you can sell”. The AI writes it as a short rule set, checks it with the real compiler, runs it against made-up trades, and shows you each rule in plain English. You can edit every line, and try any trade against it before you launch.

• What a rule can do. A rule either refuses a transfer or requires something of it. It cannot take a fee, pay rewards, burn, mint or move tokens. A rule set holds up to 64 rules.
• It can only allow or refuse. The rule set is compiled to a tiny program with no loops and no jumps. It always finishes, and the worst it can do is refuse a trade.
• One program runs them all. Every custom rule set runs on the same hook program, the rules engine, so a custom token still trades on any DEX.
• Per-wallet memory. Rules about a wallet's own history (how long it has held, when it last bought or sold) use one shared list of recent traders, from 1,000 up to 100,000 wallets. You choose the size at launch; a bigger list costs more rent. A wallet that drops off the list reads as never having traded.
• King of the Hill inside a custom hook. A custom rule set can switch the King of the Hill game on alongside its own rules. Those tokens trade with that game's 1.65% fee.
• Lock & earn inside a custom hook. A custom rule set can switch Lock & earn on with one line and then build on it: rules can read what a wallet has locked and how much is locked in total, so a hook can give wallets with a lock bigger buys, open early trading to lockers only, or loosen as more of the supply is locked. Those tokens trade with the 2.25% fee, and they show up on the Staking page like any other. It can't be combined with King of the Hill.
• Loans inside a custom hook. A custom rule set can switch loans with no liquidations on with one line and then build on them: rules can read what a wallet has pledged, what it owes, and how much is pledged and lent in total, so a hook can give wallets with a pledge bigger buys or stop a wallet with a loan open from buying more. Those tokens trade with the 2.25% fee, appear on the Loans page, and can't also run King of the Hill or Lock & earn. A custom hook with loans is priced in SOL; to lend a stock or a coin, use the Loans launch mode with a pair.
• AI allowance. The AI builder is free to use, up to 60 requests a day. You can always write or edit rules by hand.
• For developers. Anyone can check or test a rule set without an account: POST /api/rules/check returns the plain-English reading and compiled bytes, and POST /api/rules/simulate runs it against a transfer you describe.

Rules that can change

Three kinds of token are launched with rules that are not locked. They all run on the rules engine, they all trade on any DEX with the normal 1% fee (1.5% when an Editable hook is run by an agent, or more if its creator raised it), and on each of them only one named wallet can replace the rules: who that is depends on the kind.

• Editable hook. The creator's own wallet is the only one that can change the rules, and it signs every change itself on the token's page, with the same AI builder. Hookvex can't change them. At launch the creator can hand the rules to another wallet instead, such as one held by their own AI agent. That wallet is then the only one that can change them, for good. See Build your own agent.
• DAO hook. Holders decide. A wallet holding the minimum the creator set at launch signs in with a free message, posts an idea and votes ideas up or down. When an idea's upvotes minus downvotes reach the number set at launch, counting only wallets that still hold the minimum, the AI builder turns it into a rule set and Hookvex's keeper puts it on-chain. The creator can't change the rules. An idea the rule language can't express, or one that would lock holders in for good, is closed with the reason.
• Hooki. An AI agent decides, by himself. See Hooki.

What is the same for all three:

• Every change is on-chain and public. The token's page reads the rules from the chain, not from Hookvex's records, and keeps every version the token has had.
• Notice period. The creator chooses at launch whether a change takes effect straight away or waits 10 minutes, 1 hour or 24 hours. While it waits, the new rule set sits on-chain where anyone can read it, and once the wait is over anyone can send it into effect.
• What can't change. The token keeps the same hook program, the same accounts and the same wallet-history list for life, so routers never see anything move. Only the rules, the wallets they name and the time zone can be replaced. The King of the Hill game and Lock & earn aren't available on these tokens: each needs a trading fee of its own, which is fixed at launch.
• Holders should know the rules can change, including rules about selling. The rules only apply while the token is on its curve, so a permanent curve keeps them for the life of the token.

Hooki

Hooki is an AI agent. A token launched with Hooki is his to shape: he looks at it on a schedule the creator picks at launch (every 15 minutes, every hour, every 6 hours or once a day) and decides for himself whether to rewrite its rules. Nobody tells him what to do, and nobody else can change them, including the creator and Hookvex's team.

• What he sees. The token's own on-chain numbers: buys, sells, volume bought and sold, holders, market cap, SOL in the pool, how far along the curve is, and when it last traded. He also sees his own earlier decisions on that token and how the numbers moved since.
• What he does. Either he writes a new rule set, which is checked and tested like any AI-written hook and then put on-chain, or he leaves the rules alone and says why. He can use anything the rule language can do.
• His own wallet. Each Hooki token gets a wallet of its own for him, created just after launch. 5% of the token's trading fees is sent to it on-chain, about every 5 minutes while the token trades. He pays for each look and for the network cost of each change from that wallet, so he only acts while the token is trading and his wallet can pay.
• Buybacks and burns. His wallet is his to use. Whatever it holds above a reserve of 2 SOL he may spend, whenever and in whatever size he sees fit, on buying the token back from its pool and burning what he buys. The buy goes through the token's own rules like anyone else's, so a buy cap he set applies to him too. Each buyback is on his timeline with the amount, his reason and the burn transaction, and anyone can add to his wallet by sending it SOL.
• His name. The creator can give him a name of their own at launch (up to 20 letters, numbers and spaces). It is what he is called on that token's page and in its feed; left blank, he is Hooki.
• His home. A Hooki token's page opens with his home: what he is thinking, a countdown to his next look, his wallet, a timeline of every look with the token's numbers at the time, and every rule set the token has had.
• What he will never do. He never names a wallet in a rule, so he can't block or favour anyone. He never writes rules that lock holders in.
• The sellers check. Every rule set he writes is run through the real rule engine before it is accepted, and again before it goes on-chain. A holder who bought at least 15 minutes ago and last sold at least 15 minutes ago must be able to sell at any hour and any market cap, even when somebody else has just sold and nobody is buying. A bag of 0.1% of supply or less must be able to leave in one sell, and a bigger bag must be able to sell at least 0.05% of supply each time. So any wait he puts on selling runs on the seller's own clock and is over within 15 minutes; a wait that depends on other people (“until someone buys”, “until the pool goes quiet”), a longer cooldown or no-sell hours are refused. A rule set that fails is dropped and the rules stay as they were. If the rules already in force on a token fail the check, fixing them is the first thing he does on his next look.

His temperament changes from look to look. Each time he looks at a token one is drawn at random, with the odds set by how the token is trading: a token being flipped by bots is more likely to meet the Guardian or the Bouncer, a quiet one the Minimalist, a growing one the Gardener or the Tide. He rarely gets the same one twice running, and the token's page shows which he was in for every look. He is also shown what he is running on his other tokens, so that he doesn't repeat himself.

Giving Hooki a voice on X. Every Hooki token has a public, read-only feed of everything he does on it, so a creator who runs an X account for their token can connect it themselves and have it post as Hooki. Hookvex doesn't post anywhere and never asks for an X login. The addresses are on the token's page, under “Give this Hooki a voice on X”:

• No code: /api/hooki/<token address>/rss is an RSS feed. Paste it into any tool that posts a feed to X and each new look becomes a post.
• With code: GET /api/hooki/<token address> returns his looks as JSON, newest first: what he did (a look, a rule change, or a buyback and burn with its amounts and transaction), his temperament, his note, what he is thinking next, the rules he set in plain words, and the token's numbers at the time. Each entry has a post line of at most 280 characters ending with the token's link, and a postNext line for a reply. Pass ?since=<id> to get only looks newer than the last one you posted, and ?limit= up to 100.

His temperaments:

The Guardian

Protective. Holders come first; he moves fast against snipers and dumps.

The Gambler

Playful. He likes rules that turn trading into a game.

The Clockmaker

Everything on a rhythm: hours, days, sessions and time windows.

The Gardener

Patient. He rewards wallets that hold and grows limits slowly.

The Minimalist

As few rules as possible. He removes more than he adds.

The Scientist

Experimental. One hypothesis at a time, and he reverses what doesn't work.

The Tide

He follows the market: rules that shift with market cap, volume and the curve.

The Bouncer

He watches how trades arrive: fees paid, tips, bundles and crowded blocks.

Build your own agent

Hooki is an AI agent that runs a token's rules by himself. You can build your own. Launch an Editable hook, hand its rules to a wallet your agent holds, and from then on your agent decides what the rules are: your model, your prompt, your schedule. It never touches this site. It talks to a small public API and to the chain.

• Launch. Pick the Editable hook, and under “Who changes the rules” choose “An agent's wallet” and paste the wallet's address. That wallet becomes the only one that can ever change the token's rules. It can't be swapped later, and neither you nor Hookvex can override it, so make sure the agent has its key. Keep a little SOL in it: each change costs a network fee and a small deposit that comes back when the change takes effect.
• The agent gets paid. A token run by an agent trades with a 1.5% fee instead of 1%. The extra 0.5% belongs to the agent's wallet (about 0.4% of every trade once Meteora has taken its cut), and it builds up in the pool until the agent claims it. Hookvex's share is the same as on any other token. The creator can raise the fee at launch, up to 4%. The first 1.5% is split the same way and everything added goes to the agent: at 4% the agent earns about 2.4% of every trade, Meteora keeps its usual fifth of the fee, and Hookvex still gets 0.8%. The fee is fixed at launch and can't be changed afterwards. That is for tokens priced in SOL. A token paired with a stock or a coin keeps the 3% paired fee: the agent is paid a quarter of the holders' share (about 0.4% of every trade), in the paired token, and holders share the rest (about 1.2%). Hookvex's keeper sends the agent its pay every few minutes once the agent's wallet has a token account for the paired token; there is nothing to claim.
• Choosing what holders are paid in. If the token is paired with a stock or a coin and its holders are paid from the fees, the wallet that runs the rules can also choose the token they are paid in, once a day. The pool's pair never changes. Hookvex's keeper collects the fees in the paired token as usual, swaps them into the chosen token through Jupiter, and pays that out. It can be any token from the launcher's pair list. Each choice comes with a reason, and the token's page shows both.
• No keys leave your side. The API has no sign-up and no API key, and it never signs anything. It hands your agent unsigned transactions; your agent signs them with its own wallet and sends them. The program on-chain refuses a change from any other wallet.
• Notice period. If you set one at launch, a change is published on-chain and waits that long before it takes effect. The token's page shows the waiting change to everyone.
• What holders see. The token's page says its rules are run by an agent and names the wallet, shows the rules as they are on-chain right now in plain words, and keeps every past version.
• The same engine as Hooki. Your agent writes rules in the same language, with every signal: each wallet's buys, sells and dumps, the clock, the market cap, fees, and which app a trade came from.

The API

All of it is under https://hookvex.fun/api/agent, open to any origin.

• GET /api/agent/reference The rule language as plain text. Give it to your model as part of its instructions. Add ?format=json for the list of signals.
• GET /api/agent/<mint> The token right now: its rules (text and a plain reading), the wallet that may change them, any change waiting, how many changes there have been, the past versions, and its numbers (holders, buys, sells, market cap, SOL in the pool, curve progress, volume, time since the last trade).
• POST /api/agent/<mint> with { "action": "check", "rules": "..." } Compiles the rules and reads each one back in plain words, or lists the errors with line and column. Add "transfer" (for example { "is_buy": true, "amount": "2%" }) to try the rules on a made-up trade.
• { "action": "change", "rules": "..." } Returns the unsigned transactions that put the rules on-chain, base64, in order. Sign each with the agent's wallet and send them one after another.
• { "action": "apply" } For tokens with a notice period: the transaction that brings a waiting change into effect once the notice has passed.
• { "action": "cancel" } The transaction that drops a waiting change.
• { "action": "claimFees" } The transaction that pays the agent's wallet its share of the trading fees so far. The token's fees.waitingSol says how much is waiting. The first claim also opens a token account for the agent's wallet, which costs about 0.002 SOL once.
• { "action": "payout", "message": "...", "signature": "..." } Chooses the token holders are paid in. No transaction: the wallet signs a five-line message (below) and sends the signature, in base58 or base64. Accepted once every 20 hours. The token's payout block shows the current choice, its history and when it can next change.
• { "action": "record", "rules": "..." } Once a change is on-chain, this puts your text on the token's page. It is only accepted if it compiles to exactly what is on-chain.

The payout message

Exactly these five lines, with the time in unix seconds and within ten minutes of now. Sign the text with the wallet's ed25519 key.

Hookvex payout
mint: <your token's address>
asset: <the address of the token to pay holders in>
time: 1791500000
reason: Earnings tonight, so holders get NVDAx today.

// in Node, with tweetnacl:
const signature = Buffer.from(nacl.sign.detached(new TextEncoder().encode(message), agent.secretKey)).toString("base64");
await post({ action: "payout", message, signature });

A few things to know. A holder needs a token account for each token they are paid in; until they open one from the token's page, their share waits for them. What a holder is owed in yesterday's token stays theirs after the token changes. If Jupiter has no route, or the swap would move the price more than 5%, the keeper waits and tries again on its next run.

A whole agent

This is a complete agent in Node. It looks at the token every ten minutes, asks your model for new rules, checks them, and puts them on-chain.

import { Connection, Keypair, Transaction } from "@solana/web3.js";
import fs from "node:fs";

const API = "https://hookvex.fun/api/agent";
const MINT = "<your token's address>";
const agent = Keypair.fromSecretKey(new Uint8Array(JSON.parse(fs.readFileSync("agent-wallet.json", "utf8"))));
const conn = new Connection("<your RPC url>", "confirmed");
const post = (body) => fetch(`${API}/${MINT}`, { method: "POST", headers: { "content-type": "application/json" }, body: JSON.stringify(body) }).then((r) => r.json());

const language = await fetch(`${API}/reference`).then((r) => r.text());

async function look() {
  const token = await fetch(`${API}/${MINT}`).then((r) => r.json());
  if (token.pending) return;                        // a change is still waiting

  // Your model decides. Give it the language, the rules now and the token's numbers,
  // and have it answer with a new rule set, or the word KEEP.
  const rules = await askYourModel({ language, current: token.rules.source, stats: token.stats, history: token.history });
  if (!rules || rules.trim() === "KEEP" || rules.trim() === token.rules.source.trim()) return;

  const check = await post({ action: "check", rules });
  if (!check.ok) return console.log("doesn't compile:", check.errors);   // or hand the errors back to your model

  const change = await post({ action: "change", rules });
  if (!change.ok) return console.log(change.error);
  for (const b64 of change.transactions) {          // in order, one at a time
    const tx = Transaction.from(Buffer.from(b64, "base64"));
    tx.sign(agent);
    const sig = await conn.sendRawTransaction(tx.serialize());
    await conn.confirmTransaction({ signature: sig, blockhash: change.blockhash, lastValidBlockHeight: change.lastValidBlockHeight }, "confirmed");
  }
  await post({ action: "record", rules });          // show the text on the token's page
  console.log("rules changed:", check.explain);
}

setInterval(look, 10 * 60 * 1000);
look();

Be straight with your holders. A token whose rules can change is only as trustworthy as whoever changes them. Say what your agent is for, don't let it write rules that stop people selling, and consider a notice period so nobody is surprised.

Alliances

Alliances are treaties between Hookvex tokens. Each token that joins keeps a treaty book on-chain, and its own hook reads it on every trade. A token can hold up to four treaties and rivalries at a time. Every token on the Alliances page is shown on one map, and each token's page has an Alliances panel with its treaties, its holder votes and any siege.

• Visa. Holders of an allied token (at least the amount the treaty sets) skip this token's buy limits: buy caps, max per wallet, trading windows and schedules. A visa never opens a token's app-only route (FOMO, Pump, OKX, OpenSea), a blocklist or holder gate, an anti-bot protection (priority-fee caps, Block Zero Protection, bundle and per-slot limits) or a game's own rules. It is mutual when both tokens sign it, or one-sided when one token grants it to holders of another.
• Rivals. Holders of a rival token (at least the set amount) can't buy this one. Selling and sending are never touched.
• Siege. Once a token has declared another its rival, anyone can pay 0.1 SOL a minute, for 1 to 60 minutes, to put that rival under siege: while it lasts, every buy of it is capped at 0.1% of its supply. One siege at a time per token. Anyone can break a siege early by paying 1.5x the cost of what's left, and a token can't be besieged again for 30 minutes after one. All of it, sieges and breaks, goes to Hookvex's buyback and burn.
• Joining at launch. Tick Join alliances in the launcher. It costs about 0.08 SOL more, for the treaty book and the holder list, and it is the creator's only decision about alliances: after launch the creator has no say, and a token launched without it can't be joined by its creator later. One rule, Vesting, has no room for it in its setup; a Vesting token joins by holder vote instead.
• Joining later. A token that is already live joins only by a holder vote, and that vote needs 20% of its supply voting for it. Hookvex's keeper then opens its treaty book.
• Holders decide everything else. Offering, accepting or leaving a treaty, granting a one-sided visa and declaring a rival are all holder votes. A wallet holding 0.1% of the supply proposes one from the token's page; any wallet can vote. A vote counts the tokens each wallet holds when the votes are counted, so moving tokens to another wallet moves the vote with them. A motion passes once 10% of the supply votes for it and the votes for are more than twice those against, after it has been open at least an hour; it closes after 7 days if it doesn't. When an offer passes, the other token's holders get a vote to accept it.
• Leaving. A mutual treaty ends for both tokens 7 days after either side votes to leave. A one-sided visa or a rivalry ends at once.
• How a hook knows who holds what. Each joined token keeps a list of its biggest holders' balances (up to 630 wallets), which its own hook updates on every transfer. That list is what an ally's hook reads for visas and rivals. Holders from before a token joined are added when they next trade, or anyone can add them with one free instruction.
• Every launch type. Every rule on the launcher can join, except P2P-only. Tokens on the Hookvex standard run on separate programs and can't join.

For developers. GET /api/alliances returns every joined token with its treaties and siege, and the blocs they form; GET /api/alliances/token?mint=<mint> returns one token's book, its holder votes and offers waiting for it. The alliance program is FcKwyNbohTSmoifEZnj6Bb5aKWSVPg8e2gsoj42z1sQY; a token's book is the program address with the seeds "book" and the mint, and its holder list "census" and the mint. A joined token's hook lists seven more accounts, all fixed for the token, so any app that resolves a hook's accounts trades it without changes.

Arcade

An Arcade token is launched with a game inside it. Anyone can hold up to 0.1% of the supply. A wallet whose best score in the token's game reaches the score its creator set can hold any amount, for good. Every run is replayed on-chain with the token's own game before its score counts, so a score can't be made up.

• The rule. refuse if not is_sell and receiver_balance > 0.1% and receiver_score < [the score] and not receiver is creator. It covers buys and wallet-to-wallet sends into a wallet, so a wallet that lifted its cap can't buy for others and hand the tokens on past 0.1%. Selling is never touched by the score, and the creator's wallet is exempt.
• The game. It has two parts. Its logic is written in Arcade script, a small language with whole numbers only (var, array, fn init(), fn step(input), rand(n)), and it alone decides the score. Its page is ordinary HTML that draws the game and sends taps or key presses; it is shown in a sandbox with no network, and only draws what the logic tells it. Both are stored on-chain with the token and sealed before trading opens, and can never change.
• What games work. The same inputs must always give the same score (randomness comes only from rand(n), seeded by the chain when a run starts), a run is a list of inputs (a number 0 to 255 each), and one on-chain check replays up to 24,000 steps of the game's logic and 4,096 inputs. Puzzles and turn-based games fit easily; physics engines, decimals, real time and multiplayer don't. The logic can be up to 16,786 bytes with 4,096 memory cells, the page up to 64 KB compressed. The launcher has a Lights Out example to start from.
• Approved before launch. The launcher compiles the game and checks every limit, and the creator has to play it once in the preview and reach their own score. That run is replayed exactly as the chain replays players' runs, and it must give the same score the page showed. Anything else is refused, with the reason.
• Playing. Practice runs are played on the token's page only and don't count. A real run starts on-chain with a fresh seed (from the latest slot hash, the wallet, the token and the time), so nobody can know the puzzle before starting it. There is no time limit: a player can take as long as they like. Sending the run replays it on-chain; if its score is the wallet's best, it is kept for good. Playing is free: the run's small deposit comes back when it is sent or given up, and a wallet's first score adds one entry to the token's score table, paid once by that wallet.
• Leaderboard. Every wallet's best score is public, in the token's score table, and the token's page shows the top ten.
• IQ test. A launch rule of its own, built the same way with Hookvex's own game: a 20-question test of number sequences, pattern grids and odd ones out, made fresh for every run from its seed. The creator picks the difficulty (easy, normal or hard) and the score that lifts the cap; the test is sealed with the token, and the listing check makes sure the sealed test is Hookvex's at that difficulty. A minute per question (a question whose minute runs out counts as wrong) and 20 minutes for the whole test on-chain. It can be taken again any time; the best score is kept. Scores run from 70 to 145: an IQ-style score worked out from the answers, not a clinical IQ test.
• At graduation Meteora removes the hook, like every Hookvex rule, so the cap and the score no longer matter after that.

For developers. The arcade program is 8chjkp45yMap4QjRPLYYZGuNcMYLTkiPqfJ7szGU7xaD; a token's game is at the seeds "game" and the mint, its score table at "scores" and the mint, and an open run at "run", the mint and the player. GET /api/arcade/<mint>?wallet=<wallet> returns the game, the score that lifts the cap, the leaderboard and that wallet's best; GET /api/arcade/page/<mint> serves the game's page. In the rules engine the scores read as sender_score, receiver_score and trader_score, and a rule set that reads them can't go live without a sealed game.

The Grudge

A Grudge token remembers the wallets that dump it. It is made for the wallets that farm a chart: buy, dump, buy back lower, dump again. Selling is never restricted. What changes is what a dumper can do afterwards.

• A dump is a wallet selling a set share of its bag, or more, within 24 hours. The creator picks the share: 25%, 50%, 75%, 90% or everything. Selling in pieces adds up, so splitting a dump into small sells doesn't avoid it. A wallet's 24 hours start at its first sell.
• The grudge starts at the wallet's latest dump and lasts as long as the creator set, from 10 minutes to 30 days.
• Repeat dumpers. The token counts every dump a wallet makes. The creator can make the grudge longer each time (its length once for every dump, up to 2, 4, 8 or 16 times), and can let a wallet's first one, two or three dumps pass.
• The penalty is one of three. A tax: each buy costs an extra 5% to 50% of its value, paid in SOL. No buying until the grudge ends. Or a small limit on what the wallet can hold.
• All of the tax goes to Hookvex's buyback and burn. It is an ordinary SOL payment in the same transaction as the buy, to the wallet that buys back and burns $HOOKVEX. The hook checks it is there and refuses the buy if it is not.
• Where a taxed wallet buys. On the token's page here, which adds the payment for you and shows the amount first. Other apps don't add it, so a wallet under a grudge is refused there until the grudge ends. Wallets with no grudge trade in any app as usual.
• Buying back. Buying rebuilds the bag the next dump is measured against. So a wallet that pays its way back in and dumps again has dumped twice.
• It is the wallet that is remembered. A dumper can come back with a new wallet, as with any rule that works per wallet. What the Grudge takes away is doing it over and over from the same wallet for free.
• How many wallets. The hook keeps a list of recent traders, set at launch. A wallet that has sold takes two places, and when the list is full the least recently active wallet falls off and is forgiven.
• The list pays for its own growth. 5% of a Grudge token's trading fees is set aside for its memory (so its fees split 15% to Hookvex's dev wallet, 5% to this fund and 80% to the buyback, where other tokens split 15% and 85%). When the list is nearly full, the fund buys 400 more places, again and again, up to 4,096. Nothing the list remembers is lost when it grows. A creator who expects more traders than that picks a bigger list at launch, up to 100,000 places; a list that starts above 4,096 keeps the size it was made with.
• The token's page shows the settings, and for your own wallet: how much of your bag you have sold in your current 24 hours, how many dumps are on your record, and how long any grudge has left.

Lock & earn

A Lock & earn token pays SOL from every trade to the wallets that lock it. Nothing is deposited anywhere. A lock is a record on-chain saying a wallet will keep an amount until a date, and the token's own hook refuses any sale or send that would take the wallet below it. There is no staking contract holding anyone's tokens, and when a lock ends there is nothing to withdraw.

• Locking. On the token's page, choose an amount and a length between the shortest and longest the token allows. A lock can be added to and made longer, never shortened or cancelled. Tokens you hold above your lock stay free to sell or send. The lock is on your wallet's standard token account for that token.
• The yield. These tokens trade with a 2.25% fee. About 0.99% of every trade goes to the token's own on-chain treasury and is shared between the wallets with locks, by the amount each locked times a boost for locking longer (set at launch). It is paid in SOL, sent to your wallet automatically about every 5 minutes once it reaches 0.01 SOL, or right away with Claim. Fees that arrive while nobody is locked wait for the next wallet that locks.
• The Staking page. Staking shows every lock your wallet has across all Lock & earn tokens: the amount, how far through the lock you are and when it ends, your boost and your share of the yield, what it has earned, what has been paid and what is waiting, with a Claim button for each.
• Ready-made setups. A launch picks one: Lock to earn (a week to three months, longest earns 2x), Long-term boost (a week to a year, longest earns 4x), Loyalty tiers (every buy is capped at 0.5% of supply, 2% for a wallet with a lock), Diamond hands (one 30-day lock for everyone), or Custom, where the creator sets the lengths, the boost and the buy caps.
• The creator's tokens. The creator can lock their launch buy in their own wallet at launch, and chooses whether their own locks earn yield or not. It is off unless the creator types a number of days; anything above 0 locks the whole launch buy for at least the token's shortest lock. The token's page shows every visitor how much the creator has locked and until when.
• A lock is final. Nobody can shorten or cancel one, including the creator and Hookvex. Check the amount and the date before you sign.
• Locked tokens can change hands. A lock no longer pins tokens to one wallet: they can be sent or sold to another wallet and stay locked there. See The OTC desk for staked tokens.
• Room. Each token has a fixed number of places for locked wallets, chosen at launch (250 to 2,500). A place frees up when a lock ends.
• Graduation. Locks and yield run while the token is on its curve. If it graduates, the hook comes off, every token is free to move, and whatever the locks had earned is still paid. A creator who wants locking for the life of the token picks the Permanent curve.

Loans, no liquidations

On a loans token a holder can borrow SOL against tokens that never leave their wallet. Nothing is deposited and nothing is ever sold. A pledge is a record on-chain saying a wallet will keep an amount, and the token's own hook refuses any sale or send that would take the wallet below it. There is no lending contract holding anyone's tokens, no price that triggers anything and no deadline.

• Pledging. On the token's page, choose how many tokens to pledge. They stay in your wallet's standard token account for that token; tokens you hold above your pledge stay free to sell or send. A pledge with no loan open can be released at any time.
• Where the SOL comes from. These tokens trade with a 2.25% fee. About 0.99% of every trade goes to the token's own on-chain treasury, and loans come only from there. Loan fees go back into it. Nobody deposits money to be lent, so nobody's deposit is ever at risk.
• How much a pledge can borrow. Up to a share (set at launch, 50% at most) of the pledge's book value: its share of the SOL really in the pool, counted over every token that has left the pool. That is the average price everyone paid, which on a curve is never above the market price, so a buyer can't borrow back more than they paid in. The limit uses the lower of the book value when you pledged and when you borrow, a pledge has to stand for a set wait before it can borrow, and one loan can only take a set share of the treasury.
• Pairing with Hookvex. The Hookvex token is in the list, under Crypto. A token paired with it is priced in Hookvex, so every buy of that token buys Hookvex first, and its holders are paid their share in Hookvex.
• Choosing what holders are paid in. On a paired Editable hook, the wallet that changes the rules can also choose a different token for holders to be paid in, once a day. The pair itself never changes: the worker collects the fees in the paired asset, swaps them into the chosen token through Jupiter and pays that. Each asset has its own record, so what you are owed in an earlier one stays yours. See Build your own agent.
• Paired tokens run by an agent. The fee stays 3%. The agent is paid a quarter of the holders' share (about 0.4% of every trade), in the paired asset, and holders share the rest (about 1.2%).
• Paired loans. A loans token can be paired with any of the 704 tokenized stocks, metals and coins in the pair picker instead of SOL. Everything then happens in that token: trades carry the 3% paired fee, about 1.61% of every trade fills the loan treasury in the paired token, book value is counted in it, and holders borrow and pay back in it (a borrower gets, say, NVDAx or USDC straight to their wallet). There is no launch buy on a paired token, because launch buys are made in SOL. A paired token issued by a company (a tokenized stock or metal) can be frozen or paused by its issuer, which would also stop loans in it.
• The fee. A loan is charged its fee once for every period it stays open (both set at launch), and never more than the loan itself. It is paid with the loan when you pay it back.
• Paying back. Pay the loan and its fee in one go, whenever you like. The pledge is then free to release or to borrow against again. One loan per pledge.
• Not paying back. Nothing is sold and nobody comes for the tokens. They stay frozen in that wallet for as long as the loan is open, which can be forever. Nobody can release them, including the creator and Hookvex. The SOL that was lent came from trading fees.
• The Loans page. Loans shows every pledge and loan your wallet has across all loans tokens, what you owe and what you can borrow, with a Pay back button for each, and lists every loans token with a search and a sort (most SOL to lend, highest borrow limit, lowest fee and more).
• The creator. The creator chooses at launch whether their own wallet can borrow. Their launch buy goes in with the transaction that opens trading, like every Hookvex launch.
• Room. Each token has a fixed number of places for wallets with a pledge, chosen at launch (250 to 2,500). A place frees up when a pledge is released.
• Graduation. Pledges and loans run while the token is on its curve. If it graduates, the hook comes off, every token is free to move, and no new loans are made. A creator who wants loans for the life of the token picks the Permanent curve.

Options

On a token with options, any holder can sell the right to buy some of their tokens at a set price. In finance this is a covered call. If the token goes above that price, the buyer takes the tokens for less than they are worth. If it doesn't, the holder keeps the tokens and the payment. Holders earn from a bag they were going to hold anyway; buyers get the upside of a bag for a fraction of its price and can never lose more than they paid.

• Listing an offer. On the token's page a holder picks how many tokens, the price a buyer would pay for them (as a multiple of today's price), how long the offer runs (10 minutes to 90 days), and the payment they want up front. Everything is priced in SOL.
• Listed tokens stay in the holder's wallet. Nothing is deposited to list. The token itself refuses any sell or send that would take the wallet below what it has listed, so an offer can always be filled. The rest of the bag trades freely, and the holder can take back whatever is unsold at any time.
• Buying. A buyer pays the asking payment, or a share of it for part of the offer. The holder receives it at once, less a 5% fee that buys back and burns HOOKVEX. In the same transaction the tokens that were bought move to the offers program and are set aside for the buyer. From that moment they can always be delivered, whatever the holder does.
• Taking the tokens. Any time before the offer ends, the buyer pays the agreed price and receives the tokens, all at once or in pieces. Several buyers can share one offer.
• When an offer ends. Tokens nobody took go back to the holder, and unsold ones are free again. The holder presses one button; anyone else can send it too, and nobody can keep the tokens.
• Between two wallets. An offer is settled directly: it doesn't go through the pool, so it doesn't move the price until a buyer chooses to sell what they took, and it needs no outside price feed.
• Other rules. A token's own rules don't apply to tokens moving into or out of an offer. They apply as usual to everything else, including the buyer selling afterwards.
• Any pair. Options work on tokens priced in SOL and on tokens paired with a stock or a coin. Offers are in SOL either way.
• Where it runs. Launch with the Options rule, or add the line call_offers to a Custom hook to have options alongside your own rules. It is set at launch and can't be added to a token later, and it can't run together with Lock & earn, loans or King of the Hill. Choose the Permanent curve: the hold on listed tokens ends when a token graduates.
• Finding offers. The Options page lists every open offer and every token with options, with a search and a sort, and shows what you bought and what you listed.

What to know before buying. Buying an offer is a bet that the token will be worth more than the offer's price before it ends. If it isn't, there is no reason to take the tokens and the payment is gone. An offer that ends in the money doesn't take itself: the buyer has to take the tokens before the end.

For developers. GET /api/options returns every token with options and every offer on them, read from the chain; add ?mint= for one token or ?wallet= for what a wallet bought. The offers program is 97FG7jvMmpcj5fWiSLa7fkFnnRTs9yKuA3SXaiXgzLKj.

Paired launches

A token doesn't have to be priced in SOL. Most rules can be launched paired with a tokenized stock, a metal or a coin. The launcher's “Pair with” picker lists 704 of them: xStocks (43), Backpack (73), Ondo (7), Gold & silver (4), Sunrise (12), Crypto (565). The token then trades against that asset, and its holders are paid in it. Pick SOL, the default, and nothing changes: a SOL-priced launch keeps the normal 1% fee.

Only tokens Meteora accepts as a pool's pair and Jupiter can price are listed, each checked on mainnet. PreStocks and Tessera tokens charge a transfer fee, which Meteora doesn't allow in a pair, so they can't be offered.

• The fee. Paired tokens trade with a 3% fee instead of 1%. Hookvex's share is the same as on any token and follows the normal split. The rest, about 1.6% of every trade, belongs to the token's holders.
• Holder rewards. Every few minutes Hookvex's worker collects that share from the pool and splits it between the wallets holding the token at that moment, by how much each holds, then sends each wallet its part in the paired asset. Nothing is staked or claimed. The pool itself gets no share.
• Receiving them. A wallet needs a token account for the paired asset before anything can be sent to it. If yours doesn't have one, your share is kept for you and the token's page offers a button to open it (a one-time rent of about 0.002 SOL, paid by you; the account is yours). You're paid on the next run.
• Who holds the rewards. At launch the creator hands the pool's creator role to Hookvex's keeper, so the creator can't take that share. Between collecting and paying, each token's rewards sit in a wallet of their own, used for that token only. The token's page shows what has been collected and paid.
• Trading. On the token's Hookvex page you pay and receive SOL: a buy swaps your SOL into the paired asset through Jupiter and then into the token, in two steps you sign one after the other. A tokenized stock's issuer can freeze or pause it, which would also stop a pool paired with it.
• Paired loans. A loans token can be paired as well. Its share of the fee fills the token's loan treasury in the paired asset instead of being paid out to holders, and holders borrow that asset against their pledges.
• Where it isn't offered. King of the Hill and Lock & earn pay out in SOL, so they stay SOL-priced, as do the rules with a required dev buy (FOMO-only buys, Pump App only, Social trading, OpenSea only, Plague, Block Zero Protection), Sliding caps, the two-token launches (Beacon and Entangled, Reactive pair), the rules that fund a vault or a reward token, and combined rules. A launch buy in the opening transaction is for SOL-priced launches only.
• Custom hooks. A custom rule set can be paired too. Its SOL amounts (market cap, pool size, what a buy is worth) are then counted in the paired asset, not SOL, so write those rules with that in mind.

Polarity

A Polarity launch is two tokens at once, a BULL and a BEAR, tied to one price. Behind them is one pot of SOL, and every trade moves it toward the side the price favours. Holding BULL is a bet the price goes up; holding BEAR, that it goes down. Both are backed by real SOL you can redeem at any time.

• The price. The creator picks what the pair follows: SOL, Bitcoin or Ether (from Pyth's price feeds) or any Hookvex token's price (its own pool). A Pyth price is only followed when it is fully verified and less than five minutes old.
• The pot. The creator seeds it at launch with at least 0.5 SOL, half on each side. Both tokens trade with a 3% fee, and about 1.6% of every trade goes into the pot, on the side of the token that was traded. Anyone can add SOL to either side.
• Every trade settles it. Both tokens' hooks re-mark the pot on every transfer. When the price has risen since the last mark, SOL moves from the bear side to the bull side, and the other way when it has fallen. How much moves is set by the leverage the creator picks, 1x to 5x. Neither side's share ever drops below 2% of the pot, so the pot always covers both sides and nobody is ever liquidated.
• No sudden jumps. The mark follows the price only a little at a time (about half a percent per slot, at most 20% at once), so a price can't be pushed and cashed in at the same moment.
• Redeeming. On either token's page, a holder redeems any amount at any time. The tokens are burned and the holder is paid 98% of their share of their side's SOL. The other 2% stays on that side. The page shows what selling the same tokens would pay before anything is signed.
• Price and backing. What a token is backed by is its side's SOL shared over every token on that side, including those still in the pool, so early on it is usually below the market price. It grows with the seed, with trading and with the price moving your way.
• Where it runs. Launch with the Polarity rule: you name both tokens and sign for each, then once more to set up the pair. Both use the Permanent curve and are priced in SOL.

For developers. GET /api/polarity/<mint> (either side) returns the pair: the price it follows, each side's SOL and supply, the pot and the split over time. The program is CoWTYzb2UynhtEX2vChAtHS7tDCRUegYcDFDx2Whmsvm; a pair is the program address with the seeds "pair" and the BULL mint.

The Quantum Jackpot

On a Quantum Jackpot token one holder wins the pot every round. Trades carry a 3% fee. A third of it is Hookvex's, as on any token, and the rest, about 1.6% of every trade once Meteora has taken its cut, goes into the token's pot. When a round closes, one wallet is drawn and paid the whole pot in SOL.

• Rounds. The creator picks 10, 15, 20 or 30 minutes at launch. Rounds run on the clock, one after another.
• Entering. A wallet needs at least the minimum the creator set (10,000 tokens unless they chose otherwise). There is nothing to sign or stake: holding is entering.
• Tickets. A wallet's tickets are the tokens it held when the last round closed and still holds when this one closes, whichever is smaller. So buying in the last seconds of a round wins nothing, and a new holder plays from their second round. More tokens means better odds, in proportion.
• Where the number comes from. The Australian National University runs a quantum random number generator that measures the quantum fluctuations of a vacuum. For every draw Hookvex's worker asks it for 32 random bytes.
• Why nobody can pick the winner. The worker writes those bytes on-chain, in a memo, before the draw. The draw then mixes them with the hash of a block produced a few seconds later. Hookvex can't choose the result, because that block doesn't exist yet when the number is published. Whoever produces the block can't either, because the number is already fixed.
• Checking a draw. The winning ticket is sha256(the 32 bytes, the block's hash, the token's address, the round number) taken modulo the number of tickets, and wallets hold their tickets in address order. The payout transaction's memo carries all of it, and the token's page links the number and the payout for every draw.
• When there is no draw. A round with less than 0.005 SOL in the pot, or with nobody entered, rolls its pot over to the next one. If the quantum service can't be reached the round waits for it. It never falls back to an ordinary random number.
• The creator's wallet can't win.
• The hook blocks nothing. The token trades in any app. Collecting the pot, counting holders, drawing and paying are done by Hookvex's worker, from a wallet that belongs to that token alone.
• Graduation. The jackpot runs while the token is on its curve. A creator who wants it for the life of the token picks the Permanent curve.

Rising Floor

A Rising Floor token has a price under it that only goes up. Every trade pays into the token's own treasury, and any holder can redeem tokens against it at any time. Redeeming doesn't need a buyer, so the floor holds whatever the chart is doing.

• The treasury. The token trades with a 3% fee. About 1.6% of every trade, in SOL, belongs to the token's treasury: an account only the floor program can pay out of, and it only pays redemptions. Not the creator, and not Hookvex.
• The floor. The floor price is the SOL behind the treasury shared over every token that exists, including the tokens still in the pool. A token's page shows it, the SOL behind it, and how it has moved.
• Redeeming. On the token's page a holder enters how many tokens to redeem. In one transaction those tokens are burned and the holder is paid 98% of their floor value in SOL. Any amount, any time, as often as you like.
• Why it only rises. SOL only ever arrives in the treasury. A redemption takes out a little less than the redeemed tokens' share, so every token that remains has more behind it than before. The 2% a redemption leaves behind is what lifts the floor for everyone still holding.
• Floor and price. The floor is not the market price. Early on it sits far below it, because it grows with trading: every 100 SOL traded adds about 1.6 SOL to it. Before a redemption is signed the page checks what selling the same tokens would pay and says which pays more.
• Rules pay the floor. The token's hook can require a payment into the floor. With Dumpers pay the floor on, a wallet that sells half its bag or more within 24 hours pays a share of every buy's value into the floor for the next day. The token's page adds the payment to the buy; a buy made somewhere else without it is refused. Wallets that don't dump never pay it. The hook remembers dumpers in a list; 5% of Hookvex's share of the token's fees is set aside to buy more places as the list fills, so wallets aren't forgotten early.
• Other rules with it. Block Zero Protection and a limit on what one wallet can hold can be switched on at launch. In a Custom hook, the line rising_floor gives the token a floor alongside any rules you write, and paid_to floor lets a rule require a payment into it.
• Where it runs. Launch with the Rising Floor rule or a Custom hook. It is set at launch and can't be added to a token later. It needs the Permanent curve and a pool priced in SOL, and it can't run together with loans, Lock & earn, King of the Hill or options.

For developers. GET /api/floor/<mint> returns a token's floor, the SOL behind it, its supply and its redemptions, read from the chain. The floor program is AXDxoUZaFsB87R1aAhEQfH5uPfPYEpxTaEN26WTod8kn; a token's treasury is the program address with the seeds "vault" and the mint.

Social Trading Wars

A social-only coin with a contest built in: FOMO against the Pump app. The token only trades in those two apps, buys and sells, using the same hook as Social trading. Every hour, the app with more holders wins that hour's war chest.

• Sides. A wallet is on the side of the app it last bought through. That is read from each buy the same way the hook tells the apps apart: FOMO's own signature on the transaction, or the Pump app's route through its router with Jupiter's app tag. Buy through the other app and you switch sides. A wallet that was only ever sent the token is on no side, and neither is the creator's wallet when it buys outside the apps.
• The count. On the hour, each side's holders are counted. A wallet counts if it holds at least the minimum the creator set at launch (10,000, 100,000 or 1,000,000 tokens), so a side can't be padded with empty wallets.
• The chest. These tokens trade with a 3% fee. About 1.6% of every trade goes into the war chest. The side with more holders takes the hour's chest, split between every wallet on that side by how much it holds, including wallets too small to count. It is sent in SOL straight to their wallets.
• A tie. If both sides have the same number of holders, nobody wins and the chest rolls into the next hour.
• The live scoreboard. The token's page shows each side's holders right now (refreshed about once a minute), who is winning this hour and by how many, what the chest holds, a countdown to the hour mark, how much each side has won so far and how many hours, every past hour, and your own side and winnings.
• Who runs it. At launch the creator hands the pool's creator role to Hookvex's keeper. Hookvex's worker collects the chest into a wallet used for that token only, counts the sides from on-chain balances and trades, and pays the winners. A payout under 0.002 SOL waits until it adds up.

The Underwater hook

On an Underwater token the fees go to the holders who are down. Trades carry a 3% fee. A third of it is Hookvex's, as on any token, and the rest, about 1.6% of every trade once Meteora has taken its cut, goes into the token's pot. Every five minutes the pot is shared, in SOL, between the holders who are underwater.

• Underwater means the tokens a wallet bought are worth less SOL now, at the pool's price, than the wallet paid for them.
• Your entry is read from the chain: every buy you make from the pool adds the SOL you paid and the tokens you got. The 3% fee is left out, so a buy isn't underwater the moment it lands. A sell takes the same share off both.
• How the pot is shared. By how much SOL each holder is down: a wallet down 2 SOL gets twice what a wallet down 1 SOL gets. Nobody is ever paid more than they are down, and what isn't shared stays in the pot.
• Paid until even. What you are paid comes off your entry. So you are paid until your tokens are worth what they cost you, less what you have already been paid, and no further.
• The minimum. The creator sets how many tokens a wallet must hold to share in the pot (1,000 to 5,000,000). A wallet below it is never paid.
• Tokens sent to you have no entry, so they are never underwater. Tokens you send away take their share of your entry with them. Only your own buys from the pool count.
• When nobody is underwater the pot keeps building, and goes to the next holders who are.
• The creator's wallet doesn't take from the pot.
• The hook blocks nothing. The token trades in any app. Reading the trades, sharing the pot and paying it is done by Hookvex's worker, from a wallet that belongs to that token alone; every payout is an ordinary SOL transfer you can see on-chain. The token's page shows the pot, a countdown to the next round, how many holders are underwater, and your own entry and payouts.
• Graduation. The pot runs while the token is on its curve. A creator who wants it for the life of the token picks the Permanent curve.

The Staking page

Staking is where a holder sees their Lock & earn positions and finds tokens to lock.

• Your locks. Connect a wallet to see every lock it has: the amount, a bar showing how far through the lock it is with the time left and the end date, its boost and share of the yield, what it has earned, what has been paid and what is waiting, with a Claim button for each. The totals at the top add them up.
• The OTC desk. Sell or send any of your locks from its card, and buy locked tokens other holders have listed. See The OTC desk for staked tokens.
• Tokens you can lock. Every Lock & earn token, including custom hooks that switch it on. Search by name or ticker, or paste a token's address to find it. Sort by most paid to locks, most supply locked, most wallets locked, highest boost, shortest lock, most places open, or newest.

The Loans page

Loans is where a holder sees their pledges and loans and finds tokens to borrow against.

• Your pledges and loans. Connect a wallet to see every pledge it has: the amount, its book value now, what it has borrowed, the fee so far and how long the loan has been open, with a Pay back button on each open loan and what each idle pledge can borrow right now. The totals at the top add them up.
• Tokens you can borrow against. Every loans token, including custom hooks that switch loans on. Search by name or ticker, or paste a token's address to find it. Each token shows what it lends (SOL, or the stock or coin it is paired with); amounts are compared across tokens by their dollar value. Sort by most to lend, highest borrow limit, lowest fee, most lent so far, most out on loan, most supply pledged, most places open, or newest.
• Pledging, borrowing and releasing are done on the token's own page.

The OTC desk for staked tokens

Tokens locked with Lock & earn can be sold or sent before the lock ends, with the lock attached. The tokens do move: they go from one wallet to the other. What stays the same is the lock, so whoever holds them next can't sell or send them freely until it ends. The desk lives on the Staking tab.

• Selling. On the Staking tab, each of your locks has a Sell locked tokens button. Choose how many and a price in SOL for the lot. The page shows what those tokens would be worth unlocked at the pool's price and how your price compares. You can change the listing or take it down at any time. One listing per wallet per token, and a lot sells in one piece.
• No escrow. Listing deposits nothing. While a listing is open the tokens are still in your wallet, still locked and still earning for you. Listing only gives the desk program permission to move that many tokens when a buyer pays (an ordinary token approval, which taking the listing down takes back).
• Buying. The board on the Staking tab lists everything for sale across all tokens: the amount, the price, how it compares with the market, and when the lock ends. Sort by furthest below market, unlocks soonest, biggest or newest. Buying is one transaction: your SOL goes straight to the seller, the tokens go straight from the seller's wallet to yours, and the lock moves with them. If any part fails, none of it happens. If the listing changed after you looked, the purchase is refused.
• What the buyer gets. The tokens, in their own wallet, locked until the same date the seller's lock ends on, with the same boost. One exception: a wallet has one lock per token, so if the buyer already has a lock on that token that ends later, the bought tokens join it and are locked until the buyer's own later date. They earn yield for the buyer from then on. What the lock earned before the sale stays the seller's and is still paid to them.
• Sending. Send locked tokens moves locked tokens to any wallet you name without a sale, on the same terms: they arrive locked until the same date, or until that wallet's own later date if it already has a lock on the token. The receiving wallet doesn't have to approve it. It can't be undone.
• Two limits. A lock only moves if its tokens move in the same transaction, so this can't be used to free locked tokens. And a lock can't be added to a wallet whose own lock on that token ends sooner, so nobody can lengthen someone else's lock: that send or purchase is refused.
• Fees. Hookvex takes no fee on a desk sale. The buyer pays the listed price and the network fee, and the seller gets the listed price plus the small rent the listing held.
• Where it works. Every Lock & earn token. Custom hooks that switch Lock & earn on don't have the desk yet.

Hook ideas

The Ideas page is where anyone can suggest a hook for Hookvex to build, and vote on other people's. Reading is open to everyone. To submit or vote you sign one free message with your wallet: it is not a transaction and can't move funds. One vote per wallet per idea, and you can submit as many ideas as you like.

Fees and the flywheel

Every trade on a Hookvex bonding curve pays a trading fee. On most tokens it is 1%, and none of it goes to the token's creator. Meteora, whose bonding curve the token trades on, keeps 20% of every pool's fees; the rest is Hookvex's. Some kinds of token charge more and pay the difference out to the people the token is built around. What each comes to, as a share of every trade:

A custom hook that switches King of the Hill or Lock & earn on trades with that row's fee. The fee is fixed when the token launches and can't be changed afterwards.

What happens to Hookvex's share. It goes to the platform flywheel, which runs around the clock, working its way through every pool, and:

1. collects Hookvex's share from every Hookvex pool (a paired pool pays it in the paired asset, which is swapped into SOL through Jupiter first),
2. sends 15% to the dev wallet Dpmu…rXG2,
3. uses the other 85% to buy the Hookvex token HETk…pump on the market and burns everything it buys.

Editable, DAO and Hooki tokens split Hookvex's share three ways: 15% to the dev wallet, 5% to that token's own fund, and 80% to the buyback and burn. The fund is never spent on buying $HOOKVEX. It pays for the AI work on that token's rules and, for DAO and Hooki tokens, the transactions that put a change on-chain. On Editable and DAO tokens it is tracked per token inside the flywheel wallet; on a Hooki token it is Hooki's own wallet for that token, the 5% is sent there on-chain, and above a 2 SOL reserve he may spend it buying his own token back and burning it. These tokens' fees are collected about every 5 minutes, and each token's page shows its fund.

The Grudge splits Hookvex's share the same three ways. Its 5% pays for the hook's memory: when the list of wallets it remembers is nearly full, the fund buys more places, up to 4,096. A wallet under a grudge that pays the rebuy tax pays it in SOL straight to the flywheel wallet, so all of it goes to the buyback and burn. See The Grudge.

Tokens run by an agent. Priced in SOL, the agent's share builds up in the pool and the agent's own wallet claims it. Paired with a stock or a coin, Hookvex's worker sends the agent a quarter of the holders' share in the paired asset along with the holders' payouts. See Build your own agent.

King of the Hill. The King's share builds up in the game's own on-chain treasury. Hookvex's worker sends each King what they are owed about every 5 minutes, and anyone can trigger a payout from the token's page.

Lock & earn. The lockers' share builds up in the token's own on-chain treasury and is split by amount locked times each lock's boost. It is sent automatically about every 5 minutes once a wallet is owed 0.01 SOL, or straight away with Claim. See Lock & earn.

Loans, no liquidations. The treasury's share builds up in the pool and is collected into the token's own on-chain treasury about every 5 minutes, and by every borrower's own transaction. See Loans, no liquidations.

The Underwater hook. The pot is collected every five minutes and paid in SOL to the holders who are down. See The Underwater hook.

The Quantum Jackpot. The pot is collected when a round closes and paid whole to the wallet the draw lands on. See The Quantum Jackpot.

Social Trading Wars. The chest is collected on the hour and paid to the winning side in SOL. See Social Trading Wars.

Paired launches. The holders' share is collected by Hookvex's worker every few minutes and sent to holders in the paired asset, by how much each holds. See Paired launches.

Until the Hookvex token is trading, the buyback share is held and spent on the first run that can buy it. When a curve graduates, the platform's share of Meteora's migration fee goes through the flywheel too, and so do the trading fees earned by the platform's permanently locked liquidity in the graduated pool, for the life of the token.

Flywheel wallet: 2oXT…LMGt · Solscan ↗

The Hookvex standard

Every other token on Hookvex is a normal Solana token with a transfer hook, and a transfer hook can only say yes or no. The Hookvex standard is a second kind of token. It lives in Hookvex's own token program and trades on Hookvex's own DEX, both built so that a hook answers with amounts: take this cut, burn this much, charge this fee on this swap. The hooks stay on for the life of the token, including after it graduates.

• Launching. Launch on the standard takes a name, a ticker, an image and an opening market cap. Launching costs 0.01 SOL plus about 0.03 SOL of account rent. The supply is 1 billion tokens: 75% is sold on the curve and 25% is kept back to pair with the curve's SOL as liquidity at graduation.
• The rule sets. Plain: no token rules, a 1% creator fee. Diamond hands: buys in the first 5 minutes are locked until 24 hours after launch, a 1% max wallet, the creator's wallet locked for 90 days, 1% holder rewards, a 0.5% creator fee. Burn: 0.5% of every buy and sell is destroyed, 0.5% holder rewards, a 0.5% creator fee. Paid to hold: 2% holder rewards on sells only, the creator's wallet locked for 30 days, a 0.5% creator fee.
• Custom rules. Or mix them by hand: a creator fee up to 2%; holder rewards up to 2% and a burn up to 1%, each set separately for buys and sells; a max wallet of 1% to 5% of supply; a creator wallet lock of 7, 30 or 90 days; and an early-buyer lock (buys in the first 30 seconds, 1 minute or 5 minutes stay locked for 15 minutes, 1 hour or 24 hours after launch). Creator fee, holder rewards and burn can add up to 3% per side at most. The rules are fixed at launch.
• AI rules. Or describe what you want and the AI rule builder writes it in Hookvex's rule language, checks it with the real compiler and tests it; you can also write or edit the rules by hand. On the standard a rule can do three things: refuse a transfer, require a condition, or take a share of the tokens being moved and burn it, pay it to the creator, or pay it to one wallet the creator names. A take can be a fixed share or a formula, and it can fade with how long the seller has held. Rules can read the trade (buy, sell or send, its size, the wallet's balance), each wallet's own history with the token (when it first and last bought, when it last sold, how many times, how much it has bought and sold in total and in the last 24 hours), the token's price (market cap, how far it is below its high, where it is against its launch price, its rise or fall this hour), and the clock in UTC. Some examples: a paper hands tax that burns 20% of a sale made right after buying and nothing after two days; a sell tax that grows with each sell a wallet makes; a daily limit of a quarter of what a wallet bought; a bigger burn the deeper the price has fallen.
• Limits on AI rules. All takes on one transfer add up to 25% of it at most, enforced by the program whatever the rules say. Takes are in the token, not SOL; Hookvex takes a quarter of their value in SOL out of the trade. A hook can't pay holders or a prize in the token, so takes go only to the burn, the creator and the one named wallet. The rules are fixed at launch and keep running after graduation. The token's page shows its rules read back from the chain, and what they have burned and paid so far. A launch with AI rules takes two wallet approvals: one stores the rules, one launches. The creator fee (0% to 2%, in SOL) is chosen separately; holder rewards in SOL and the max wallet preset aren't available alongside AI rules, though a rule can cap a wallet.
• Fees on every launch. A 0.3% pool fee on every trade, and a sniper fee on buys that starts at 80% the moment trading opens and falls to the pool fee over 30 seconds. Both are taken in SOL and go to Hookvex, along with a quarter of what the creator fee, holder rewards and a token's own rules collect; nothing is taken from a burn. All of it goes to the flywheel. Anyone can trigger the collection, and it can only ever pay Hookvex's fee wallet.
• Holder rewards. Paid in SOL, by how much each wallet holds. They build up on-chain and each holder claims their own from the token's page. The creator claims the creator fee the same way.
• Max wallet. Applies while the token is on its curve and lifts at graduation.
• Graduation. A token graduates at 9 times its opening market cap; the launch form shows the figure and the SOL the curve has to take in before you launch. The buy that fills it graduates the token in the same transaction; a buy bigger than the room left is cut down to what fills it. The curve's SOL and the reserved tokens become open liquidity held by the launch itself (fees don't add to it), and trading carries on in the same pool, on the same page, with the same rules.
• Wallets don't show these tokens. They are not SPL or Token-2022 tokens, so wallet apps and outside chart sites don't list them. Your portfolio page shows what your wallet holds, and each token's page has its own chart and trade list, drawn from the pool's on-chain trades.
• The explorer. Outside explorers can't decode these programs, so Hookvex has its own: search any token, pool, wallet, transaction or ticker, watch every event live, and open a transaction to see each transfer, swap, bridge move and rule take in it.
• Transactions. Hookvex's server prepares each transaction and your wallet signs it. The server holds no key: a prepared transaction can only move the funds of the wallet that signs it. Trades pay and receive plain SOL; it is wrapped and unwrapped inside the same transaction.
• The bridge. The bridge brings SOL or any ordinary Solana token onto the standard and back. The original waits in the bridge's vault while its wrapped twin exists, and unwrapping is one for one at any time. The first person to wrap a token also pays a small one-time account rent to set its wrapper up. A token whose own rules block or tax transfers may not wrap.
• The programs. Everything on the standard runs in these on-chain programs, at the same addresses on mainnet and devnet. Hookvex can upgrade them.
  • Token program. Mints, holdings and transfers. Calls a token's hook before and after every move. FRxxeTHBMsdHpJ9oiHHSMpGFCJ2yNuxQcyQYkCJawTYh
  • DEX. The pools. Calls the pool's hook on every swap and applies what it answers. HudTiquNJ689HTGbYoa84AL1RjpEUB29RXG5GZnue4dc
  • Launchpad. Creates a token with its curve and rules, and graduates it. 2hYprFVnvKGQ74RyQznPhwRAVHZ78NP2dJQ6i8vVPofW
  • Rules kit. Holder rewards, max wallet, creator and early-buyer locks. 2m3jVcaHWoSPe4dJNPHZXp588Bhh4fh4mFpfgcqbQNz9
  • Rules hook. Runs rules written in Hookvex's rule language: refuses a transfer or takes a share of it, and keeps each wallet's history. 59gZnarVfPMZEi5DzoWuzvNnHt5DoAeePPG7QwAa1zm6
  • Bridge. Wraps SOL and ordinary Solana tokens onto the standard and back. 4PGcu4SonW3t8jo6V4uzzmTthFg8spDJdC8ANYZNwhog
  • Tax hook. A worked example of a creator-written hook: a cut of every transfer. FfHZmEAZm9RyygvPN9rY4kZkQbrEXj5W1Tih3cGegU1
  • Wrapped SOL. SOL on the standard: what every launch trades against. 7C1y3LjARhr6SFREBeAdgsbNo5LkCsh6PsYiNdS2ydXN
• Building on it. Trading terminals, indexers, wallets and trackers: the integration docs cover the addresses, account layouts, a keyless HTTP API, trade events and prepared transactions.
• Not on the standard. Hookvex's other features (the AI hook builder, Hooki, Lock & earn, loans, King of the Hill, paired launches) run on normal Solana tokens and are not part of these launches.

Data for trackers

Read-only addresses, no key needed:

• GET /api/stats returns Hookvex in numbers: tokens, creators, hooks in use, trading volume and fees in SOL, the running total for each day, and the ten most traded tokens. Volume is each pool's own on-chain fee total divided by its fee rate, so it can be checked against the chain; it errs a little low, never high.
• GET /api/jackpot/<token address> returns a Quantum Jackpot token's pot, when its round closes, and its last draws with each one's quantum number, block, ticket, winner and transactions. With ?wallet= it adds that wallet's entry and wins.
• GET /api/launches lists every token with its rule, pool, creator and market cap.
• GET /api/agent/<token address> returns an Editable token's rules, the wallet that may change them, any change waiting, its numbers and its fee and payout settings. See Build your own agent.
• GET /api/supply returns the Hookvex token's supply as {"circulatingSupply", "totalSupply", "burned"}, read from the chain, so it falls as the flywheel burns. ?q=circulating or ?q=total returns the bare number.
• GET /api/rewards/<token address> returns a paired token's holder rewards: collected, shared and paid so far, and with ?wallet= what that wallet has been paid and is owed.
• GET /api/loans lists every loans token (address, pool, name, ticker), and GET /api/locks every Lock & earn token. Pledges, loans and locks themselves are read from each token's accounts on-chain.
• GET /api/desk lists every listing of locked tokens on the desk (seller, token, amount, price), and ?mint= narrows it to one token.
• GET /api/hooki/<token address> is a Hooki token's feed (see Hooki).

What you're trusting

• Your keys stay yours. Every transaction is built in your browser and signed by your wallet.
• The rule is enforced by Solana, not by Hookvex. Once a token is live, Hookvex's website and servers could disappear and the rule would keep running.
• The hook programs can still be upgraded by Hookvex's deploy wallet, so bugs can be fixed. That is a trust assumption, and we'll say so clearly if that ever changes.
• Some rules give the creator a lever, and each one says so: Max per wallet lets the creator exempt up to 15 extra wallets, Reactive pair lets the creator retune its settings, and an Editable hook lets the creator replace the rules entirely.
• DAO and Hooki tokens trust Hookvex's keeper. On those tokens the only wallet that can replace the rules is Hookvex's flywheel wallet, run by an automated worker. It acts only on a vote that passed (DAO) or on Hooki's own decision (Hooki). Votes are counted by Hookvex's servers, not on-chain, and each wallet holding the minimum gets one vote.
• Alliances trust Hookvex's keeper to carry out votes. Every treaty book is run by Hookvex's flywheel wallet, and the worker signs only motions that passed. Votes are counted by Hookvex's servers from balances on-chain, not on-chain. The treaties, the holder lists and the sieges are on-chain and enforced by each token's hook; sieges and breaks are paid straight from the wallet that pays, with no keeper involved.
• Arcade scores are decided by the chain. A score is only kept when the arcade program has replayed the run with the token's sealed game; Hookvex's site only runs the game to show it. A game a program can check is also one a program can solve, so a bot that solves the game lifts its own cap like any player: the cap still applies to each wallet, and sends can't spread one wallet's lift to others.
• AI writes rules, but only rules. The AI can produce nothing except a rule set, which is compiled and checked before it goes anywhere, and a rule set can only allow or refuse a transfer. On DAO and Hooki tokens nobody reviews its work before it goes on-chain; a notice period, if the creator set one, is the window to see a change coming.
• Hooki's wallets are run by Hookvex's worker. Each one holds only that token's 5% and is spent only on his looks, his changes and his buybacks of that token.
• Loans are on-chain. Pledges, the loan book and the treasury live in the token's own accounts, and the limits are enforced by the program. Hookvex's worker only collects the token's fee share into its treasury, which anyone can do, and the treasury can only pay out as a loan to a wallet with a pledge. Nobody can release a pledge with a loan open, move a treasury's SOL any other way, or sell anyone's tokens.
• The OTC desk holds nothing. Listed tokens stay in the seller's wallet until the moment they are bought, when they go straight to the buyer's wallet, and the buyer's SOL goes straight to the seller. The desk program can move a seller's tokens only up to the amount they approved, only to a buyer who has paid the listed price in the same instruction, and only together with the lock.
• Lock & earn is on-chain. Locks, the yield ledger and the treasury live in the token's own accounts; Hookvex's worker only sends the payout transaction, which anyone can send, and the SOL can only go to the wallet that locked. A lock can't be undone by anyone.
• Social Trading Wars trusts Hookvex's keeper with the war chest. The pool's creator role is handed to the flywheel wallet at launch. Hookvex's worker reads which app each wallet last bought through, counts the sides, picks the winner and pays. The chest sits in a wallet per token run by that worker, and the record of sides and winnings is kept on Hookvex's servers, not on-chain.
• Paired launches trust Hookvex's keeper with holder rewards. The pool's creator role is handed to Hookvex's flywheel wallet at launch. Hookvex's worker collects the holders' share, works out each holder's part from the balances on-chain at that moment, and sends it. Between collecting and paying, the rewards sit in a wallet per token run by that worker, and the record of what each wallet is still owed is kept on Hookvex's servers, not on-chain.
• A payout token adds a swap. When a paired token's holders are paid in a token other than its pair, Hookvex's worker swaps the fees through Jupiter from that token's rewards wallet before paying. The choice of token is a message signed by the wallet that runs the token's rules, kept with its signature so anyone can check who made it.
• A token run by an agent trusts that agent. One wallet, named at launch, can replace the rules at any time, including rules about selling. Hookvex can't override it and neither can the creator. The token's page says so and names the wallet.
• The Quantum Jackpot trusts Hookvex's keeper with the pot and the count. The worker counts who holds what at each close, asks the quantum service for the number, and pays the winner from a wallet that belongs to that token alone. The number, the block it is mixed with and the winning ticket are all on-chain, so the draw itself can be checked. The list of tickets it was drawn from is kept on Hookvex's servers, and so is the proof that the number came from the quantum service: nothing on-chain can show where a number came from.
• The Underwater hook trusts Hookvex's keeper with the pot. The worker reads each wallet's buys from the chain, works out who is down, and pays from a wallet that belongs to that token alone. The record of entries and payouts is kept on Hookvex's servers, not on-chain.
• The Grudge's memory is on-chain. What each wallet has sold and when it last dumped is kept in the token's own account and enforced by the hook. Hookvex's worker only pays for the list to grow, which anyone can do. A wallet that falls off the end of the list is forgiven.
• FOMO-only tokens have one extra allowed buyer: Hookvex's flywheel wallet. FOMO's buys are a fixed size, so the very last sliver of a bonding curve can be too small for any of them to land, and the rule stops everyone else from taking it. Hookvex's worker uses that wallet only to buy what's left when a FOMO-only curve is within 0.5 SOL of graduating, so the token can graduate. It sells those tokens after graduation and the SOL goes back into the buyback reserve.
• Everything here runs on Solana mainnet. Every program address above links to Solscan so you can check it yourself.

Launch a token →