Dripz

@Dripzfi × @Patcha_fi — live on Solana mainnet. Every Dripz LBP launch now ships through Patcha's hook executor. The Dripz auto-CLMM cron installs anti-mev, price-impact-cap, and jit-defense on every migrated Raydium pair (T1 holder rate, 100 PATCHA burnt per install). The Dripz program v0.5 swap path fires Patcha's trigger_hook (BeforeSwap) CPI on every buy and sell -- veto from the hook reverts the swap. Two anchor programs, one launch flow, zero manual integration. Dripz program AsxnSxBeFwtkzxchwVDxz1VBZRuePFXBcdodfcinTrQx Patcha program EPcW7e8RxBNPpQK2XKoKG9maWH6QvmU3ejxifoU5rNRa dripz.fi/launchpad

A glacier does not melt on demand. dripz.fi · $DRIPZ

Things you can verify on-chain on every Dripz launch, in order: 1. Program ID — AsxnSxBeFwtkzxchwVDxz1VBZRuePFXBcdodfcinTrQx 2. Mint authority — None (setAuthority(null) in launch tx) 3. Freeze authority — None (same tx) 4. Initial liquidity — both vaults non-zero (seed_pool in launch tx) 5. Curve params — readable on the Pool account 6. LBP close — close_lbp signed by the cron wallet 7. Raydium pool — record_clmm_pool writes the pair address on-chain 8. LP burn — Raydium LP mint total supply = 0 No checklist on the website would be worth anything if any of these were missing. Every one is verifiable by reading the chain. dripz.fi/launchpad just makes them easy to follow.

The minute a Dripz pool migrates, it shows up on the aggregators traders already use: · DexScreener · GMGN · Axiom · Photon · Padre The Raydium pool address is written on-chain via record_clmm_pool, the launchpad detail page renders five deep-links into those frontends, and the LP is burnt before any of them finish indexing. The trader's wallet, the trader's chart, the trader's terminal — all already on Dripz pools. dripz.fi/launchpad

Five standard curves on one screen. Same Anchor instruction underneath, different weight function on top: · Linear — even decay, the canonical LBP shape · Exponential — aggressive early decay, snipers buy at the worst tick · Step — piecewise constant, four rungs, surfaces a fairer floor · Dutch Auction — strict descent from start price to a floor · Fair Discovery — symmetric U, biased toward middle-of-window buyers Pick a curve in the form, the backtest preview runs the same Rust runtime the on-chain executor ships with. The number you see is the number the program signs. dripz.fi/launchpad

What "permanently locked" means on Dripz: close_lbp finishes the LBP window. migrate_to_clmm moves 10% of the post-LBP vault into a PDA holding ATA owned by the pool itself. withdraw_clmm_holding drains that PDA into the cron wallet. The cron then calls Raydium's createPool with the freshly-withdrawn tokens, gets back an LP mint, and immediately calls burn() on the entire LP balance. No wallet - not the issuer, not Dripz ops, not the cron - can ever pull that liquidity. The pool ID is then written back on-chain via record_clmm_pool so the badge appears in the launchpad list automatically. dripz.fi/launchpad

The launch transaction does six things in one signature: · initialize_pool — the Anchor program creates the LBP and writes the curve · seed_pool — issuer deposits both sides into the pool vaults · optional dev buy — the issuer pre-buys at the opening price, atomically · setAuthority(null) × 2 — mint and freeze, both revoked · two SOL transfers — split launch fee to the buyback vault and the cron vault The dev buy lives inside the same tx as initialize_pool. There is no window between "pool exists" and "first buy lands" for a bot to wedge into.

Every Dripz launch ships with mint + freeze authorities revoked on-chain. Not an opt-in toggle. The launch tx appends two setAuthority(null) calls right after seed_pool — MintTokens and FreezeAccount, both null, atomically. GMGN, Birdeye, and Solscan all read a clean "authorities revoked" badge the moment the tx confirms. If the issuer can't inflate supply and can't freeze a trader's ATA, the two oldest rug switches are physically gone from the launch path. dripz.fi/launchpad

Why this matters for traders on Dripz: you never wait for the dev to migrate. Trade from the second the pool exists. While you're buying or selling inside the LBP window, the auto-finalize cron is already watching the clock. The moment the window closes, it locks the price, pairs 10% into a Raydium CPMM, and burns the LP — without anyone clicking anything. The "dev keeps the LP and rugs at migration" switch doesn't exist on Dripz. The migration runs whether the dev is at their desk or asleep. ~30 seconds after the LBP expires, the CLMM pair is permanently locked. dripz.fi/launchpad

