Skip to main content

Phantasma

Phantasma (SOUL, KCAL) — 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).

Phantasma — an L1 / NFT / Gaming blockchain network (oriented toward games, Smart NFTs and dApps) with a dual‑token model: SOUL (governance + staking) and KCAL (resource/fee token).

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 games and Smart NFTs, plus an ecosystem of wallets/SDKs/tools.
  • Who it’s for: game and dApp developers, creators of collections/marketplaces, ecosystem users.
  • Why onchain/token: the tokens are used for network security (staking/validators), governance and payment for transactions/operations (via KCAL).

How it works (very briefly)

  1. The user does: sends transactions, mints/transfers NFTs, interacts with dApps via a wallet/Link.
  2. The system does: validates transactions via a PoS model with block producers; executes onchain logic (NFTs/contracts) and updates the network state.
  3. The user gets: ownership of assets (NFTs/tokens), fast operations, access to dApps and tools.
  4. Where the blockchain is: asset ownership/transaction accounting/NFT rules and part of the protocol logic are executed onchain.
  5. Token role (if any): SOUL — staking/governance, generation of KCAL; KCAL — a resource for fees/operations.

Quick links: AI thesis fit

Project passport

Field Value
Project name Phantasma
Also known as (aliases) Phantasma Phoenix; SOUL; KCAL
Logo (logo) ../assets/211_phantasma_logo.webp
Token symbol (ticker) SOUL (governance/staking) + KCAL (fee/resource)
Category L1 | NFT | Gaming
Primary chain (chain) Phantasma
Type non-EVM
Network status mainnet
Consensus (consensus) PoS variant with Block Producers (validators via voting/staking)
Launch date (launch_date) 2019
Project status (status) active (with the Phoenix upgrade program)
Token (standard) native
Token contract native: —; ERC‑20 (wrapper/representation): 0x75858677e27C930FB622759FeafFeE2b754Af07F (Etherscan)
Token model (token_type) utility (governance + staking (SOUL); fee + resource (KCAL))
Max supply SOUL: initial max supply 94,000,000 (whitepaper), with inflation provided for thereafter; KCAL: a resource token, its issuance is tied to staking
Issuance inflationary (SOUL: 3%/year + 125,000 SOUL/month for Soul Masters per the whitepaper)
Tokenomics (tokenomics, brief) staking SOUL generates KCAL; Soul Masters (≥50k SOUL) receive additional rewards (whitepaper)
Governance onchain governance (polls; community/BP) described in the whitepaper
Admins/keys unknown (no description of administration keys found in public Tier‑1 materials)
Audit partially: a repo with the TGE audit/reports (not an audit of the current protocol/smart contracts)
Bug bounty unknown (no public bug bounty program found in Tier‑1)
Team (team) the project and the community; the website mentions “under the stewardship of GOATi Entertainment” (see Evidence)
Funding (investors/funding) unknown
AI component (ai_component) none (NFT/gaming L1)
Use‑case (use_case) Smart NFTs, gaming dApps, storage, swaps
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

General project overview

Phantasma is a separate L1 network positioned as infrastructure for games, “Smart Digital Assets (Smart NFTs)” and dApps. The key idea is to give developers and users a “gaming” UX (wallets, Link integrations, SDKs) while providing onchain ownership of assets and the rules of their circulation.

The whitepaper describes: scaling via side chains (each dApp can run on its own side chain), a dual‑token model (SOUL + KCAL), onchain governance, built‑in oracles and decentralized data storage (storage at the block producers). On the website, the project also emphasizes “Smart NFT” capabilities (ROM/RAM layer, on‑demand minting, nested/infused NFTs) and plans for cross‑chain swaps/interoperability (roadmap 2025–2026).

