Ink Cat ($ICAT) is a community-owned memecoin native to the Ink blockchain (EIP-155 chain ID 57073), with its official website at inkcat.fun. The project positions itself as unaffiliated with Kraken or the Ink development team, citing origin in a viral moment involving an ‘Ink Risk Manager’ cat. Its sole verified contract address is 0xEF172EE53FbBE945AE2bd6CcfF93384ACf9CF19D, deployed on Ink and viewable on the Ink Blockscout explorer. The site documents a live ICAT/WETH trading pair on DyorSwap, price data pulled directly from DexScreener, and a four-step onboarding flow: adding Ink network, bridging ETH, swapping on DyorSwap, and verifying the contract. Tokenomics state a fixed supply of 1 billion tokens, zero transfer tax, no mint function, and full launch liquidity burned to zero. Official channels are limited to @icat_token on X and t.me/INK_CAT. Key evaluation questions include whether the claimed end-to-end user journey—from bridge to swap to wallet receipt—is demonstrably functional, whether the live chart and pool reflect real-time, verifiable on-chain activity, and whether the absence of owner controls and mint functions is confirmed by on-chain inspection rather than assertion.
Ink Cat ($ICAT) presents a coherent, self-consistent identity across all supplied evidence: the website inkcat.fun, API source_2, and explorer/Telegram/X links all converge on contract
0xEF17…F19Don Ink Chain (EIP-155:57073), zero tax, burned launch liquidity, and explicit disclaimers of affiliation with Kraken or Ink Labs. The lore-driven narrative is internally consistent and transparently framed as meme culture—not utility—reducing expectation mismatch. Tokenomics are clearly disclosed: fixed 1B supply, no mint function, no owner, no transfer tax. Operational dependencies are also candid: users must bridge ETH to Ink, use DyorSwap exclusively, and verify the CA manually—no hidden wrappers or obfuscated flows. However, critical verification gaps remain. No on-chain audit or bytecode verification is cited or linked; the claim that LP tokens were burned to zero is asserted but not demonstrated via explorer transaction hashes or block-level proof in the supplied evidence. The API source repeats website claims without independent validation, and both sources share temporal proximity (retrieved within hours on 2026-09-18), limiting evidentiary independence. While no verified contradiction or concealed control mechanism appears, the absence of third-party technical validation means risk exposure cannot be ruled out. This supports a strong but not exceptional assessment.Overall score: 7/10 Confidence: Medium