Skip to main content

Streamr

Streamr — 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).

Streamr — an Infra / Data / DePIN project: a P2P network for publishing and subscribing to real‑time data (streams); token: DATA.

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: a decentralized “message broker” network for real‑time data (publish/subscribe).
  • Who it’s for: developers and projects that need streaming data exchange without a centralized broker; node operators.
  • Why onchain/token: DATA is used for node staking/delegation and incentivization, as well as for governance and some payments at the application level (Hub).

How it works (very briefly)

  1. The user does: publishes messages to a stream and/or subscribes to a stream.
  2. The system does: nodes in the P2P network deliver messages along the stream topology.
  3. The user gets: scalable/resilient delivery of messages in real time.
  4. Where the blockchain is: onchain contracts are used for the incentive mechanics (Sponsorship/Operator/Delegation), as well as for governance.
  5. Token role (if any): DATA is a “stake/work/governance” token for nodes and tokenomics participants.

Quick links: AI thesis fit

Project passport

Field Value
Project name Streamr
Also known as (aliases) Streamr Network, DATA
Logo (logo) ../assets/172_streamr_logo.png
Token symbol (ticker) DATA
Category Infra | Data | DePIN
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract Ethereum: 0x8f693ca8d21b157107184d29d398a8d082b38b76
Token model (token_type) utility (payments + staking + governance)
Max supply 1,312,523,352 DATA (max total supply, per the explorer)
Issuance fixed (per max supply)
Tokenomics (tokenomics, brief) Sponsorships pay operators; delegators fund operators’ stake; there is a protocol fee in profit sharing
Governance governance by DATA token holders (SIPs, Snapshot)
Admins/keys —
Audit yes (list of audits/papers on the whitepapers page)
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) none (data streaming infrastructure)
Use‑case (use_case) P2P publish/subscribe for realtime data
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 1 / 2 / 2 / 2
Last verified 2026-02-11

General project overview

Streamr Network is a P2P network for publishing and subscribing to real‑time data. In the documentation, Streams are described as “topics” in a publish/subscribe system, and the network’s task is to deliver messages to all subscribers of a specific stream. At the tokenomics level, Streamr uses onchain contracts (Operator/Sponsorship, etc.) to create incentives for “good” and resilient nodes and to reduce the problems of free‑riders/malicious participants.

Note on networks (passport normalization): the passport lists Ethereum as the primary chain (per the token). The mention of Polygon PoS in the documentation refers to the staking/delegation contracts and remains in the text as context.

Features/modules

  • Streams (topics): named message streams; an SDK/CLI is available for working with them.
  • P2P nodes: nodes form topologies and relay messages.
  • Incentives / tokenomics: Sponsorships pay for delivery quality; operators stake DATA, delegators fund operators.
  • Governance: decisions via DATA holders (SIPs; Snapshot).

Typical scenarios

  • Scenario 1 (dApp messaging): an application publishes events/state to a stream → users/services subscribe → receive the events without a centralized broker.
  • Scenario 2 (node operator): an operator runs a node and stakes DATA in a Sponsorship → earns rewards for “relaying”.
  • Scenario 3 (delegator): a delegator sends DATA to an Operator contract → shares the operator’s profit from Sponsorships.

Getting started (wallet/network)

  • What you need: for development — the SDK/Node; for the tokenomics — an EVM wallet and DATA.
  • Network/chain: the DATA token — Ethereum (and bridges), staking/delegation — Polygon PoS (per the docs).
  • Fees: onchain transactions depend on the network (Ethereum/Polygon); protocol payouts/profit sharing go through the tokenomics contracts.

Architecture/tech (non‑AI)

  • Components: Streamr nodes (P2P), Streams (topics), client applications/SDK, onchain tokenomics contracts (Operator/Sponsorship).
  • Participant roles: Publishers/Subscribers (at the network level) + Sponsor/Operator/Delegator (at the tokenomics level).
  • Where logic runs: message delivery — offchain (P2P protocol), incentives/accounting/payouts — onchain (smart contracts).
  • Dependencies: Polygon PoS (staking/delegation), DATA token bridges, Snapshot for governance.