Features/modules

  • Dual token system: SOUL (governance/staking) + KCAL (energy/fees).
  • Staking: staking SOUL generates KCAL; additional roles/rewards for large stakers (Soul Masters) per the whitepaper.
  • Block Producers (validators): a PoS variant with selection/rotation of block producers and voting (whitepaper).
  • Smart NFTs / Smart Digital Assets: extended NFT functions (multi‑layer, ROM/RAM, on‑demand minting, nesting, etc.) are described on the website.
  • Onchain governance: parameterizable rules and polls for the network (whitepaper).
  • Developer tooling: dev documentation (GitBook), an SDK/Link client (docs) and wallets (website).
  • Storage & oracles (per the whitepaper): decentralized storage at the validators and a built‑in oracle subsystem.

Typical scenarios

  • Scenario 1: a developer integrates a game → mints/manages Smart NFTs → players get onchain ownership and trading of assets.
  • Scenario 2: a user stakes SOUL → receives KCAL → pays for network operations (transfers/minting/interaction with dApps).
  • Scenario 3: the community takes part in governance processes → votes on parameters/validators (polls are described per the whitepaper).

Getting started (wallet/network)

  • What you need: an ecosystem wallet (for example, Poltergeist Lite / Ecto / Pavillion Hub per the website) or integration via Phantasma Link (docs).
  • Network/chain: Phantasma (Phoenix) mainnet.
  • Fees: network operations require the KCAL resource token (website; the dual‑token system is also described in the whitepaper).

Architecture/tech (non‑AI)

  • Components: the L1 network + validators (block producers), wallets, Link/SDK for applications, explorer; per the whitepaper — main chain + side chains, oracles and a storage layer.
  • Participant roles: users; SOUL stakers; block producers (validators); dApp/game developers.
  • Where logic runs: the core logic of asset ownership/transactions and the protocol rules — onchain in Phantasma; client applications/UX — offchain.
  • Dependencies: RPC/wallets; per the whitepaper, oracles and cross‑chain interoperability are provided for; per the roadmap — plans for cross‑chain swaps (ETH/BNB/NEO/CAS, etc.).

Token/economics (expanded, no forecasts)

  • Token utilities: SOUL — governance/staking; KCAL — a resource token for paying fees/operations (whitepaper + website).
  • Protocol necessity drivers: staking SOUL is tied to security/participation (validators and voting) and to the generation of KCAL; KCAL is needed for transactions (dual‑token model).
  • Who pays fees: users/applications when performing operations (payment in KCAL).
  • Where fees go: the whitepaper describes a validator reward model (including a share of fees) and the distribution of inflation; the exact current implementation/parameters may differ from the 2019 version (requires separate verification against the current protocol docs/releases).
  • Issuance/burn: per the whitepaper, inflation is described for SOUL: 3%/year + 125,000 SOUL/month for Soul Masters; KCAL is generated by staking SOUL.
  • Security/incentive mechanisms: PoS validators (block producers) and staking; the whitepaper describes Active/Standby roles and the distribution of rewards.
  • Distribution and token issuance schedule: current distribution/vesting tables were not extracted; to assess centralization, data on genesis/treasury/distribution needs to be collected separately from official materials.
  • Treasury: the whitepaper mentions a treasury for the “Phantom Force Foundation” (developer community) with a monthly inflow (within the inflationary model); specific addresses/the management process require separate verification.

Governance

  • Who makes decisions: per the whitepaper, onchain polls are provided for, including community polls and block producer polls.
  • How protocol parameters change: the network rules are parameterizable and can be changed onchain when consensus is reached in a poll (whitepaper).
  • Where decisions are discussed/made: the project’s official channels (blog/social media/Discord); formalized governance pages were not extracted.
  • Keys/multisig: unknown (no description found in public Tier‑1 materials).

Security and incidents

  • Audits: the PhantasmaAudit repo contains materials on the audit/reporting of the token generation event (TGE) and report generation tools; this is not a universal audit of the current protocol components.
  • Bug bounty: unknown.
  • Incidents: public post‑mortems/incidents were not collected.
  • Threat model: the risks are typical for L1 networks: consensus/validator security, protocol upgrades, bridges/wrappers on other networks, security of wallets/Link integrations.

