How to use it
Use a trigger when you can finish the sentence “this row exists because of this specific counterparty”. Good targets:- A wallet you have observed. A signer that arbitrages your pool, or a sniper. Ban it with 10,000 bps or more under the wildcard program. Banning a wallet seconds after its first trade is fine. The target is the wallet.
- A bot program on your pool. Key the row on your own config, with the bot’s program id as the program filter. It fires only when that program calls your pool.
How NOT to use it
Do not use a trigger to add spread to all of your routed flow. Routers quote your pool without knowing which triggers will fire, so a row that fires on every swap is a hidden tax: the user is quoted one price and filled at a worse one. Rows that do this:- Your pool itself. Your config, vaults, curve meta, spread config, pool fee config, mints or fee recipient token accounts, under the wildcard or under a router program. Every swap on your pool carries these, and routers copy every one of them into their own instruction.
- All routers. Jupiter, Titan, OKX or DFlow program ids, their event authority PDAs, the jup.ag
frontend signer
sighWH8KaiT7QhtV4w29ReVF8kG6D5yG3EQP1KYyGVF, the Jupiter Ultra relayerAgmLJBMDCqWynYnQiPCuj9ewsNNsBJXyzoUhD9LJzN51or Titan’s authorityD5YqVMoSxnqeZAKAUUE1Dm3bmjtdxQ5DCF356ozqN9cM, under any program filter. - All competing venues. Other venues’ program ids or pools under the wildcard. A retail route that hops through that venue pays it too, and no router quotes it.
- Accounts no swap can avoid. The Token programs, the Associated Token program, the wSOL, USDC
or USDT mints, the global
FeeConfig, the Clock or Instructions sysvars. - Tips and markers. Jito tip accounts,
jitodontfrontmarkers, the Memo program or Jupiter referral. These ride on a large share of ordinary retail flow. NEGATEunder the wildcard or a router. It fires when the account is absent, which is almost every swap, whatever account it names.
Some examples of what’s okay
Some examples of what’s not okay
We may flag other tables beyond these examples. The goal is to prevent retail abuse.