Token/economics (expanded, no forecasts)

  • Token utility: DATA is used for governance, node operator incentives, stake delegation and payments/visibility on the Streamr Hub.
  • Protocol necessity drivers: at the “network” level, the tokenomics is needed to pay for infrastructure costs and to incentivize quality delivery (churn/free riders/malicious nodes).
  • Who pays fees: Sponsors fund Sponsorship contracts; Operators stake; Delegators delegate.
  • Where fees go: part goes to the protocol treasury (protocol fee), part to the operator, part to the delegators (profit sharing).
  • Issuance/burn: the max supply is fixed (see the explorer); regular mint/distribution facts are published in the official transparency reports (see Evidence), but no single “issuance table by year” was found in the reviewed Tier‑1 sources.
  • Security/incentive mechanisms: operator staking, potential slashing (described in the tokenomics), a peer‑reviewing/flagging process for nodes (described as part of the mechanics).
  • Distribution and token issuance schedule: — (no single canonical distribution/vesting table was found in the reviewed Tier‑1 sources; see the official blog/transparency reports as the source of facts on distributions).
  • Treasury: the protocol treasury is mentioned in the tokenomics as the recipient of the fee share.

Governance

  • Who makes decisions: DATA holders (governance).
  • How protocol parameters change: via Streamr Improvement Proposals (SIPs), voting on Snapshot; some tokenomics/inspection/penalty parameters are determined by SIPs.
  • Where decisions are discussed/made: Snapshot + Discord (stated on the governance page of the docs).
  • Keys/multisig: —.

Security and incidents

  • Audits: the whitepapers page publishes links to audits (including DATAv2 audits and a tokenomics audit).
  • Bug bounty: —.
  • Incidents: — (no public Tier‑1 postmortems/incidents were found in the reviewed sources).
  • Threat model: economic attacks on incentives (Sybil/free riders), risks of the tokenomics smart contracts, risks of bridges and of the multi‑chain token.

Project status and timeline

  • Current status: the network is described as an operating P2P network; the tokenomics and smart contracts are deployed (Polygon PoS).
  • Key releases/milestones: —.
  • Roadmap: available on the website (see links_*).

Ecosystem/integrations

  • Integrations: Streamr SDK/CLI; Snapshot governance; multi‑chain DATA token.
  • Partners: —.
  • Where it’s actually used: use cases are listed in the overview docs (smart cities/IoT/apps), but specific production cases in the form of a “client catalog” are not recorded in the reviewed Tier‑1 sources.

