The holder lane · metered tool endpoints

5× capacity for verified holders.

Verified $KASCOV holders get five times the published anonymous capacity on kascov’s metered tool endpoints: preflight, compile, simulate, zk-verify, publish and prove-holding — and, when the public engines are all busy, a few engines kept back for the lane. That is the whole feature: more room, for people who proved an address. Plain data reads are free for everyone, are not metered, and need no lane. Nothing else on this site knows or cares whether you hold anything.

One signature, one token

Mint your lane token.

Your wallet signs a one-time phrase; kascov checks the balance from chain and answers with the token. The page never sees a key.

Your wallet signs a one-time phrase of the form kascov lane: <address> <nonce>. The signature proves the address is yours; kascov checks the balance from chain and answers with the token.

Minting a lane pass is a public act: your address, tier and mint date are published in the lane ledger, and each time the mainnet anchor runs its payload commits to the ledger’s merkle root next to the passport root (how to check both). The pass itself stays private — the ledger records that a pass exists, never the pass.

Looking for a wallet…

Use it

Send the token in the X-Kascov-Lane header on any of the metered tool endpoints. Without the header the same request still works — it just rides the anonymous tier. The header does nothing on plain data reads, because those are never metered.

curl -X POST -H 'X-Kascov-Lane: <lane token>' \ -H 'content-type: application/json' -d '{…}' \ 'https://kascov.io/data/mainnet/preflight'

Signing a message is free and moves no funds. It cannot authorise a transaction. kascov will never ask for your seed phrase or private key, and this page never sees either. If anything asks you for one, it is not us.

Privacy: the mint call sees the address you chose to prove and one signature, verifies both, publishes one line in the public lane ledger — your address, tier and mint date — and drops the rest. The pass itself and your signature are never stored; a request carrying the header reveals the token, not your Discord and not your history. Your address and its balances were already public on chain before any of this.