Skip to main content

Story Protocol

Story Protocol — 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).

Story Protocol — an AI/Other | Infra project on the Story network (EVM‑compatible L1), token: IP.

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 network and a set of modules for registering IP assets, licensing and royalty distribution.
  • Who it’s for: creators/rights holders and application developers who want programmable licenses and payouts.
  • Why onchain/token: a public system of record for rights/licenses and settlements; the IP token is used as gas/staking/settlement currency.

How it works (very briefly)

  1. The user does: registers an IP asset and sets the license terms.
  2. The system does: records the IP object and usage parameters onchain; issues licenses/rights tokens according to the module rules.
  3. The user gets: a verifiable history of ownership/licensing and automated royalty payouts.
  4. Where the blockchain is: the IP asset registry, licensing, royalties/distribution, dispute processes and transaction settlements.
  5. Token role (if any): IP — gas/PoS staking and a utility token for value flows (fees/payouts/incentives).

Quick links: AI thesis fit

Project passport

Field Value
Project name Story Protocol
Also known as (aliases) Story, Story Network
Logo (logo) ../assets/story_favicon.png
Token symbol (ticker) IP
Category AI/Other | Infra
Primary chain (chain) Story
Type Appchain
Network status mainnet
Consensus (consensus) PoS (CometBFT)
Launch date (launch_date) 2025-02-13
Project status (status) active
Token (standard) native
Token contract —
Token model (token_type) utility (gas + staking + governance)
Max supply genesis allocation: 1,000,000,000; thereafter — inflationary emissions
Issuance inflationary + burn (EIP‑1559 base fee)
Tokenomics (tokenomics, brief) IP is used as gas/settlement currency and is staked by PoS validators; part of the fees is burned.
Governance DAO (IP tokenholders; Story DAO + Story Foundation)
Admins/keys —
Audit yes
Bug bounty yes
Team (team) Story Foundation / PIP Labs
Funding (investors/funding) —
AI component (ai_component) AI-native IP infrastructure
Use‑case (use_case) programmable IP + licensing
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 1 / onchain_score 3 / token_score 3 / evidence_score 3
Last verified 2026-02-10

General project overview

Story is a purpose‑built L1 blockchain for intellectual property: it attempts to make IP assets “programmable” (registration, terms of use, licensing, royalties) and thereby reduce friction between creators, rights holders, applications and (in the future) AI agents that consume/produce IP.

The network is EVM‑compatible and is complemented by specialized components/modules for IP structures and processes (licenses, royalties, disputes, etc.).

Features/modules

  • IP Asset and IP Account: registration of IP as an onchain asset (described in the whitepaper).
  • Licensing (PIL / Licensing module): issuance of licenses with usage parameters.
  • Royalties (Royalty module): rules for distributing revenue along the chain of derivative works.
  • Dispute module: the dispute/arbitration process around IP assets.
  • Staking/validators: PoS security of the network and rewards.

Typical scenarios

  • Scenario 1: a rights holder registers an IP asset → sets the license terms → a third party obtains a license and uses the IP with automatic payouts.
  • Scenario 2: an application builds a UX on top of Story → users interact with IP assets/licenses → royalties are distributed according to onchain rules.
  • Scenario 3: a staker delegates IP to a validator → receives rewards after emissions begin.

Getting started (wallet/network)

  • What you need: an EVM‑compatible wallet and access to a Story RPC (via the official network documentation).
  • Network/chain: Story mainnet.
  • Fees: network fees are paid in IP (gas); part of the base fee is burned via an EIP‑1559‑like mechanism.

Architecture/tech (non‑AI)

  • Components: an EVM‑compatible execution environment + a PoS consensus layer on CometBFT/Cosmos SDK; protocol modules for IP assets/licenses/royalties/disputes.
  • Participant roles: users/applications, validators and delegators, rights holders and licensees.
  • Where logic runs: key rules and state — onchain in the Story L1; external checks/attestations and offchain services may complement it (described as an offchain‑sync approach in the whitepaper).
  • Dependencies: the EVM stack (a geth fork as the execution client is mentioned in the docs), the CometBFT consensus engine; cross‑chain interaction via an IBC approach (in the whitepaper).

