Field manual

What Triggerpad is

A Solana launchpad where every token launches with rules the chain enforces.

Those rules are called triggers. A trigger is a Token-2022 transfer hook: a program Solana runs on every transfer of the token. Break the rule and the transfer never lands.

No bot watches the chart. No snapshot gets taken after the fact. No website has to keep its word. The chain enforces the rules, so they keep working even if Triggerpad’s site goes dark.

Each token carries up to three triggers. Picking them is called building your loadout: three slots, and every transfer has to clear every trigger loaded. The triggers you pick from are racked in The Armory, the trigger catalog (section 06).

How a trigger works

Solana calls the trigger on every transfer. If it says no, the transaction fails. That’s the whole trick.

Token-2022 is Solana’s newer token program, built for extensions. One extension is the transfer hook: a token names a program, and Token-2022 calls that program on every transfer of the token. Every Triggerpad token names the Triggerpad trigger engine.

Every transfer means every transfer: buys, sells and plain wallet-to-wallet sends. There is no side door.

Refused means reverted

When a trigger says no, the engine returns an error. That error aborts Token-2022’s transfer. On a trade, that aborts Meteora’s swap, which aborts the whole transaction. Nothing moves. We call it shot down (REVERTED). An explorer shows it as a failed transaction.

A trigger checks the result

Token-2022 updates both balances before it calls the hook, so a trigger judges a transfer by its result. Mag Cap, for example, looks at what the receiving wallet holds after the buy, not before. If the result breaks a rule, the revert rolls everything back as if the transfer never happened.

Buy, sell or send

Every curve keeps its unsold tokens in one account, the pool vault. When a token is armed, the engine reads the vault’s address from the Meteora pool and stores it. That one address sorts every transfer.

Curve fees are collected in SOL, not in the token. So while a trigger is armed, nothing but a swap moves tokens out of the vault, and a transfer out of the vault is always a real buy.

Arming a token

Arm a token is the launch flow: four steps, four signatures, about 0.1 SOL.

Your wallet signs every step. Triggerpad never holds a key.

What you sign

Pool and arm share one transaction on purpose: they land together or not at all. There is never a moment when the token trades without its rules. The launch shows up on The Range, the list of every launch, only after Triggerpad’s server has checked it on-chain.

Locked at launch

Your loadout is written once, by the launch itself. Only the pool’s creator can arm it, and only once. After that there are no creator levers: no admin switch, no way to loosen a cap, no way to unload a trigger. The only thing that ever disarms a token is Safety on (section 04).

One footnote, stated up front: the trigger engine’s code can be upgraded by a multisig. Section 08 spells out what that means.

Curves and graduation

Every token launches on a bonding curve. Graduation is Safety on: the trigger disarms.

Tokens launch on a Meteora Dynamic Bonding Curve (DBC). The curve is the market: buyers pay SOL in and take tokens out, sellers do the reverse, and the price moves along the curve.

Meteora’s program creates the token itself. It mints the full supply into the curve’s vault, points the transfer hook at the trigger engine, and keeps the hook’s authority. Not Triggerpad. Not the creator.

Safety on

Graduation happens inside the buy that fills the curve. That buy is still checked by every trigger. Then, in the same transaction, Meteora’s program clears the token’s hook program and then the hook authority. The trigger disarms: that’s Safety on.

Next, anyone can run the migration that moves the token to a Meteora DAMM v2 pool, where it trades like any other token. DAMM v2 accepts it only because the hook is gone: a DAMM v2 pool can’t carry an active hook.

Permanent curves

Meteora has no “never graduate” switch, so a permanent curve is a normal curve with a threshold nobody can reach: 10 billion SOL, about 15 times all the SOL in existence. Early on it prices much like a graduating curve. It just never fills, so the token trades on its curve for life and its triggers never disarm.

Trading

While a token is armed, it trades on Triggerpad. After Safety on, it trades like any other token.

Every token has a Spec sheet, its page on Triggerpad. While the token is armed, trade it there. The trade panel builds Meteora’s hook-aware swap, adds the accounts the trigger engine needs, and hands it to your wallet to sign.

