가입 후 초대 링크를 공유하면 동영상 재생 및 초대 보상을 받을 수 있습니다.

SliKᵍᵐ
@0xSLK
Full-stack eng · Blockchain & AI enthusiast I like hard problems, clean solutions, and tools people actually use. 🔗 | tg: slkzgm | Discord: slkz.
가입 January 2013
2.5K 팔로잉 중    5.5K
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.
더 보기