karatscan
Check a token
Kaspa mainnet · post-Toccata

Know what a Kaspa token can do to you.

Karat recompiles every KCC20 contract locally and grades what the chain proves — mint authority, supply, ownership, and identity.

try
The scan

Every flag opens into its evidence.

assayed at daa 515,802,657
$KRONKCC20
Kron Token
Karat grade
24K
Supply provably fixed. Mint allowance exhausted.
Assessed at DAA score 515,802,657. This grade describes state at that score and nothing after it.
supply420,000,000
allowance0
templatekron-native · template_verified
mintercontroller covenant
genesisdaa 496,018,626
deployerc01583…3e21
Checksclick a row for on-chain evidence
Karat never labels a token safe. It reports which properties were observed, and at which DAA score.
94
tokens indexed
64
graded 24K
0%
mint unbounded
0
ticker collisions
The scale

One number. No interpretation needed.

24K
Supply provably fixed. Mint allowance exhausted.
bytecode matches template · program revealed · allowance = 0 · image_hash present
22K
Mint capped by a controller covenant. Remaining amount shown.
as 24K, but allowance > 0 held by a controller covenant
18K
Standard contract, but one key can mint without limit.
registry match · minter branch owned by a pubkey
14K
Custom contract. Readable, not yet reviewed.
no registry match · logic readable · unassayed
Plated
Program never revealed on chain. Nobody can audit it.
P2SH commitment only · no preimage published
Counterfeit
Ticker collides with a higher-graded token. Possible impersonation.
ticker match against a token holding a higher grade
A minter cannot stop being a minter. An allowance of zero is the only proof of fixed supply.
01

Recompiled, not scraped

Every contract is rebuilt with silverc and matched byte-for-byte against a versioned template registry.

02

Every claim links to chain

No finding without an outpoint, a payload, or a transaction you can open yourself.

03

Free API, open rules

The grading engine and the registry are public. Embed the badge anywhere, no key required.

Roadmap

Registry first, brand later.

Phase 0
The original
18 Aug → 07 Sep 2026
BuildTemplate Registry v0: compile kcc20.sil across constructor parameter sets, extract prefix, suffix and hash, assign versions. MIT repo, karat-registry.
BuildLight indexer reading from a node plus the kcc20.info and kascov APIs, decoding all four state fields of every mainnet KCC20 UTXO.
ShipReport: State of KCC20 — September 2026. How many tokens, how many revealed the program, how many still hold a pubkey minter branch.
Exit · Report published and circulating in the core community
Not doing · No website, no logo, no marketing
Phase 1
Public scanner
08 Sep → 15 Oct 2026
Shipkarat.scan goes live: a page per token, the Karat grade, and clickable on-chain evidence behind every flag.
ShipEmbeddable badge (iframe and SVG) so projects can carry their grade on their own site.
ShipPublic API v0, no key required, and a Vietnamese guide: read a KCC20 token in five minutes.
Exit · Three external sites embed the badge
Not doing · Price charts, portfolio tracking, wallet labels
Phase 2
Distribution and token
16 Oct → 30 Nov 2026
ShipTelegram bot alerting on every new token with its Karat grade the moment genesis appears.
PartnerGrading inside KRON's launchpad flow, pre-signature warnings in Kaspire, listings surfaced in KaspaCom.
BuildDeploy $KARAT with the allowance exhausted in the final transaction — the first 24K token on mainnet, product as exhibit.
Exit · One signed integration
Not doing · Token as a revenue source
Phase 3
Revenue
01 Dec 2026 → 28 Feb 2027
RevenueAPI tiers: free for individuals, metered for launchpads, wallets, bots and exchanges.
RevenueKarat Certified: pre-sale review for a project, one-time fee, report published publicly.
RevenueContinuous monitoring subscription: alerts when a token's state changes — new mint, large wallet movement.
Exit · First paying customer before 31 January
Not doing · Private findings, paid grade upgrades
Phase 4
Becoming the standard
Q1 – Q2 2027
StandardPublish the KCC20 metadata and safety specification as a community standard, into a standards track if it is taken up.
BuildShip safe contract variants (Capped, Renounceable) — none exist today beyond the reference implementation.
ExtendMove into KCC721 once the NFT covenant proposal matures.
Exit · A third party ships against the spec
Not doing · Forking the ecosystem with a competing standard
API

Public v0. No key.

One endpoint per token, one per registry template. Free for individuals, metered for launchpads, wallets, bots and exchanges. Every response carries the DAA score the assessment was made at.

GET/v0/token/:ticker
GET/v0/token/:ticker/checks
GET/v0/registry/templates
GET/v0/badge/:ticker.svg
WS/v0/stream/genesis
$curl https://api.karat.scan/v0/token/KARATcoming soon
{
  "ticker": "KARAT",
  "grade": "24K",
  "assessed_at_daa": 412908331,
  "template": {
    "name": "kcc20.sil",
    "version": "v0.3.1",
    "bytecode_match": true
  },
  "supply": {
    "minted": "21000000",
    "mint_allowance": "0",
    "allowance_exhausted": true
  },
  "minter_branch": "controller_covenant",
  "program_revealed": true,
  "metadata": { "image_hash": "sha256:9c1f…d0a7" },
  "ticker_collisions": [],
  "disclaimer": "State observed at the given DAA score only."
}

Running a launch? Put the grade on your page.

<script src="karat.scan/badge.js">
September 2026

State of KCC20: how many tokens exist, how many revealed their program, how many still let the deployer mint without limit.

One email when the report lands, then a weekly note. No token sale.
Karat reports what the chain proves. It never certifies intent.
GitHubX