Patcha @Patcha_fi

Patcha TG is open. a room to ask install questions, share hook configs, drop your install tx when you ship one, and hang out. join: t.me/patchasol

npm i -g patcha-cli@latest # 0.4.0 patcha list # 8 hooks patcha simulate jit-defense --pool --dex orca patcha install price-impact-cap --pool --dex orca market: patcha.fi/market — 8 cards, new two at the bottom. next: live stats dashboard. install count, burn total, tier distribution, HookTriggered events — all read live from chain. so you don't have to trust me when I say "8 hooks are live" — you'll watch the counter move.

verified on mainnet, not just install paths this time: dispatch effect. PriceImpactCap: small swap allowed, oversized swap reverted with HookVetoed. JIT-Defense: BeforeAddLiquidity records the block, same-block add+remove in one tx reverts. burn path. install_hook_burning through the CLI on a fresh pool from a T5 wallet — supply Δ and wallet Δ both exactly -50,000 PATCHA. CLI burn proof tx: solscan.io/tx/3Z5oLgD3MGn…

shipped, end to end. eight builtin hooks live on mainnet. the two new ones: PriceImpactCap (gating, beforeSwap) — per-swap impact cap. LP-owned slippage ceiling on the pool. JIT-Defense (mev, beforeSwap + addLiq + removeLiq) — same-block add → remove sandwich detection. on-chain state plumbing, not a stub.

ready?

two new hooks queued. PriceImpactCap — beforeSwap callback. denies any swap that would move the pool price more than `cap_bps`. set it to 100 bps and a single dump trying to push the price 1.5% gets reverted before it touches the pool. LPs install it to put a ceiling on slippage in their own pool. JIT-Defense — beforeSwap + beforeAddLiquidity + beforeRemoveLiquidity. tracks add → swap → remove patterns within one Solana block from the same wallet. when the same wallet adds liquidity, sandwiches a swap, and removes liquidity in the same block, the second-to-last step reverts. just-in-time LP attacks routed away. both ride the same install_hook_burning path the existing six do — same holder-tier burn, same Solscan receipt shape, same simulate-then-install flow. shipping when the runtime port lands and the backend simulator passes on at least one mainnet pool's history. no specific date. eight standard hooks instead of six.

small site update for anyone trying to actually use patcha-cli. new at patcha.fi/cli: - exact prerequisites (Node 20+, Solana CLI, a keypair, some SOL, PATCHA for the burn path) - the 2 install paths (npm or hosted tarball) - a 60-second walk-through (list → tiers --wallet → simulate → install → init) - per-command reference with examples - the holder burn tier table - common errors and how to unblock (insufficient PATCHA, fetch failed pre-0.3.x, the bigint warning, missing keypair) also added a /docs entry for the same content so it's searchable, and mirrored to github.com/patcha-fi/patc… for people who'd rather read on github. a lot of the friction was just "I installed patcha-cli but it does nothing" — turns out Solana CLI + a keypair weren't obvious. now they are.

@Naruto_san10 I'm planning to launch it within the next 24 hours. having a public community brings massive momentum and is great for maintaining or raising the price. but if we don't manage it well, people will complain a lot... lol That's why I wanted to wait until we were perfectly ready.

"how do I get into a lower burn tier?" short answer: hold more PATCHA. that's it. five tiers, on chain, the table is a pure function of your share of total supply. walking through it ↓

@dora_bae8 PATCHA is the "ticket" for using the slot. every time someone installs a rule, a small amount of PATCHA they hold goes away forever. the more PATCHA you already hold, the smaller the ticket cost.

example rules people want to bolt on: - charge less fee during quiet hours, more during volatile ones - only let approved wallets trade for the first hour - block any single trade that moves the price more than 1% each of those is a "hook". patcha is the slot where the hooks go. six are built in. devs can write their own.

honest question, easiest answer: think of a vending machine for tokens. it sits there, takes in one coin, gives you back another, all by a fixed rule (price = depth of what's inside). a "liquidity pool" is that vending machine. patcha lets you bolt a small rule of your own onto the machine.

honest question, easiest answer: think of a vending machine for tokens. it sits there, takes in one coin, gives you back another, all by a fixed rule (price = depth of what's inside). a "liquidity pool" is that vending machine. patcha lets you bolt a small rule of your own onto the machine.

why trust the number: the same calculate_burn function runs in the Anchor program (executor), the SDK (off-chain quote), and the CLI. one rust function, three call sites, identical math. mint authority on PATCHA is null. burn is a permanent supply reduction, not a transfer to a treasury. full spec: patcha.fi/docs#token-eco…

check your tier right now without installing anything: npm i -g patcha-cli@latest patcha tiers --wallet reads live mint supply + your Token-2022 ATA balance, prints the tier, the burn amount per install, and how many installs you have left before the next bracket. no signer key needed — read-only quote.

shipped. install burn is now a function of your PATCHA holdings, not a flat fee. five tiers, all on chain, no admin discretion: T1 ≥ 2.0% supply → 100 PATCHA / install T2 ≥ 1.0% → 300 T3 ≥ 0.5% → 1,000 T4 ≥ 0.1% → 5,000 T5 < 0.1% → 50,000 holding is the discount. non-holders pay the heavy rate, which forces a buy → install → re-buy loop. that loop is the supply-side pressure. verify your own tier any time: npm i -g patcha-cli && patcha tiers --wallet four T5 burns went through today on the same test wallet. last one: solscan.io/tx/XHTuLoZuLX9… PATCHA mint authority is off, supply only goes down. next on the queue: fee buyback.