The token exists.
Its utility is coming.
Minted when Zaia launched, on Base, via Virtuals. One billion, fixed, verifiable by anyone. Not equity, not a promise of returns, not a gate. The key that opens more of KinkyBunny and Zaia, never the lock.
0x3a2459C39f50406f40D28Db8d823433df0352b11On-chain facts, verified 3 Oct 2026. Price is not published.
Per the published schedule, every allocation except equity investor perks has fully vested by October 2026. The live schedule is the Virtuals agent page. Exact terms below.
Allocation and vesting, as a table
| Allocation | Share | Tokens | Terms |
|---|---|---|---|
| Public sale | 37.5% | 375,000,000 | Fully unlocked at launch, via Genesis bonding |
| Founding team | 20.0% | 200,000,000 | Linear over 12 months from 6 Aug 2025 |
| Development fund | 13.0% | 130,000,000 | 15% at 6 Oct 2025, remainder linear to May 2026 |
| Liquidity pool | 12.5% | 125,000,000 | Uniswap at graduation; not held by the project |
| Marketing & community | 12.0% | 120,000,000 | 30% at 6 Aug 2025, remainder linear to Mar 2026 |
| Equity investor perks | 5.0% | 50,000,000 | 10% at 6 Nov 2025, remainder linear to Nov 2026 |
It enriches. It never gates.
The product is complete without KBT. No screen locks, nothing essential disappears. Holding KBT will add, across KinkyBunny and Zaia, with no ranking and no dates:
Holding KBT confers no ownership of Black Octopus SA, no dividends, no profit share.
No returns are promised or implied. No buyback, burn or price mechanism exists or is planned.
Everything essential works without it; it only adds extras. Never a condition to pay for anything, never a paid place in the results.
KBT operates under a Swiss utility token model in alignment with FINMA guidelines. It is designed purely for platform access and participation. No profit-sharing. No equity or financial claims. No speculative guarantees. KBT is a utility token, not a security. It offers no investment returns and is not marketed as a financial product.
Version 2.0, October 2026. Includes what changed since v1.0, and why.