Skip to content

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.

KAY9, the watchdog mascot, inside its brass ring
block
…
token
not deployed
pool
not launched
audit
not deployed

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
—

In the last 8 minutes of chain time.

Reached a real pool
—

The ones people can actually buy.

Launch sources active
—

Of the sources this browser pass reads.

reading…

  •  
  •  
  •  
  •  

Rows with a score were scanned by this browser, in the order the watchdog would take them: what people can already buy first. The rest have only been detected, and KAY9 has no opinion about them. A token appearing here is neither a warning nor a recommendation.

No wallet is needed for any of this. Every reading in the table is made by your own browser against a public node, kept in this browser for a day so a reload does not repeat it, and sent nowhere.

Live feedScan a token yourself

Scan before you buy.

Every launch the feed picks up is checked in your own browser before you trust it. The verdicts that matter are written to the chain, where nobody can edit them.

WatchdogSee the roadmapWatch the demo

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 token

For 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 token

For 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 registry

KAY9 is on the buyer's side. Everything else follows from that.

Questions people ask about KAY9

What is KAY9?

KAY9 is an on-chain watchdog for Robinhood Chain (chain id 4663). It finds new token launches, runs a free automatic scan and records the results in a public contract, KAY9ScanRegistry, before anyone asks. Anyone can also scan any token free, in their own browser. $KAY9 is the project's fixed-supply token; the watchdog runs without it.

How do I check a Robinhood Chain token before I buy it?

Open the audit page, paste the token's contract address and run the basic scan. It runs in your browser against a public Robinhood Chain node: no wallet, no sign-up and no fee, and nothing is sent to a KAY9 server. It shows who can mint more of the token, whether anyone can freeze your balance, how concentrated the holders are and which wallet launched it.

Does a KAY9 scan or audit cost anything?

No. The basic scan and the watchdog's automatic scans are free. Deeper audits are not sold either: you lock KAY9 in KAY9AccessVault to open an access period, and the full amount comes back when the lock ends. There is no fee, no yield and no price per audit.

Does KAY9 tell me a token is safe?

No. A KAY9 result is a technical risk reading of one token at one block, never a safety guarantee or investment advice. Scores run from 0 to 100, where higher means fewer risks were found, and every result names the block it was measured at and the evidence behind it. When a scan cannot measure enough, it says "Insufficient data" instead of giving a score.

Where are KAY9 results stored?

On Robinhood Chain. The watchdog's scans are committed to KAY9ScanRegistry, and a deep audit is appended to KAY9Registry once two of three independent auditors have signed the same result. Nothing is overwritten: a newer result is added beside the older one, so the history stays checkable.

Can a token's creator pay for a better score?

No. Paying nothing and declaring nothing can change a score. A creator who requests an audit of their own token gets the same engine and the same scoring as anyone else, and the report records who asked for it.

Where this is going

The launch is set for Tuesday 10 November 2026 and gated on fourteen conditions anyone can check. Every date sits on one line, counted down to the day.

See the roadmap

Target launch

…

A target, not a promise: if a gate is still open on the date, the date moves.

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.

How it works, step by step

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

See what will be deployed

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.

Robinhood Chain carries the on-chain record. BNB Chain and Solana are scanned in your browser today through the shipped adapters, but nothing about them is written on-chain yet. Later chains are drawn in outline because they are planned, not shipped.

KAY9 coreEVM adapterSolana adapterRobinhood 4663liveBNB Chain 56basic scanLater EVM chainsplannedSolana mainnetbasic scan

What runs where

The website is a window. If it disappears, everything below still works and anyone can build another one.

ClaimWhere it lives
Basic checksyour browser, public RPC
Requesting an auditKAY9AuditHub.requestAudit
Your accessKAY9AccessVault
Your remaining allowanceKAY9AccessVault.consume
Deep and forensic analysisthree auditor jobs, run separately
Agreement between auditorsKAY9AuditHub.attest, 2 of 3
The committed resultKAY9Registry.recordReport
Every past resultKAY9Registry, append-only
The full reportIPFS, hash committed on-chain
This websitestatic 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. The three keys are held by three people in three countries, and two of them, the developer and the owner, are the project, so the project can still reach a quorum on its own. What changed is that no one person can. Moving a second key outside the project 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.

What has to be true first

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.

The full tokenomics

  1. 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.

  2. 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.

  3. 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

Total supply

1,000,000,000

KAY9

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.

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.

0 %3 %6 %9 %1 %TGE5 %+6 months9 %+12 months

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 ETH
    Uniswap v4 pool

    100 % of the raise

  • 455,000,000 KAY9 reserve
    Uniswap v4 pool

    Full-range position, paired against the ETH at the clearing price

  • LP NFT
    FeeSplitter — 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.