Token/economics (expanded, no forecasts)

  • Token utility: IP — network gas/fees, a means of settlement within the ecosystem, staking for PoS security; also mentioned as the currency of value flows in the IP economy (whitepaper).
  • Protocol necessity drivers: validators/delegators stake IP; users pay fees in IP; the protocol distributes inflationary rewards and applies slashing for violations.
  • Who pays fees: users/applications performing transactions on the network.
  • Where fees go: the base fee is burned via an EIP‑1559‑like mechanism; the priority fee goes to the proposer; inflationary emissions go to block rewards and the community pool (Tier‑1 docs).
  • Issuance/burn: genesis allocation 1B; annual inflation is set in the docs by the parameter inflations_per_year: 20,000,000; base fee burn per EIP‑1559; the first rewards begin after the “Big Bang Block” (Tier‑1).
  • Security/incentive mechanisms: PoS staking, slashing for double‑sign and downtime; the active validator set (top‑64) receives rewards (Tier‑1 docs).
  • Distribution and issuance: the genesis allocation is distributed among ecosystem participants/the foundation/investors/the team; distribution details are placed in a separate official material (Tier‑1 docs).
  • Treasury: the Foundation states its role of managing/overseeing the treasury and executing DAO decisions (Tier‑1 governance docs).

Governance

  • Who makes decisions: Story DAO (IP tokenholders) with the support of the Story Foundation.
  • How protocol parameters change: parameters/algorithms can be updated via governance or via a hard fork (example: emission parameters in the docs).
  • Where decisions are discussed/made: the official governance section in the documentation and the project forum.
  • Keys/multisig: —

Security and incidents

  • Audits: yes (public reports/materials are collected in the project’s official audits repository).
  • Bug bounty: yes (public program).
  • Incidents: —
  • Threat model: PoS risks (slashing/validators/availability), smart‑contract risks of the IP‑logic modules, governance/upgrade risks.

Project status and timeline

  • Current status: mainnet (public).
  • Key releases/milestones: genesis block (2025‑01‑19, “block 0”); public mainnet launch (2025‑02‑13); the “Big Bang Block” as the start of emissions/staking rewards (expected ~2025‑03‑04, per the official post).
  • Roadmap: available (official forum/doc pages; see links_*).

Ecosystem/integrations

  • Integrations: official bridge, explorer, staking dashboard (within the Story Foundation ecosystem).
  • Partners: —
  • Where it’s actually used: onchain registration/licensing of IP and ecosystem applications (see the official ecosystem portal in the mainnet blog post).

AI component of the project

  • What is real AI here? In Tier‑1 sources, Story is positioned as “AI‑native” infrastructure for IP and describes AI use cases/intentions (including the idea of a future AI‑core), but no Tier‑1 confirmation of a working AI component at the protocol level (model/inference/metrics) was found.
  • What is truly onchain? Story is an L1 network: PoS consensus, smart contracts/modules and state (IP assets, licenses, royalties, staking) live onchain.
  • Why is a token needed? IP — gas and PoS staking, as well as a utility token for settlements and incentives (emissions/rewards/slashing); IP tokenholders figure in governance.
  • Red flags (based on the information found): AI‑washing — moderate risk (a lot of Tier‑1 about AI positioning, but without evidence for AI_1..AI_4); onchain‑washing — low risk (it is an L1); token‑washing — low risk (PoS/gas/emissions are described in Tier‑1).

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality low 1
Onchain necessity high 3
Token necessity high 3
Evidence Tier‑1 present 3
Details

