Casper Network

Casper Network (CSPR) — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

Casper — an L1 blockchain platform with smart contracts on WebAssembly (Wasm) and Proof‑of‑Stake consensus (Zug). The CSPR token is the network’s native currency (gas/staking/validator rewards).

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

What it is: an L1 blockchain for smart contracts and dApps, oriented toward upgrades and enterprise use.
Who it’s for: smart contract/infrastructure developers, validators and delegators, dApp users.
Why onchain/token: CSPR is needed to pay for computation (gas) and for staking in PoS; the onchain state and transaction history are the core of the product.

How it works (very briefly)

The user does: sends a transaction/installs a contract (Wasm) or delegates CSPR to a validator.
The system does: validators in PoS consensus finalize blocks and execute transactions, updating the global state.
The user gets: an executed transaction/state change; when staking — rewards.
Where the blockchain is: the entire product is onchain execution and a verifiable network state.
Token role: CSPR — gas/staking/rewards.

Quick links: AI thesis fit

Project passport

Field	Value
Project name	Casper Network
Also known as (aliases)	Casper \| CSPR
Logo (logo)	../assets/39_casper_logo.svg
Token symbol (ticker)	CSPR
Category	Infra
Primary chain (chain)	Casper
Type	non-EVM
Network status	mainnet
Consensus (consensus)	PoS (Zug)
Launch date (launch_date)	2021
Project status (status)	active
Token (standard)	native
Token contract	—
Token model (token_type)	utility (gas + staking)
Max supply	— (inflationary model; started at 10,000,000,000 CSPR at genesis)
Issuance	inflationary (target annual supply growth rate: 8%)
Tokenomics (tokenomics, brief)	PoS staking by validators/delegators; rewards from inflation; CSPR is used as gas
Governance	—
Admins/keys	—
Audit	yes
Bug bounty	yes
Team (team)	—
Funding (investors/funding)	—
AI component (ai_component)	—
Use‑case (use_case)	Wasm smart contracts for general dApps
DecAI Fit — AI thesis fit	0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary	0 / 3 / 2 / 3
Last verified	2026-02-11

Links (links_*)

Type	Link
Website	https://casper.network/
Docs	http://docs.casper.network/economics
GitHub	https://github.com/casper-network/
Releases / Changelog	https://docs.casper.network/condor/index
Whitepaper	https://casper.network/casper-whitepaper
Roadmap	https://github.com/casper-network/roadmap
Security advisories	https://github.com/casper-network/casper-node/security/advisories
Explorer	https://cspr.live/
X	https://twitter.com/Casper_Network
Discord	https://discord.com/invite/caspernetwork
Telegram	https://t.me/casperblockchain
Medium	https://medium.com/casperblockchain/a16z-licenses-a-practical-guide-e8fed9db9a05
Audit report(s)	https://www.halborn.com/audits/casper-association/casper-20-12a8fb
Bug bounty	https://github.com/casper-network/bounty-program
CoinGecko (profile, reference)	https://www.coingecko.com/en/coins/casper-network
CoinMarketCap (profile, reference)	https://coinmarketcap.com/currencies/casper/

General project overview

Casper is an L1 blockchain whose whitepaper describes a “language‑agnostic smart contracting” approach via WebAssembly (Wasm): developers can use languages that compile to Wasm, and contracts can be updated through the “contract package” mechanism (the ability to upgrade while preserving the entry point).

In the network’s economics, PoS staking by validators and delegators is the basic security mechanism, while computation and storage of resources in the runtime are accounted for via gas. The documentation records that mainnet started with 10 billion CSPR and that the target supply growth rate is 8% per year.

Features/modules

Wasm smart contracts and installation/invocation of contracts as transactions.
Global state (Merkle trie) as the network’s main data layer.
Proof‑of‑Stake (Zug): validators, delegators, epochs (eras), validator auction.
Protocol upgrades (Casper 2.0) and release notes.

Typical scenarios

