Programmable execution for Meteora.
Compose deterministic risk, execution, treasury and automation policies around swaps routed to Meteora DAMM v2 and DLMM.
Add a policy layer to execution
Build a bounded stack that runs before and after a routed swap. The router verifies the selected Meteora program and pool ownership, measures actual wallet balance changes and enforces max-in or min-out atomically.
Compose market behavior
Every routed trade runs its stack in priority order: before hooks, the Meteora CPI, after hooks and settlement. One denial or failed check reverts the complete transaction.
Build within clear limits
Write WHEN / IF / THEN in the Composer and compile it to a bounded Policy VM with no loops or arbitrary CPI. Inspect capability-scoped state, priority namespaces, estimated compute and deterministic execution before routing a transaction.
Bounded automation, not custody
An off-chain engine may propose a tighter execution regime, while the program verifies its signature, nonce, freshness and TTL ceiling. It never signs for users, never trades by itself and never takes custody of wallet funds.
What Meteora Hooks can and cannot do.
The enforcement boundary is explicit so users can judge the product honestly.
Meteora programs do not call this hook system natively. Direct DAMM v2 or DLMM swaps bypass the stack.
The wallet signs one atomic transaction. The policy layer does not hold user tokens or redirect venue fees.
Meteora's mainnet venue programs are verified. Hook-enforced mainnet writes remain disabled until the custom router is audited and deployed there.