I've had a lot of DMs asking for updates, so I want to clarify where I stand and ask for your feedback. $LEAK started as a live POC while I was building LaunchProof. At the time, I could only detect X-verified launches from @zacklabadie . I launched $LEAK to confirm whether the public flow worked for someone else and whether my detection was accurate. It worked. That was its original purpose. I never promised utility or a roadmap. What happened afterwards was much bigger than expected. $LEAK nearly reached a $500K market cap, and I kept shipping because I felt responsible for the people around it. Today, I own no $LEAK. I burned my remaining balance after the community asked me to, including tokens I had bought around an $80K market cap. Creator fees are negligible and cannot fund continued development by themselves. I also have a job and other responsibilities. I am always happy to share real progress, receive feedback and consider useful features. What I do not want to do is create announcements or activity purely to influence the chart. $LEAK did not fall in isolation either. Most tokens built around the narrative followed similar charts. I am still open to building something much more ambitious if there is a real market for it. Better analysis, security tools, data, alerts, execution or even a complete trading product could all be interesting directions. That genuinely excites me. But I want to build something solid with a real chance of working, not rush out a broken product in three days for a short-lived reaction. If LaunchProof eventually generates enough revenue to fund development and let me dedicate myself to it full time, many more things become possible. LEAK integrations, holder benefits or even transparent buybacks could then be discussed. Revenue has to exist first, and I do not want to promise mechanisms that cannot yet be funded. If LaunchProof finds a product people genuinely use and becomes sustainable, I’ll be able to dedicate much more time to it and build it properly. I’d genuinely enjoy shaping that direction with the people using it. So tell me what would actually be useful. What is missing from LaunchProof, and which problem would you want it to solve?

A quick note on X verification across @Uniswap’s new launches. and Uniswap’s public launch data are currently missing the X identity for many tokens that were genuinely authenticated during deployment. This matters because seeing an X handle inside onchain metadata is not enough to call a launch verified. Anyone can write a handle, user ID and wallet into a token’s metadata. The important part is proving that the data was signed through Uniswap’s X flow and belongs to the wallet that actually deployed the token. Until now, I deliberately required two confirmations: • Uniswap had to expose the authenticated X account through its API • The signed wallet had to match the onchain deployer This was the safest approach available. If Uniswap had not indexed the identity yet, LaunchProof would not display a verified badge or send an alert, even when the launch might eventually prove authentic. A recent audit confirmed how incomplete the current indexing is. I scanned 12,238 launches from the registered Uniswap launch contracts. 311 contained an X verification claim, but only a fraction were properly reflected in Uniswap’s public data. After checking them independently: • 249 contained a valid X-to-wallet binding • 30 had no genuine signature • 16 contained malformed signatures • 12 were rejected by Uniswap’s verifier • 4 reused a valid token from the wrong wallet So the caution was justified: an X-looking payload is not automatically authentic. The good news is that I found a way to validate these signatures directly through Uniswap’s official verification flow, without signing or broadcasting any transaction. LaunchProof can now detect a launch onchain, confirm that its X proof is authentic, and verify that it belongs to the actual deployer without waiting for or ListLaunches to catch up. Uniswap’s API remains useful for images, current handles and market data, but it is no longer required to establish provenance. The historical launches have been backfilled, and the dashboard and Telegram alerts can now recognize valid X-linked launches even while Uniswap’s public indexing is delayed. Technical errors still fail closed: if a verification cannot be completed, it remains pending and no verified badge or alert is produced. Unfortunately, since I know some of you were hoping for alpha, the follower ranking did not reveal much this time. The largest accounts either launched Crowd auctions that never migrated or Instant tokens whose markets are already effectively dead. Authenticated provenance tells us who launched a token. It does not make the token liquid, safe or worth buying.

Incredibly excited for the launch of @TradePools!! This rollout has been absolutely insane. Degens discovered earlier versions of the smart contracts and traded over $150m in trading volume before the UI even went live This created a unique challenge where we had to update our site and indexing to support both the earlier test versions and the final versions of the contracts at the same time, which added some additional time to the launch People have used uniswap as both a launchpad and launchpad infra for over 8 years. We're excited to be building alongside all the other launchpads to move the space forward What most sets apart? - no added launchpad fee, just the normal protocol fee that comes with all v4 pools. This makes the launch pool way better for traders, with total spreads far lower than most launchpads - autocompounding liquidity (excited to bring this feature to normal Uniswap LPing as well) - permanently locked liquidity for all launches - two launch methods: instant launch works similar to other launchpads, and crowd launch simplifies what we built with CCA to create a fairer, more bundle resistant launch method - deep integrations and distribution: Pools has day one support across uniswap web app, wallet, trading api, all third party trading api integrations, bitget, fomo, gmgn, okx wallet, etc, with more coming online rapidly Have seen various takes claiming incorrect fee splits - to be clear the 0.25% LP fees autocompounds to the locked liquidity pool, it does not go to the uniswap team. This becomes 20% to the creator and 80% to the liquidity compounding mechanism Uniswap Labs team has been cooking hard on this one but its still in beta. We intend to ship a constant stream of upgrades and improvements from here. So please share any feedback!!

The next token may not exist yet. You can still watch its deployer. LaunchProof now lets you follow any X account or wallet and receive a push the moment it launches through Uniswap—even with the app closed.

No wait, you guys are being harsh. It’s basically the same as except for the charts, the browser alerts, the Telegram alerts, the direct trading links, the deployer profiles, the X profile pictures, the deployer info, and… Okay yeah, never mind 😭

If you’re like me and have ever launched a token only to realize the bots bought it before you did: fixed. Sorry, I just made the LaunchProof flow one step longer. Instant Launches now support an optional atomic dev buy: token creation, pool initialization and your buy all execute in the same transaction. No gap for snipers. Official Uniswap route. 0 added fees.

Still waiting for we have at home Track every launch. Launch through Uniswap’s official contracts. Manage creator fees. Looking forward to the official release too 🤝

Quick LaunchProof update following an official @Uniswap SDK change on Robinhood Chain. The SDK now references Liquidity Launcher v3.1.1. In practical terms, it uses a new launcher, dedicated Instant strategies for fees-on and fees-off launches, and a new FeeSplitter/BeneficiaryVault pair to manage creator fees. LaunchProof now supports this generation across tracking, launching, alerts and fee management. The dashboard detects launches directly from the launcher contracts, then uses Uniswap’s API for market data and metadata. This gives us a more complete index across both registered launchers. What’s new: • Instant Launch now uses the current v3.1.1 route • Explore tracks launches across both launchers • X-linked provenance is still cross-checked against the onchain sender • The $LEAK holder Telegram bot now watches both launchers • The Fees page lists tokens created by your wallet and positions where you are the current beneficiary • Beneficiaries can collect pending LP fees and claim credited fees directly from their wallet No custody, no automatic collection and no added platform fee. Every fee action is simulated and explicitly confirmed by the beneficiary wallet. As always, X verification proves provenance, not safety or endorsement. There might be a little alpha hidden in the video too, for those paying attention. 👀

Thank you for all the support around LaunchProof. Demand for X-verified launches using the 1M $LEAK burn was higher than I expected and caught me a bit off guard, so I built the process directly into the app. It verifies the burn, walks you through the X setup, then takes you through the verified deployment end to end. This should reduce the bottleneck on my side. If you run into any issue, my DMs are still open. I also added @wallet (OKX Wallet) to the one-click trading links. Sorry if I’m slow with DMs and replies right now. There’s a lot coming in, but I’m reading everything and answering as much as I can. I want to stay available for questions while continuing to ship useful tools for everyone.