Scenario 1 (dApp user): signs a transaction → pays gas in CSPR → receives a change of the onchain state.
Scenario 2 (developer): compiles a contract to Wasm → deploys/updates a contract package → interacts with the contract.
Scenario 3 (delegator): delegates CSPR to a validator → receives a share of the rewards (minus the validator’s delegation rate).

Getting started (wallet/network)

What you need: a Casper wallet/keys and access to the network’s RPC/infrastructure.
Network/chain: Casper mainnet.
Fees: gas (accounting of computation/storage) in CSPR; the terms may depend on the network configuration.

Architecture/tech (non‑AI)

Components: nodes (validators/readers), p2p network, consensus, execution engine (Wasm), global state.
Participant roles: validators (stake + block finalization), delegators (add stake to validators), users/developers (transactions/contracts).
Where logic runs: consensus and transaction execution onchain; clients/SDKs offchain.
Dependencies: the ecosystem of tools/SDKs/explorers.

Token/economics (expanded, no forecasts)

Token utility: payment of gas and PoS staking.
Protocol necessity drivers: without CSPR it is impossible to pay for transactions and to participate in consensus security via stake.
Who pays fees: transaction senders.
Where fees/rewards go: validators and delegators receive rewards for participating in consensus; the exact model depends on the protocol rules.
Issuance/burn: an inflationary model with a target 8% annual supply growth is described.
Security/incentive mechanisms: PoS validator auction, rewards, eviction of inactive validators (in the economics docs); the staking doc notes the absence of slashing.
Distribution and token issuance schedule: — (not disclosed in the selected Tier‑1 sources for this card).
Treasury: — (not established).

Governance

Who makes decisions: — (not recorded within this card; some parameters may change through network upgrades/validator votes).
How protocol parameters change: through protocol releases/upgrades (e.g. Casper 2.0).
Where decisions are discussed/made: — (not established).
Keys/multisig: — (not established).

Security and incidents

Audits: a Casper 2.0 audit has been published (Halborn).
Bug bounty: a bounty program exists in the official GitHub repository.
Incidents: — (not established).
Threat model: typical L1 risks: consensus security, vulnerabilities of the execution engine/runtime, upgrade risks.

Project status and timeline

Current status: mainnet; documentation and release notes for Casper 2.0.
Key releases/milestones: Casper 2.0 (Condor) release notes.
Roadmap: in the GitHub roadmap repository.

Ecosystem/integrations

Integrations: explorers (cspr.live), SDKs/infrastructure; developer/validator communities.
Where it’s actually used: as a general‑purpose L1 for dApps and enterprise cases (details depend on the specific applications).

AI component of the project

What is real AI here? In the selected Tier‑1 sources Casper is described as a general‑purpose L1; AI functions/agents/ML modules are not declared as part of the protocol.
What is truly onchain? Consensus, transactions and the global state — fully onchain.
Why is a token needed? CSPR is needed for gas and PoS staking.
Red flags (based on the information found): for the DecAI assessment — the absence of a Tier‑1 AI thesis (ai_score=0), so DecAI Fit = 0 by rule.

DecAI Fit component summary

DecAI Fit: 0/6 — no AI reality and no AI intent (ai_score=0)

Component	Level	Score
AI reality	low	0
Onchain necessity	high	3
Token necessity	medium	2
Evidence	Tier‑1 present (not for AI)	3

Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

AI_0 (decision): 0
Claim (one line): the Tier‑1 sources contain no AI roadmap/AI thesis for Casper as part of the protocol.
Evidence: Tier‑1 — — | No Tier‑1 source on an AI thesis for Casper was found.
Why sufficient / why not (one line): absence of AI positioning in the official docs/whitepaper for the selected pages.
Conflict note (if any): —

AI_1 — what the AI does (1/0)

AI_1 (decision): 0
Claim (one line): no AI component of the protocol is described.
Evidence: Tier‑1 — https://casper.network/casper-whitepaper
Why sufficient / why not (one line): the whitepaper describes Wasm smart contracts and PoS, not AI.
Conflict note (if any): —

AI_2 — demos/examples (1/0)