AI component of the project

  • What is real AI here? In the verified Tier‑1 sources, Streamr is described as a realtime data network; an AI function as a component of the protocol is not claimed.
  • What is truly onchain? The tokenomics contracts (Operator/Sponsorship), delegation and governance (Snapshot).
  • Why is a token needed? DATA — stake/incentives/delegation for operators and governance; it is also mentioned as a payment/visibility token on the Hub dApp.
  • Red flags (based on the information found): AI‑washing (if one tries to classify it as an AI project). What to double‑check — the actual onchain deployments of the tokenomics contracts and the activity of the incentives.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 1
  • Claim (one line): the project is data infrastructure; AI is mentioned as a possible consumer/area of application (IoT/smart cities/analytics), but not as an AI model.
  • Evidence: Tier‑1 — https://docs.streamr.network/
  • Why sufficient / why not (one line): this confirms an “AI context”, but not the presence of its own AI component.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): an AI function (inference/training) as part of the Streamr protocol is not described in Tier‑1 sources.
  • Evidence: Tier‑1 — https://docs.streamr.network/
  • Why sufficient / why not (one line): the description is about P2P data delivery and tokenomics, without AI models.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): there are demos/tools of the network, but they demonstrate data streaming, not an AI component.
  • Evidence: Tier‑1 — https://docs.streamr.network/
  • Why sufficient / why not (one line): a demo of the network ≠ a demo of AI.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://docs.streamr.network/
  • Why sufficient / why not (one line): AI quality metrics are absent, since no AI module is claimed.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): the technical description concerns the data network and tokenomics, not an AI architecture.
  • Evidence: Tier‑1 — https://docs.streamr.network/
  • Why sufficient / why not (one line): there is no AI architecture/model versions.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum (native), Polygon PoS (staking/delegation)
  • Addresses/identifiers: DATA (Ethereum): 0x8f693ca8D21b157107184d29D398A8D082b38b76
  • Evidence: Tier‑1 — https://docs.streamr.network/streamr-project/governance/ ; https://etherscan.io/token/0x8f693ca8d21b157107184d29d398a8d082b38b76
  • Why sufficient / why not (one line): the docs list the DATA addresses on the supported chains and the voting conditions; the explorer confirms the contract.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: Sponsorship/Operator contracts, delegation and distribution of profit/fees (tokenomics).
  • Evidence: Tier‑1 — https://docs.streamr.network/streamr-network/incentives/network-incentives/
  • Why sufficient / why not (one line): the tokenomics describes the onchain distribution mechanics and the accounting of stake/delegation.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: message delivery could exist without onchain, but the transparent incentives/governance layer would be lost.
  • Evidence: Tier‑1 — https://docs.streamr.network/
  • Why sufficient / why not (one line): onchain is important for the economy and governance, but it is not the only way to do data streaming.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, DATA.
  • Evidence: Tier‑1 — https://docs.streamr.network/streamr-network/incentives/network-incentives/
  • Why sufficient / why not (one line): the docs directly describe the role of DATA.
  • 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): DATA is used for “payments and visibility on the Streamr Hub dApp”.
  • Evidence: Tier‑1 — https://docs.streamr.network/streamr-network/incentives/network-incentives/
  • Why sufficient / why not (one line): on the tokenomics page, DATA is explicitly specified as a payment/visibility token at the application level.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): an operator stakes DATA to receive payouts from Sponsorships; delegators fund the stake; penalties/slashing are provided for in the description of the mechanics.
  • Evidence: Tier‑1 — https://docs.streamr.network/streamr-network/incentives/network-incentives/
  • Why sufficient / why not (one line): the page describes staking/delegation/profit sharing in detail.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): governance is carried out by DATA holders (SIPs, Snapshot; voting is available to holders on the supported chains).
  • Evidence: Tier‑1 — https://docs.streamr.network/streamr-project/governance/
  • Why sufficient / why not (one line): the governance page directly describes the process and eligibility.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): in principle, incentives/payments could be in another asset (for example, a stablecoin), although the current system is built around DATA.
  • Evidence: Tier‑1 — https://docs.streamr.network/streamr-network/incentives/network-incentives/
  • Why sufficient / why not (one line): the need for the token follows from the design of the incentive layer, but the “message delivery” service itself could conceptually be paid for in another currency.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.streamr.network/ What Streamr Network is (P2P publish/subscribe for realtime data)
Tier‑1 https://docs.streamr.network/streamr-network/incentives/network-incentives/ The role of DATA in the tokenomics (incentives, delegation, profit sharing; use of token) and the onchain tokenomics contracts
Tier‑1 https://docs.streamr.network/streamr-project/governance/ Governance via DATA holders; SIPs and Snapshot; token addresses on the supported chains
Tier‑1 https://streamr.network/whitepapers Public list of whitepapers and audit documents (including audits)
Tier‑1 https://etherscan.io/token/0x8f693ca8d21b157107184d29d398a8d082b38b76 The DATA contract on Ethereum and the max total supply
Tier‑1 https://blog.streamr.network/streamr-token-economics Token economics overview (official blog)
Tier‑1 https://blog.streamr.network/streamr-2025-q1-transparency-report Example of a transparency report (facts on token mint/distribution and treasury activity)

No comments to display

Back to top