KAY9The On-Chain Watchdog
You found a token. Before you touch it, find out what it can do to you: who can mint it, who can freeze you, who is holding it and who launched it. Scan any token free, in this browser.
English governs the contract statements on this page. Contract names, addresses and numbers are shown as they are on the chain.
- block
- …
- token
- not deployed
- pool
- not launched
- audit
- not deployed
Who this is for
For traders and buyers
You found a token and you want to know what it can do to you before you touch it. Scan the contract free in your browser, and go deeper on the ones that matter.
Scan a tokenFor token creators
Put your own token under the watchdog. You get exactly the same engine and exactly the same scoring as anyone else, and the report says you asked for it. You cannot buy a good score here.
Audit your tokenFor builders
Wallets, exchanges, launchpads and bots can read KAY9 risk data straight from the registry contract. One call returns the latest score, its flags and when it was measured.
Read the registryKAY9 is on the buyer's side. Everything else follows from that.
What the chain is launching right now
Read by your own browser, straight from Robinhood Chain. No KAY9 server is involved and none of these numbers is one you have to take on trust.
- Tokens launched
- —
- Reached a real pool
- —
- Launch sources active
- —
In the last 8 minutes of chain time.
The ones people can actually buy.
Of the sources this browser pass reads.
reading…
These have been detected, not scanned. KAY9 has no opinion about any of them yet, and a token appearing here is neither a warning nor a recommendation. Scanning happens in order of what people can already buy.
What is proven
Six claims the token contracts settle, once launched — none of them are deployed yet. Each one names the code that will enforce it, so you can check the source rather than believe a promise.
Fixed supply
1,000,000,000 KAY9, minted once in the constructor.
KAY9Token — no mint function exists
Fair launch
No presale, no whitelist, no team pre-buy, no validation hook.
KAY9Genesis asserts every launch parameter on-chain
Permanent liquidity
The LP NFT goes to a fee splitter with no withdrawal path.
KAY9LiquidityLock — one way, permissionless
0 % token tax
Buy, sell and transfer are the unmodified OpenZeppelin ERC-20.
KAY9Token — standard transfer, no hooks
Official pool fee 1 %
A Uniswap v4 pool fee paid to liquidity providers, not a token tax.
pool key fee = 10000, tick spacing 200, hook = Uniswap InitializerHook (initialize-only gate)
Team locked on-chain
9 % over three immutable unlock timestamps, released permissionlessly.
KAY9TeamVesting — timestamps are immutable
The audit protocol
Access gets you analysis, not a score. A token's own creator can open access, request an audit of their token, and still get 25/100.
Steps drawn in brass happen on Robinhood Chain. Steps drawn in outline happen off-chain, in the auditors — that outline is the trust boundary, and it is where the quorum signature exists to close it.
1Lock
You lock KAY9 to open a 30-day access period. Nothing is spent and nothing is paid.
Where this step runs
This step happens on Robinhood Chain.
2Request
The hub checks your access and spends one audit from your allowance. No KAY9 moves.
Where this step runs
This step happens on Robinhood Chain.
3Detect
Three auditors see AuditRequested and each starts its own analysis of the same block.
Where this step runs
This step happens off-chain, in the auditors.
4Analyze
Each auditor reads the target chain independently and writes a report of its own.
Where this step runs
This step happens off-chain, in the auditors.
5Sign
Each auditor signs the EIP-712 result it computed, and only that one.
Where this step runs
This step happens off-chain, in the auditors.
6Commit
Two matching signatures append the result to the registry. Three different answers mark the job disputed instead.
Where this step runs
This step happens on Robinhood Chain.
Live protocol activity
The last eight events, read from the chain when you opened this page.
No protocol events yet on this chain.
The contracts are not deployed here. Once they are, the last eight events appear in this ledger with a link to each block.
One registry, many chains
Reports are keyed by a CAIP-2 chain key and an asset id, so a Solana mint and a BNB token sit in the same append-only history as a Robinhood address.
Only Robinhood Chain is live. Everything else is drawn in outline because it is planned, not shipped.
What runs where
The website is a window. If it disappears, everything below still works and anyone can build another one.
| Claim | Where it lives |
|---|---|
| Basic checks | your browser, public RPC |
| Requesting an audit | KAY9AuditHub.requestAudit |
| Your access | KAY9AccessVault |
| Your remaining allowance | KAY9AccessVault.consume |
| Deep and forensic analysis | three independent auditors |
| Agreement between auditors | KAY9AuditHub.attest, 2 of 3 |
| The committed result | KAY9Registry.recordReport |
| Every past result | KAY9Registry, append-only |
| The full report | IPFS, hash committed on-chain |
| This website | static export, no server |
The limit of a two-of-three quorum
Two agreeing auditors can commit a result, so the arrangement protects against one dishonest auditor and not against two. At launch two of the three identities run inside accounts the project owner controls. Moving them onto independent operators is the next piece of work, and it is on the roadmap rather than described as already done.
The token comes after this works
$KAY9 has not launched. Everything above runs without it, and will keep running whether or not it ever does.
When it does launch it is a fixed supply of one billion, sold in a public auction anybody can bid in, with the liquidity permanently locked and the team on calendar unlocks. It buys access to deep and forensic audits by being locked, not spent — the principal comes back in full. The conditions that have to be met before any of that happens are written down and checkable.
Where the supply goes
One billion KAY9, split once at genesis. The 91 % launch allocation is halved: half is sold in the auction, half is paired with the auction's ETH as permanent liquidity.
Public fair auction
455,000,000
45.5 % · KAY9
Sold in the continuous clearing auction.
One billion KAY9 are minted once, in the constructor of KAY9Token, and handed to KAY9Genesis. The 91 % launch allocation is split evenly: half is sold in the auction, half is paired with the auction's ETH as permanent liquidity. The remaining 9 % goes straight into the vesting contract and cannot be touched before its timestamps.
Permanent liquidity reserve
455,000,000
45.5 % · KAY9
Paired with the auction ETH in the v4 pool.
One billion KAY9 are minted once, in the constructor of KAY9Token, and handed to KAY9Genesis. The 91 % launch allocation is split evenly: half is sold in the auction, half is paired with the auction's ETH as permanent liquidity. The remaining 9 % goes straight into the vesting contract and cannot be touched before its timestamps.
Team
90,000,000
9 % · KAY9
Locked by KAY9TeamVesting, three tranches.
Enforced by KAY9TeamVesting.unlocked() — three immutable timestamps set in the constructor, and a permissionless release().
Allocation at genesis
Point at a slice or a label to read its exact figure; the pie and the bar highlight together.
Point at a slice or a label to read its exact figure; the pie and the bar highlight together.
| Allocation | KAY9 | Share |
|---|---|---|
| Public fair auction | 455,000,000 | 45.5 % |
| Permanent liquidity reserve | 455,000,000 | 45.5 % |
| Team | 90,000,000 | 9 % |
When can the team sell?
In three steps, against timestamps that are set once and can never move: 1 % at TGE, 4 % six calendar months later, 4 % after twelve. The unlocks are calendar dates, not “180 days”, and they are computed as exact UTC instants at deployment.
Team unlock schedule
Cumulative team supply unlocked over time. The offsets are fixed by the contract; the exact UTC timestamps are set when KAY9TeamVesting is deployed.
| Tranche | Unlocks (UTC) | Amount | Cumulative share of supply |
|---|---|---|---|
| TGE | Set when KAY9TeamVesting is deployed | 10,000,000 | 1 % |
| +6 months | Set when KAY9TeamVesting is deployed | 40,000,000 | 5 % |
| +12 months | Set when KAY9TeamVesting is deployed | 40,000,000 | 9 % |
TGE
10,000,000 KAY9 · 1 % of supply
Timestamp set at deployment
+6 months
40,000,000 KAY9 · 4 % of supply
Timestamp set at deployment
+12 months
40,000,000 KAY9 · 4 % of supply
Timestamp set at deployment
Enforced by KAY9TeamVesting.unlocked() — three immutable timestamps set in the constructor, and a permissionless release().
Where does the auction ETH go?
Into the pool, all of it. The LBP strategy sweeps the ETH, initializes the v4 pool at the clearing price, mints one full-range position and hands the NFT to KAY9LiquidityLock, which passes it to the Uniswap FeeSplitter. No path returns that principal to an owner address.
- Auction ETHUniswap v4 pool
100 % of the raise
- 455,000,000 KAY9 reserveUniswap v4 pool
Full-range position, paired against the ETH at the clearing price
- LP NFTFeeSplitter — locked
Transferred by KAY9LiquidityLock; no withdrawal path exists
Pool fees, as deployed
- ETH-side fees to the creator address
- 40 %
- ETH-side fees compounded into the position
- 60 %
- KAY9-side fees compounded into the position
- 100 %
Enforced by the Uniswap FeeSplitter, whose splits are immutable configuration. The creator address never receives a share of a trade — it receives a share of the pool fee that the pool has already collected.
Check it. Do not trust it.
Every number on this page is either a constant in a deployed contract or a value read from Robinhood Chain. The ledger shows both, line by line.