Project status and timeline

  • Current status: mainnet; the website positions the current phase as “Phantasma Phoenix”.
  • Key releases/milestones: network launch — 2019 (whitepaper/website); then — a series of upgrades (see the blog and roadmap).
  • Roadmap: a 2025–2026 roadmap has been published (Phoenix chain upgrade, wallets, API/Explorer v2, cross‑chain swaps, etc.).

Ecosystem/integrations

  • Integrations: wallets (Poltergeist Lite, Ecto, Pavillion Hub) and Link integrations; dev documentation/SDK; explorer.
  • Partners: partnerships were not catalogued (see the blog for announcements).
  • Where it’s actually used: use‑case — a gaming/NFT ecosystem; examples of dApps and solutions are listed on the website (Solutions/Games/Marketplace sections).

AI component of the project

  • What is real AI here? An AI component is not claimed as part of the product/protocol in Phantasma’s Tier‑1 materials.
  • What is truly onchain? The Phantasma L1 network: transactions, ownership of tokens/NFTs and the network’s protocol rules.
  • Why is a token needed? SOUL — staking/governance; KCAL — resource/fees for network operations.
  • Red flags (based on the information found): AI‑washing — not relevant; onchain‑washing — not relevant (it is the blockchain itself); token‑washing — low (the tokens are protocol‑level: staking/fees).

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 3
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): in Phantasma’s roadmap/whitepaper, AI functionality is not claimed as a product goal.
  • Evidence: Tier‑1 — https://phantasma.info/phantasma-phoenix-unveils-exciting-2025-2026-roadmap/ ; https://phantasma.info/wp-content/uploads/2020/09/phantasma_whitepaper_en.pdf
  • Why sufficient / why not (one line): the materials describe blockchain features (NFTs, swaps, API), but not an AI roadmap.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): an AI component (models/agents/inference) is not part of the Phantasma protocol per Tier‑1.
  • Evidence: Tier‑1 — https://phantasma.info/blockchain/ ; https://phantasma.info/wp-content/uploads/2020/09/phantasma_whitepaper_en.pdf
  • Why sufficient / why not (one line): blockchain mechanisms and NFT features are described without AI.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): no public AI demos are claimed as part of Phantasma.
  • Evidence: Tier‑1 — https://phantasma.info/blockchain/
  • Why sufficient / why not (one line): the product page lists wallets/NFTs/roadmap without an AI demo.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://phantasma.info/wp-content/uploads/2020/09/phantasma_whitepaper_en.pdf
  • Why sufficient / why not (one line): there are no AI metrics in the whitepaper, because no AI component is described.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): the technical description relates to the blockchain architecture (side chains, PoS validators, dual‑token), not AI.
  • Evidence: Tier‑1 — https://phantasma.info/wp-content/uploads/2020/09/phantasma_whitepaper_en.pdf
  • Why sufficient / why not (one line): there is no object of verification for an “AI architecture”, since AI is not claimed.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Phantasma (Phoenix) mainnet; an ERC‑20 SOUL token is also present on Ethereum as a representation.
  • Addresses/identifiers: Explorer: https://explorer.phantasma.info/en ; ERC‑20: 0x75858677e27C930FB622759FeafFeE2b754Af07F
  • Evidence: Tier‑1 — https://phantasma.info/blockchain/ ; https://explorer.phantasma.info/en ; https://etherscan.io/token/0x75858677e27C930FB622759FeafFeE2b754Af07F
  • Why sufficient / why not (one line): there are official links to the explorer and a public token record in the explorer.
  • Conflict note (if any): the ERC‑20 address is not Phantasma’s “primary chain”, but a separate representation on Ethereum.

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

  • OC_2 (decision): 1
  • What useful logic is onchain: the network’s L1 logic: transactions, asset ownership, Smart NFTs and protocol mechanisms (staking/governance) are described in the whitepaper/on the website.
  • Evidence: Tier‑1 — https://phantasma.info/wp-content/uploads/2020/09/phantasma_whitepaper_en.pdf ; https://phantasma.info/blockchain/
  • Why sufficient / why not (one line): this is a full‑fledged L1 with onchain logic beyond “just a token”.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without the blockchain the whole product breaks down: there would be no onchain ownership/transfers of assets and no consensus/validation.
  • Evidence: Tier‑1 — https://phantasma.info/wp-content/uploads/2020/09/phantasma_whitepaper_en.pdf
  • Why sufficient / why not (one line): Phantasma is the blockchain network itself; onchain is the core here.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): Phantasma has the SOUL and KCAL tokens (dual‑token).
  • Evidence: Tier‑1 — https://phantasma.info/wp-content/uploads/2020/09/phantasma_whitepaper_en.pdf ; https://phantasma.info/blockchain/
  • Why sufficient / why not (one line): the tokens are described as protocol‑level (staking/governance and fees).
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): network operations are paid for with the KCAL resource token; SOUL is used via staking to obtain KCAL.
  • Evidence: Tier‑1 — https://phantasma.info/wp-content/uploads/2020/09/phantasma_whitepaper_en.pdf ; https://phantasma.info/blockchain/
  • Why sufficient / why not (one line): the dual‑token model explicitly describes KCAL as a fee/resource token.
  • Conflict note (if any): the specific parameters of the fee model depend on the current network version.

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

  • TK_2 (decision): 1
  • Claim (one line): staking SOUL is linked to the role of validators (block producers) and rewards (including inflation/fees); large stakers (Soul Masters) have separate rewards.
  • Evidence: Tier‑1 — https://phantasma.info/wp-content/uploads/2020/09/phantasma_whitepaper_en.pdf
  • Why sufficient / why not (one line): the whitepaper describes roles/rewards linked to staking and validation.
  • Conflict note (if any): the penalty/slashing mechanics is not detailed in the extracted fragment.

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): SOUL is used for onchain governance: voting for block producers and network parameters.
  • Evidence: Tier‑1 — https://phantasma.info/wp-content/uploads/2020/09/phantasma_whitepaper_en.pdf
  • Why sufficient / why not (one line): the whitepaper directly describes governance polls and stake‑based voting power.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): protocol tokens for staking/governance/fees are hard to replace without changing the L1 architecture.
  • Evidence: Tier‑1 — https://phantasma.info/wp-content/uploads/2020/09/phantasma_whitepaper_en.pdf
  • Why sufficient / why not (one line): the dual‑token system and PoS validators are described as basic mechanisms of the network.
  • Conflict note (if any): the economy could theoretically be replaced with a different model, but that would be a different protocol.

