Under the hood · plain-English explainer

What is Kasplex?

Kasplex is the indexer and protocol behind every KRC-20 token on Kaspa. It's the reason a Kaspa token needs no smart contract and can't be held by a custodian — it just reads public on-chain data and tallies who owns what. Here's how it actually works.

The 30-second version

The engine that reads Kaspa tokens

Kasplex is a layer built on top of Kaspa's base chain that defines and reads token standards — most importantly KRC-20 (fungible tokens) and KRC-721 (NFTs). Per its own docs it's a third-party, non-profit, open-source project — not part of the core Kaspa protocol.

The key idea: there's no smart contract. To create a token, a deployer broadcasts a standardized deploy operation inscribed into a normal Kaspa transaction; minters then broadcast mint operations. Kasplex's indexer scans every block, applies the protocol rules, and computes balances — which anyone can then read through its public API without running a node.

Because the token logic is an indexer reading public data rather than code that custodies funds, KRC-20 is non-custodial by construction: your tokens sit on the Kaspa BlockDAG under your own keys, exactly like your KAS. That's the foundation the whole Fair-Launch Radar is built on.

Indexer
Reads token ops off the
BlockDAG — doesn't run code
Open-source
Anyone can run it and
verify any balance
Non-custodial
Your tokens stay under
your own wallet keys
How Kasplex works

The three parts of Kasplex

Kasplex isn't one thing — it's a meta-protocol made of three pieces working together on top of Kaspa. Here's what each one does.

✍️

1 · Data insertion

Token actions are inscribed into ordinary Kaspa transactions using Pay-to-Script-Hash (P2SH). This records the deploy/mint/transfer data on-chain without bloating the UTXO set — the token history is public and permanent.

🔎

2 · The indexer

An open-source program scans every block, finds those inscriptions, applies the KRC-20 rules (max supply, per-mint limit, first-come minting) and tallies balances. It doesn't move funds — it just reads and totals what the chain already recorded.

🔌

3 · The APIs

Public endpoints (the mainnet API lives at api.kasplex.org) let any wallet, explorer, or tool query token info, supply, holders and balances without running a full node. This is the data source most Kaspa token apps — including this radar — read from.

The mental model

Kasplex indexer vs a smart contract

Coming from Ethereum, the natural question is "so where's the contract?" There isn't one — and that difference is the whole point.

 Kasplex / KRC-20 (Kaspa)Smart contract / ERC-20 (Ethereum)
What defines the tokenStandardized ops read by an indexerCode deployed to the chain
Who holds your tokensNobody — your own keys, on-chainThe contract's ledger
Attack surfaceNo custom code to exploitContract bugs / malicious functions
Can you verify it yourselfYes — re-run the open-source indexerYes, if you can read Solidity
Cost to launch~1,000 KAS deploy, ~1 KAS per mintGas to deploy + audit costs

Simplified for clarity. Note that Kaspa's Toccata upgrade did add native contract-style programmability at the base layer — but the KRC-20 standard people mint today is still the indexer-read model described here. Always verify a token's parameters on-chain before minting.

Why it matters to you

Public data cuts both ways

The best thing about the Kasplex model is that everything is transparent. Because the indexer only reads public on-chain data, anyone can independently verify a token's supply, its pre-mint, and how concentrated its holders are — no need to trust a single company's word. There's no hidden contract logic and no custodian who can freeze or drain your balance.

But transparency isn't the same as safety. The same open, no-code system that lets an honest team launch in minutes lets a bad actor do it just as fast — and a fair launch and a rug read identically for the first few minutes. The difference is always in the public numbers Kasplex exposes: the pre-mint, the mint progress, the holder spread, the deployer's grip on supply.

That's exactly what our free Fair-Launch Radar does — it reads the same public Kasplex data every wallet sees and grades each live launch A–F, so you don't have to parse raw indexer output yourself. New to the risks? Start with how to spot a KRC-20 rug pull, or see the exact rubric on the methodology page.

Non-custodial goes all the way to the mint.

Because Kasplex holds nothing, minting should never mean handing over custody either. When you mint through the radar, you sign every transaction from your own wallet — and pay a flat 1.75% tool fee instead of the 5% the dominant bots take. Same on-chain token, your keys, nearly 3× less.

1.75%vs 5% on the bots
Questions people search

Kasplex — FAQ

What is Kasplex?

Kasplex is the indexer and protocol that makes KRC-20 tokens work on Kaspa. It's a third-party, open-source project that reads standardized token operations recorded on the Kaspa BlockDAG and tallies them into balances. It defines the KRC-20 (fungible) and KRC-721 (NFT) standards and exposes public APIs so any wallet or tool can query token data without running a full node.

Is Kasplex the same thing as KRC-20?

Related, but not the same. KRC-20 is the token standard — the rules a token follows. Kasplex is the layer that enforces and reads those rules: the protocol that defines the deploy/mint operations, plus the open-source indexer and APIs that turn them into balances everyone can see. KRC-20 is the format; Kasplex is the engine that reads it.

Is Kasplex built by the Kaspa team?

No. Per its own documentation, Kasplex is a separate third-party, non-profit project built on top of Kaspa's base layer, not part of the core Kaspa protocol. Kaspa provides the fast, secure BlockDAG that records the data; Kasplex defines the token meta-protocol and runs the reference indexer and APIs on top of it.

Does Kasplex hold my tokens or my keys?

No. Kasplex is an indexer, not a custodian — it only reads public on-chain data and computes balances. Your KRC-20 tokens live on the Kaspa BlockDAG under your own wallet keys, exactly like your KAS. That's why holding and minting KRC-20 is non-custodial — no contract holds your funds and no indexer can move them.

What is the Kasplex API?

The Kasplex Indexer API lets tools query KRC-20 data — token info, supply, balances, holders, transaction history — over public HTTP endpoints (the mainnet API is at api.kasplex.org), so you can read any token's state without running a node. It's the data source most Kaspa token wallets, explorers, and tools rely on, including this radar's A–F fairness grades.

Do I have to trust Kasplex?

Less than you'd think. Because the indexer is open-source and the underlying operations are all public on the Kaspa BlockDAG, anyone can run their own indexer and independently verify any balance or supply. Kasplex is the convenient reference reader, not a gatekeeper — the truth lives on-chain, which is exactly why fairness can be graded transparently.

Live now

See the Kasplex data, graded

Now you know how KRC-20 tokens are read. Watch the same public Kasplex data turn into live A–F fairness grades — and mint from your own wallet at a flat 1.75%, never custodial.