Aggregators

Aggregators like Jupiter don’t route armed curve tokens today. We verified it on mainnet: Jupiter’s quote API returned TOKEN_NOT_TRADABLE for the ten newest hook-enabled curve tokens, while curve tokens without a hook routed fine in the same minute. Jupiter has no route yet for Meteora’s hook-aware curve swap.

After Safety on, the token trades in a regular Meteora DAMM v2 pool, and Jupiter routes it. Permanent tokens never graduate, so they only ever trade on their curve: on Triggerpad, or on any venue that builds the hook-aware swap itself.

Wallet sends

Hook-aware wallets can send armed tokens. They look up the hook’s extra accounts, which follow from the token’s mint alone, and add them to the transfer automatically. The exception is Chambered: a token with it loaded refuses wallet-to-wallet sends until Safety on.

What a miss costs

A transfer that gets shot down costs only the network fee. The whole transaction reverts, so apart from that fee, no tokens and no SOL move.

Every trigger and its settings

The Armory, in full: five v1 triggers, their settings, and what each one shoots down.

Load up to three per token. Most settings are a share of supply, and every Triggerpad token has a fixed supply of 1,000,000,000, so 1% is 10,000,000 tokens. The quoted line on each spec sheet is the default setting in plain numbers.

Triggers stack. A transfer has to clear every trigger in the loadout, so the strictest one decides.

Fees and the flywheel

Every shot fired buys and burns $TRIGGER.

Trades on the curve pay a 1% fee, collected in SOL. Meteora’s protocol keeps 20% of it. The other 80% is Triggerpad’s share.

Of Triggerpad’s share, 85% buys $TRIGGER through Jupiter, and every token bought is burned. 15% funds development. Creators get 0% today; that share is configurable later.

The flywheel

Every 10 minutes the flywheel runs the same four moves: claim the fees, split them, buy, burn.

Until $TRIGGER trades, the buyback share is held and spent on the first run that can buy. Graduated pools feed the same flywheel: the migration-fee share and the fees from locked LP run through it too.

Every burn is public. The running total is Spent brass: $TRIGGER bought back and burned, shown on Triggerpad and on-chain for anyone to check.

What you’re trusting

Triggers remove a lot of trust. Not all of it. Here is what’s left, stated plainly.

An armed token relies on three layers of programs. You are trusting each one to do its job.

The engine is upgradeable

The trigger engine is an upgradeable program. Its upgrade authority is planned to sit behind a Squads multisig rather than a single key. Plainly: that multisig could change trigger logic, for every armed token at once.

It is also the only safety net. Nobody can remove a hook early, us included, so if a bug ever blocked trading, an engine upgrade would be the only fix. We would rather keep that fix, and tell you it exists, than promise a program with no bugs. The engine isn’t deployed yet and hasn’t been audited.

What Triggerpad can’t do

• ✕Hold your keys. Your wallet signs every launch and every trade.
• ✕Change a token’s settings. They are written once, at launch, and nothing in the engine rewrites them.
• ✕Switch triggers off before graduation. Only Meteora’s program can remove the hook, and only in the buy that fills the curve.

The one lever behind the last two is the upgrade above: new engine code could behave differently. That is why it belongs behind a multisig, and why it’s written here.

Known limits

• Mag Cap counts per wallet token account, not per person. One person with many wallets can spread out.
• Mag Cap exempts the pool and the creator, so the creator’s wallet can hold more than the cap.
• Chambered blocks sends to exchanges too, and to your own other wallets. Anything that isn’t a trade with the pool waits for Safety on.
• Aggregators don’t route armed tokens. Before Safety on, trade on Triggerpad or on a venue that builds the hook-aware swap itself. Permanent tokens stay that way for life.
• Rate of Fire counts every buy in a block, whoever sends it. In a busy block your buy can be shot down; the next block is about 0.4 seconds away.
• The home page scope and counters are simulated until the indexer is live.

Program addresses

Every program Triggerpad relies on. Don’t take our word for any of it: each address opens on Solscan.