AI reality

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

  • AI_0 (decision): 1
  • Claim (one line): The whitepaper describes AI use cases and even the idea of a future “AI core”, but this is not evidence of a working AI component of the protocol.
  • Evidence: Tier‑1 — https://www.story.foundation/whitepaper.pdf
  • Why sufficient / why not (one line): This is a Tier‑1 declaration of AI direction/applicability and plans, without AI_1..AI_4 artifacts.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): No Tier‑1 confirmation of a specific working AI function/model at the protocol level was found.
  • Evidence: Tier‑1 — https://www.story.foundation/whitepaper.pdf
  • Why sufficient / why not (one line): The document describes AI use cases/intentions but does not record a specific AI subsystem (“what the AI does”) as a product fact.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): No Tier‑1 demos/examples of the protocol’s AI component specifically (inference/model/evaluation) were found.
  • Evidence: Tier‑1 — https://www.story.foundation/whitepaper.pdf
  • Why sufficient / why not (one line): The presence of AI use cases in the whitepaper is not the same as a demonstration of a working AI module.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://www.story.foundation/whitepaper.pdf
  • Why sufficient / why not (one line): No Tier‑1 quality metrics for an AI subsystem/model were found in the sources.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): No Tier‑1 technical description of a specific AI model/versions/pipeline (as a working component) was found.
  • Evidence: Tier‑1 — https://www.story.foundation/whitepaper.pdf
  • Why sufficient / why not (one line): The whitepaper discusses a potential “AI core” as an idea, but without a model/version specification and without evidence of deployment.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Story mainnet
  • Addresses/identifiers: staking contract 0xcccccc0000000000000000000000000000000001 (Story)
  • Evidence: Tier‑1 — https://docs.story.foundation/network/overview ; https://docs.story.foundation/network/learn/token-economy
  • Why sufficient / why not (one line): Tier‑1 docs describe the Story network (L1) and provide onchain identifiers of the key protocol contracts.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: IP assets (IP Assets), licensing (PIL), royalties/distribution, disputes, staking/slashing.
  • Evidence: Tier‑1 — https://www.story.foundation/whitepaper.pdf ; https://docs.story.foundation/network/learn/token-economy
  • Why sufficient / why not (one line): The Tier‑1 whitepaper describes the modular IP logic, and the Tier‑1 docs describe protocol staking/rewards/slashing.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without onchain, the trustless accounting of rights/licenses/royalties and the verifiability of history break down; a “central DB” brings back a trusted intermediary and the risk of rewriting rules/history.
  • Evidence: Tier‑1 — https://www.story.foundation/whitepaper.pdf
  • Why sufficient / why not (one line): The motivation of a “peer‑to‑peer IP network without intermediaries” and onchain enforcement of terms is the central idea of the whitepaper.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a native token, IP.
  • Evidence: Tier‑1 — https://www.story.foundation/whitepaper.pdf
  • Why sufficient / why not (one line): The whitepaper explicitly describes “Story’s native token, IP”.
  • 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): IP is used to pay transaction fees and as the medium of exchange in the protocol.
  • Evidence: Tier‑1 — https://www.story.foundation/whitepaper.pdf
  • Why sufficient / why not (one line): The whitepaper describes IP as the underlying medium of exchange and as fee payments/flows of value.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): Validators stake IP in PoS; there are inflationary rewards and slashing (double sign/downtime).
  • Evidence: Tier‑1 — https://docs.story.foundation/network/learn/token-economy ; https://www.story.foundation/whitepaper.pdf
  • Why sufficient / why not (one line): Tier‑1 docs provide the emission/slashing parameters, and the whitepaper links IP staking to network security.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): Governance is described as the Story DAO with the participation of IP tokenholders.
  • Evidence: Tier‑1 — https://docs.story.foundation/foundation/governance
  • Why sufficient / why not (one line): Tier‑1 governance docs explicitly mention “$IP Tokenholders” and the Story DAO.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): The token is not described as “easily replaceable”: it is embedded in PoS (staking/slashing) and in protocol fees.
  • Evidence: Tier‑1 — https://docs.story.foundation/network/learn/token-economy ; https://www.story.foundation/whitepaper.pdf
  • Why sufficient / why not (one line): Replacing it with an external token breaks part of the PoS protocol mechanisms and the emission/burn design described in Tier‑1.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://www.story.foundation/blog/story-mainnet Public mainnet launch and the launch date (2025‑02‑13); positioning as a “programmable market for IP” tied to AI.
Tier‑1 https://www.story.foundation/blog/big-bang-block Genesis block (2025‑01‑19) and a description of the start of emissions/staking rewards at the “Big Bang Block”.
Tier‑1 https://docs.story.foundation/network/learn/node-software/consensus_layer Consensus layer: Cosmos SDK + CometBFT (Tendermint‑class), connected via ABCI++.
Tier‑1 https://docs.story.foundation/network/learn/token-economy Tokenomics/staking: genesis allocation 1B; inflations_per_year: 20,000,000; burn per EIP‑1559; slashing and the addresses of protocol contracts.
Tier‑1 https://docs.story.foundation/foundation/governance Governance: Story DAO and the role of the Story Foundation; mention of $IP tokenholders.
Tier‑1 https://www.story.foundation/whitepaper.pdf Architecture and protocol modules (IP assets/licensing/royalty/disputes) and the role of the IP token (gas/staking/medium of exchange); AI use cases/AI‑intent.
Tier‑2 — —
Tier‑3 — —

No comments to display

Back to top