AI_2 (decision): 0
Claim (one line): no demos of AI functions are described.
Evidence: Tier‑1 — — | No Tier‑1 source on demos of AI functions was found.
Why sufficient / why not (one line): there is no AI object to assess.
Conflict note (if any): —

AI_3 — metrics/quality (1/0)

AI_3 (decision): 0
Metrics: —
Context (version/date/how measured): —
Evidence: Tier‑1 — — | No Tier‑1 source on AI metrics was found.
Why sufficient / why not (one line): there is no AI object to assess.
Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

AI_4 (decision): 0
Claim (one line): a technical description exists, but it is about the L1/consensus/execution, not about AI models.
Evidence: Tier‑1 — https://casper.network/casper-whitepaper
Why sufficient / why not (one line): the AI component is absent.
Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

OC_1 (decision): 1
Chain: Casper mainnet
Addresses/identifiers: — (network/explorer)
Evidence: Tier‑1 — https://cspr.live/
Why sufficient / why not (one line): there is a public explorer of the network.
Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

OC_2 (decision): 1
What useful logic is onchain: execution of transactions/smart contracts (Wasm) and updating of the global state.
Evidence: Tier‑1 — https://casper.network/casper-whitepaper
Why sufficient / why not (one line): onchain logic = the network’s main function.
Conflict note (if any): —

OC_3 — onchain is critical (1/0)

OC_3 (decision): 1
“Replace the blockchain” test: without a blockchain, trustless execution and the verifiable state/history disappear — the product loses its meaning.
Evidence: Tier‑1 — https://casper.network/casper-whitepaper
Why sufficient / why not (one line): this is the basic nature of an L1 smart contract platform.
Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

TK_0 (decision): 0
Claim (one line): the network has a native token, CSPR.
Evidence: Tier‑1 — https://docs.casper.network/concepts/economics/staking
Why sufficient / why not (one line): the staking doc explicitly speaks of the native token CSPR.
Conflict note (if any): —

TK_1 — payment for the service (1/0)

TK_1 (decision): 1
Claim (one line): transactions and contract execution are accounted for via gas paid in the token.
Evidence: Tier‑1 — http://docs.casper.network/economics
Why sufficient / why not (one line): the runtime economics describes gas metering and holds/fee models.
Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

TK_2 (decision): 1
Claim (one line): PoS staking and rewards to validators/delegators.
Evidence: Tier‑1 — https://docs.casper.network/concepts/economics/staking
Why sufficient / why not (one line): staking and rewards are described officially.
Conflict note (if any): —

TK_3 — governance (1/0)

TK_3 (decision): 0
Claim (one line): the use of CSPR as a governance token is not recorded in the selected Tier‑1 pages.
Evidence: Tier‑1 — — | No Tier‑1 source on token governance (CSPR) was found.
Why sufficient / why not (one line): in the selected sources the token is described as gas/staking.
Conflict note (if any): —

TK_4 — token is replaceable (1/0)

TK_4 (decision): 0
Claim (one line): the native token is systemic for gas and PoS.
Evidence: Tier‑1 — https://docs.casper.network/concepts/economics/staking
Why sufficient / why not (one line): gas+staking usually require a native currency.
Conflict note (if any): —

Evidence (table)

Tier	Source	What it proves
Tier‑1	https://casper.network/casper-whitepaper	Wasm smart contracts, PoS model, architecture of the global state/blocks/consensus
Tier‑1	https://docs.casper.network/concepts/economics/staking	PoS staking, native token CSPR; genesis supply 10B; target annual supply growth rate 8%; absence of slashing
Tier‑1	http://docs.casper.network/economics	overview of the economics: consensus/gas/inflationary model (fixed annual percentage rate)
Tier‑1	https://docs.casper.network/condor/index	Casper 2.0 (Condor) release notes and changes (Zug consensus and others)
Tier‑1	https://www.halborn.com/audits/casper-association/casper-20-12a8fb	Casper 2.0 audit (scope/period/remediation status)
Tier‑1	https://github.com/casper-network/bounty-program	existence of a bounty program (repository)
Tier‑1	https://www.casper.network/news/update-on-circulating-supply	methodology of circulating supply and the context of staking/circulation