Hadron lets you add or subtract spread for specific addresses or programs, letting you distinguish toxic flow from retail flow. Examples:Documentation Index
Fetch the complete documentation index at: https://docs.hadron.fi/llms.txt
Use this file to discover all available pages before exploring further.
- Reduce cyclic arbitrage: Add spread for trades involving competing venue programs or specific bot addresses that buy from your pool and sell to a competing AMM.
- Be more competitive with retail traders: Offer tighter spreads (negative
spread_bps) to transactions with clear signs of retail origin, such as the Phantom/Solflare fee accounts or the Jupiter Ultra fee accounts.
updateSpreadConfig
Replace the pool’s spread trigger list in one call.Full replacement This is a full replacement of all existing triggers. Always pass the complete final list you want on-chain — not just the new entries.
| Param | Type | Description |
|---|---|---|
admin | &Pubkey | Spread config admin signer |
params.triggers | Vec<SpreadTriggerInput> | Full list of spread triggers to store (replaces previous list) |
params.triggers[].account | Pubkey | Account or program key to match against the instruction context |
params.triggers[].spread_bps | i32 | Extra spread in basis points. Positive adds spread (penalises flow); negative subtracts spread (rewards flow) |
params.triggers[].match_mode | Option<u8> | 0 = Anywhere (match if account appears anywhere in the transaction accounts list); 1 = AfterProgramId (match only if account appears immediately after the program ID in the accounts list) |
.png?fit=max&auto=format&n=pH37fL0GL14scVCH&q=85&s=5749b485c8c5b2386a4cca404e97d6be)