Skip to content
KAY9

How it works

Two sequences. One turns an audit request into a verdict on the chain. The other turns a token into a market with liquidity nobody can withdraw.

English governs the contract statements on this page. Contract names, addresses and numbers are shown as they are on the chain.

The audit sequence

Two of the five steps are transactions. Three happen in operator daemons that KAY9 does not control and cannot vouch for — which is exactly why the result has to arrive with a quorum of signatures before the chain will accept it.

off-chain — operator daemonsDetectAnalyzeSignon-chain — Robinhood ChainrequestAuditspends one allowance unitsubmitResultquorum signaturesKAY9Registry — append onlyYou

  1. 1Request

    You call requestAudit with a chain key, an asset id and the tier. The hub asks KAY9AccessVault whether you hold a live period of at least that tier with allowance left, and the vault, not this website, is what decides. If it does, one allowance unit is debited and AuditRequested is emitted. No KAY9 moves.

    On Robinhood Chain

  2. 2Detect

    Three auditors read AuditRequested on a schedule. There is no queue, no always-on server and no allow-list of requesters — the event is the whole coordination mechanism, and each auditor pins its analysis to the block the chain recorded, so all three read the same history.

    Off-chain, in the operator daemons

  3. 3Analyze

    The watchdog engine reads the target chain through its adapters, computes the seven risk dimensions and the flags bitmask, and writes a canonical JSON report. Every finding carries evidence and a confidence; the engine never claims intent.

    Off-chain, in the operator daemons

  4. 4Sign

    Each auditor pins the report, hashes it, and signs the EIP-712 AuditResult with its own key. An auditor signs only the result it computed itself. This is the only part of the protocol you have to take on trust, and the quorum threshold is what bounds it.

    Off-chain, in the operator daemons

  5. 5Commit

    Each auditor's answer is recorded as it arrives. The moment one result has threshold-many signatures from auditors still in the active set, the hub appends it to KAY9Registry for good. If three auditors report three different results, agreement is out of reach and the job is marked disputed on-chain instead, with the allowance unit returned.

    On Robinhood Chain

The launch sequence

Every step after the owner’s single signature is permissionless. If the team disappears halfway through, a stranger can finish the launch.

See the live launch state

Auction455 M KAY9, 4 h, native ETH1GraduationcurrencyRaised ≥ required2Migrationanyone calls migrate()3Lockanyone calls lock()4

  1. 1Auction

    A continuous clearing auction sells 455,000,000 KAY9 for native ETH over roughly four hours (1,200 blocks). Anyone can bid; the same auction is listed on the Uniswap app. There is no whitelist because validationHook is the zero address, and KAY9Genesis asserts that before the auction is created.

  2. 2Graduation

    The auction graduates when currencyRaised reaches requiredCurrencyRaised. If it does not, bidders refund themselves with exitBid, the whole 455 M returns to the launch vault, and the owner may configure a new launch 48 hours later.

  3. 3Migration

    After the migration block, anyone can call LBPStrategy.migrate. The strategy sweeps the ETH, initializes the v4 pool at the clearing price with a 1 % fee and tick spacing 200 and no hook, mints one full-range position with 100 % of the ETH and up to 455 M KAY9, and sends the LP NFT to KAY9LiquidityLock.

  4. 4Trading

    Anyone calls lock(tokenId). The lock registers the creator-fee beneficiary while it still owns the NFT, then transfers it to the Uniswap FeeSplitter, where the principal is irrecoverable. Unsold tokens are settled into a single-sided position above the price, or burned if they are below the dust threshold.