use cases

Kaspa application data without rebuilding the indexing layer.

Concrete product surfaces that can use KasGraph once their subgraphs, mappings, and hosted data paths are validated.

example apps

Example apps powered by KasGraph.

These are concrete integration targets for the indexing layer, not claims of existing production deployments.

Problem: Token dashboards need supply, holders, transfers, and activity without custom inscription parsers.

KasGraph provides: Indexed KRC entities, transfer history, holder counts, and GraphQL queries.

example query/output

tokens(first: 10) { ticker holdersCount totalSupply }

Problem: NFT explorers need ownership, transfers, collections, and metadata timelines.

KasGraph provides: Collection and token entity schemas backed by KRC-721 detectors and mappings.

example query/output

collections { id tokenCount ownersCount }

Problem: Covenant apps need to follow spend paths, state transitions, and UTXO lineage.

KasGraph provides: Covenant ID indexing, lineage queries, and BlockDAG-aware history.

example query/output

covenant(id: $id) { transactions { spendPath } currentUtxos { txid } }

Problem: Verifier dashboards need SLA bonds, signatures, deadlines, releases, and slashes.

KasGraph provides: App-specific subgraphs with typed entities and POI-backed checkpoints.

example query/output

bonds(where: { status: ACTIVE }) { id deadline verifier }

Problem: Agents should not scrape explorers or infer raw RPC responses.

KasGraph provides: MCP tools for schema discovery, query execution, pattern search, and lineage reads.

example query/output

get_covenant_lineage({ covenantId: "cov_..." })

Problem: Wallets need fast access to balances, token holdings, activity, and app state.

KasGraph provides: Indexed wallet-facing entities, asset balances, transfer history, and subscriptions.

example query/output

wallet(address: $addr) { assets { id balance } transfers { hash } }