The Glacier Zero Challenge - 24 hours, five winners. Two steps to enter: 1. Buy any amount of $DRIPZ - post the tx hash in reply. 2. Launch your own pool on dripz.fi/launchpad and reach Migrated status - tag the pool's CLMM pair in the same reply. Five winners drawn at random from qualifying replies: · 1 SOL each (5 SOL total) · Permanent shoutout from @Dripzfi Every Migrated pool counts equally - no "highest market cap" gaming, no token-supply tricks. Genuine end-to-end launches only. dripz.fi/launchpad

The Launchpad opens shortly. list and inspect every active LBP on Dripz, connect a wallet, configure a pool of your own. Curve, duration, anti-snipe slot count, vesting cliff and length, Jito tip, CLMM bridge target — every parameter is a field, every field has a backtest preview that calls the same Rust runtime the executor ships. Issuers, not bots, set the curve. Bots, by design, pay the worst price on it.

Five standard curves. One Anchor instruction. Linear — w(t) = w0 - (w0 - w1) * t / T. Even decay; the canonical LBP shape. Exponential — w(t) = w1 + (w0 - w1) * exp(-k * t / T). Aggressive early decay; snipers eat their own bid. Step — piecewise constant, 4 rungs by default (or a custom JSON). For DAO treasury issuance. Dutch Auction — weight is pinned to a price target descending from p_max to p_min. Short, sharp price discovery. Fair Discovery — weight follows realised buy pressure with alpha. Copper-style adaptive curve. `CurveKind::{Linear, Exponential, Step, Dutch, Fair}` is a runtime enum. Picking a curve is a parameter on initialize_pool, not a separate program. The Designer simulates each one; the executor runs each one from the same byte-identical fee fn. github.com/dripz-labs/dripz/…

MAINNET dripz_lbp is on Solana mainnet at AsxnSxBeFwtkzxchwVDxz1VBZRuePFXBcdodfcinTrQx. same Program ID as the devnet binary. same .so. same byte-identical curve-runtime shared with the off-chain Rust crate, so the number you backtested in the Curve Designer is the number the chain runs. loader: BPFLoaderUpgradeab1e11111111111111111111111 deploy tx: spmfbGS8nVYxa7xEdqfxeUe9aTw1x98D1DKFrcPx7DtnPgtU2346qRXvZZKdHGdciqtBJE7gzMQGyJhm8jrNVb9 IDL on-chain: 3XTTGoGdsmzNXTjNZS2DNg6ADsZsWY99m33fj7YhvqKi what runs on mainnet today: initialize_pool / seed_pool / buy / close_lbp / transition_to_vesting. the five standard curves. Streamflow-compatible vesting handover on close. The default CLI / SDK submit buys via Jito bundles with the DontFront tip pattern. explorer.solana.com/address/… dripz.fi github.com/dripz-labs/dripz

The Anchor 0.31 executor is built. dripz_lbp.so compiled from the public source at github.com/dripz-labs/dripz. Same binary that runs the devnet tests today, byte-identical to what mainnet will receive. Program ID will stay AsxnSxBeFwtkzxchwVDxz1VBZRuePFXBcdodfcinTrQx — the keypair was generated once and pinned. What the executor enforces on-chain: the five curve kinds, the protected-window per-tx max-buy cap, and the close + auto-vesting transition. What the default toolkit (dripz-cli, @dripzfi/sdk, Launchpad) adds on the client side: Jito-bundle submission with the DontFront tip pattern. All of it in the source. The deploy slot is the next one. github.com/dripz-labs/dripz

The Curve Designer is open. dripz.fi/designer — drag a Linear, Exponential, Step, Dutch Auction or Fair Discovery curve onto the bench. Set the duration, the start and end weights, the curve-specific knob, the anti-snipe slot count. Backtest it against a synthetic Pump.fun-style snipe profile and read the spot price drift, the snipe-window bps lost, and the realised exit weight. Composing and backtesting are free. The Rust curve-runtime behind it ships byte-identical to the on-chain Anchor executor. What the Designer prints is what the chain will run. dripz.fi/designer

The Curve Designer opens shortly. Five curve kinds on one rack. Drag a curve, set start weight, end weight, duration, anti-snipe slots, the curve-specific knob (k for exponential, step heights, dutch min/max, fair alpha). Backtest against a synthetic snipe profile before anything touches the chain. The Designer calls the same Rust curve-runtime the on-chain executor will ship — byte-identical fee and weight functions. The number you see is the number the chain will run.