Evidence (table)

Tier Source What it proves
Tier‑1 https://phantasma.info/wp-content/uploads/2020/09/phantasma_whitepaper_en.pdf L1 architecture, consensus (a PoS variant with block producers), dual‑token (SOUL/KCAL), staking, governance and economics (as of the document version).
Tier‑1 https://phantasma.info/blockchain/ Product positioning (gaming/NFT), wallets/Link, description of the role of SOUL/KCAL, basic FAQ (including PoS and the 2019 launch).
Tier‑1 https://phantasma.gitbook.io/developers/ The existence of dev documentation/tools for developers (GitBook).
Tier‑1 https://phantasma.info/phantasma-phoenix-unveils-exciting-2025-2026-roadmap/ Roadmap 2025–2026: Phoenix upgrade, API/Explorer v2, cross‑chain swaps, etc.
Tier‑1 https://github.com/phantasma-io/PhantasmaAudit Repository with materials/a tool for the TGE audit (.csv reports and a generator).
Tier‑2 https://www.coingecko.com/en/coins/phantasma Reference profile (prices/market/links); does not confirm technical claims.
Tier‑3 https://coinmarketcap.com/currencies/phantasma/ Reference aggregator, not a Tier‑1 source on architecture/tokenomics.

No comments to display

Back to top