Patcha
41 posts


Quick prelude before the proper post:
patcha-cli@0.2.0 is on the npm registry.
npm i -g patcha-cli
esbuild bundles every runtime dep into one binary, so the install adds exactly one package. Same toolkit as the web Designer and the VS Code extension.
The longer write-up sits in the next post.
npmjs.com/package/patcha…

English

The Hook Marketplace is open.
patcha.fi/market — six standard hooks, each with its category, the callbacks it fires on, its params, and its cable colour. Browse a hook, read its source, install it on an Orca or Raydium pool with patcha-cli. The mainnet executor from the last post backs every install — same byte-identical fee fn as the Designer simulation.
Every HookTriggered event is readable on Solana Explorer — pool, slug, callback, allow, fee_override_bps, mev_bps_saved.
patcha.fi/market

English

/4
AntiMEV reports what it prevents as mev_bps_saved on the same event, accumulated across the hook stack; the simulate endpoint surfaces it before you install. Mainnet receipts are public — read every HookTriggered event off the executor's Solana Explorer page.
patcha.fi/designer
English

/1
A backtest is only worth the gap between it and execution. Patcha's gap is zero by construction.
DynamicFee, concretely:
fee = base_bps + (max_bps - base_bps) · min(amount_in, pivot) / pivot
Defaults base 30 bps, max 100 bps, pivot 1 SOL. Integer math, no floats — a small swap pays 30, the pivot pays the 100 cap, between interpolates.

English

The idea of hooks is not new. The Solana CLMM implementation is.
Uniswap v4 hooks (Uniswap Labs 2024) defined composable pool callbacks on EVM. Orca Whirlpools and Raydium CLMM brought concentrated liquidity to Solana. Anchor 0.31 (Coral 2026) is the program framework. Jito's MEV work (Jito Labs 2024) informs AntiMEV.
Patcha stands on those. The first standard hook library and executor for Solana CLMMs is the new part.
patcha.fi/docs

English

Ship hooks from your editor.
The VS Code extension is the Designer in your editor: scaffold a hook, see inline backtest results, install with a command. patcha-cli is the same toolkit in your terminal — init, create, list, simulate, deploy, install.
npm i -g patcha-cli
Downloads (cli 0.1.2, extension 0.1.2):
patcha.fi/devtools


English

/4
Same toolkit, three surfaces: the web Designer, the CLI, the VS Code extension — one @patcha/sdk, one runtime behind them. simulate, install, and trigger all hit the same mainnet executor. Same number off-chain and on.
github.com/patcha-fi/patc…
English

/1
Build your first hook, end to end.
npm i -g patcha.fi/downloads/patc…
patcha init my-hook
patcha simulate dynamic-fee --pool
patcha install dynamic-fee --pool --cluster mainnet
Four lines: scaffold, backtest on real pool data, install on mainnet. The CLI is the hosted tarball — not on the npm registry yet. simulate is free; install pays a tiny SOL fee for the registry write.

English

