AGENTIC INU ← Back to packs

Pack odds, in the open.
Nothing here is rigged — and you don't have to trust us to know it.

This page explains exactly how the rarity of every Agentic Inu pack is decided, why nobody — not the team, not a whale, not the contract itself — can influence a pull, and how you can re-check any pull ever made, yourself, from public data.

1. The odds

Every pack costs $1 (paid in BNB at the live Chainlink BNB/USD price) and contains exactly one pull. A pull pays $AINU tokens directly — the rarity is a multiplier on a base award of 50,000,000 $AINU:

These five percentages are constants written into the smart contract. The contract has no function that can change them — not by the owner, not by anyone. Once the contract is deployed and its source is verified (publicly readable on Sourcify), the odds above are the odds forever.

2. How a pull is decided

1. You buy a pack. The contract records your purchase and requests a random number from Chainlink VRF — the same verifiable-randomness service used across BNB Chain. The request is a public on-chain transaction.
2. Chainlink generates the number off-chain and delivers it with a cryptographic proof. The contract checks the proof on-chain before accepting the number. A number without a valid proof is rejected automatically.
3. The contract maps the number to a rarity using only the fixed table below, and publishes the result in a public event: your wallet, the request ID, the random number, the rarity, and the token amount.

The exact mapping — check it yourself

Take the random number delivered for a pull, compute number mod 10,000, and look up the result:

That is the whole mechanism. There is no hidden second step, no server, no manual review.

3. Why it cannot be rigged

• The team cannot pick the number. It is generated by Chainlink's oracle network, not by our servers, and delivered with a proof the contract verifies. A forged number cannot pass.
• The team cannot see your number before you buy. The number does not exist until after your purchase transaction is on-chain and the VRF request is made.
• Nobody can re-roll. The result function can only be called by the Chainlink VRF coordinator, exactly once per request. A bad result cannot be discarded and retried — there is no retry path in the code.
• Nobody can change the odds after launch. The percentages are compile-time constants, not settings. There is no admin function for them.
• Nobody can mint outside the pack system. $AINU starts at zero supply and is created only by pack pulls and the pool seed described on the main page, under a hard cap of 100,000,000,000,000 (100T) and a maximum of 1,000,000 packs.

4. "But nobody has pulled a Mythic yet — is it real?"

Yes. Mythic is expected 10 times per 10,000 packs on average — about 2 in every 2,000 packs — but averages are not schedules. In any specific run of 2,000 packs the count is random, typically between 0 and 5, and roughly one run in seven has no Mythic at all; that is what honest 0.1% odds look like. What would not be normal is a long-run rate that drifts away from 0.1% — and that is exactly what the public record makes impossible to hide.

The real test of fairness is the long run, and it is fully public: every pull ever made is an on-chain event anyone can count. Over 100,000 packs the observed rates must converge on the table in section 1 (roughly 87,400 Commons, 10,000 Rares, 2,000 Epics, 500 Legends, 100 Mythics, within normal statistical wobble). If our numbers ever drifted from that, anyone could prove it from public data — the data cannot be edited or deleted.

5. Verify a pull yourself

1. Find the pack purchase on BscScan and note the VRF requestId.
2. Open the fulfillment transaction: it publishes the random number delivered by Chainlink.
3. Compute number mod 10,000 and compare it with the mapping table in section 2.
4. Compare the rarity and amount in the pull event with your calculation. They must match — the contract derived them from that same number using that same table.

A one-click pull checker will be linked here at launch.

6. The rest of the system, briefly

• Packs are sold only to wallets holding a Binance Agent ID (SPACE ID), verified on-chain by the contract. Phase 1 limit: 10 packs per wallet.
• Phase 1 payments are held in escrow. At pack #10,000 the pool opens: 80% of the $10,000 raised seeds a PancakeSwap pool together with 500,000,000,000 $AINU; 20% goes to the treasury. Every pull mints its $AINU into the escrow at reveal, so a buyer's tokens exist from the moment their pack opens; at pool open the escrow pays everyone out in waves, and token transfers stay locked until distribution completes — nobody trades before every phase-1 buyer holds their tokens. The pack price rises in fixed steps after the pool opens; the schedule is a constant in the same verified contract.
• If pack #10,000 is not reached within 7 days, the sale fails and every buyer reclaims 100% of their payment with claimRefund(); their escrowed tokens are burned and the pool never opens.
• After the pool opens, packs keep selling: 80% of every payment enters the pool, pulls pay the pack's value at the live pool price plus a 1% bonus, and a public floor-defense function burns pool tokens whenever the market value of the supply falls below ~1.8× the total paid in.