My sister
41 posts

My sister
@Goodproject0
I have been working in blockchain for exactly three years

You're name-dropping Drift while their hybrid vAMM literally got exploited today. Not the old one, the upgraded version they rebuilt after the first vAMM failed. So the timeline is: Drift launches vAMM, gets exploited, spends two years rebuilding into a hybrid JIT model, and that just got exploited too. And your plan is to follow the same path starting from step one. Your vAMM is already live and already mispricing trades, users losing money on winning positions right now. And your roadmap is to eventually copy a model that just blew up today. Toly's Percolator skipped vAMM entirely, composable matchers, permissionless listing, best offer wins. No single pricing mechanism to exploit. You're not following Drift's blueprint, you're following their exploit timeline. Good Luck 🍀


Drift protocol appears to have been exploited for over $270 MILLION These massive attacks can’t keep happening (This is not an april fools joke although the timing is ironic)







This is the single most important article for any team competing to fork @toly's Percolator. x.com/PERK_FUND/stat…






Everything here is wrong so let me just walk through it "Zero PERCOLAT magic bytes" — yeah because we ported the risk engine math, we didn't copy paste someone else's binary. That's what porting means. Same equations, clean room implementation "Uses vAMM not Percolator's native matching" — Percolator IS a vAMM. x*y=k with a peg multiplier. That's literally what we built. This tells me you didn't actually read the Percolator spec before writing this thread "Built with Anchor" — like every serious Solana program shipped in the last two years. We wrote it from scratch because we understand the math well enough to do that "Stablecoin collateral instead of SOL-native" — users deposit USDC. It's a design choice not a red flag "GitHub repo created 2 days ago" — that's the public repo. Development was private. We published the source so anyone can verify the on-chain binary matches. Which brings me to the next point "No OtterSec report" — we never claimed a paid OtterSec audit. OtterSec VERIFIED the build. That means the on-chain program binary matches our published source code byte for byte. Anyone can check this themselves at verify.osec.io You scanned 128 accounts and somehow wrote six paragraphs of wrong conclusions. You could've just read the code





