Skip to main content

Saga

Saga (Saga Protocol / SAGA) — 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).

Saga — an Infra project on Saga (Cosmos‑SDK), token (symbol: SAGA).

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 “chain‑to‑launch‑chains” L1 protocol: it lets developers launch dedicated application‑specific L1s (“chainlets”) with shared security and EVM compatibility.
  • Who it’s for: dApp teams/developers who need their own blockspace and managed infrastructure without competing for resources on a “shared” L1.
  • Why onchain/token: onchain is needed for trustlessness (validators, staking, CCV/shared security, chain management); the SAGA token — for staking/security and (per the plan/mainnet phase regime) for payments/bonds when launching chainlets.

How it works (very briefly)

  1. The developer does: deploys/manages a chainlet via the Saga App/CLI (and/or deploys the application into a dedicated environment).
  2. The system does: the platform orchestrates the chainlet launch, while the security+platform chain provide shared security (CCV) and the validator infrastructure.
  3. The user gets: the dApp runs in a dedicated chain (less competition for blockspace; a “gasless” UX model for end users is claimed).
  4. Where the blockchain is: the security chain and the platform chain (Cosmos‑SDK) + chainlets; staking/validators/accounting and chainlet launches — onchain.
  5. Token role: SAGA — staking/slashing for the security chain; the launch plan also describes a role of SAGA for provisioning chainlets.

Quick links: AI thesis fit

Project passport

Field Value
Project name Saga
Also known as (aliases) Saga Protocol, chainlets, $SAGA
Logo (logo) ../assets/96_saga_logo.svg
Token symbol (ticker) SAGA
Category Infra
Primary chain (chain) Saga
Type Appchain
Network status mainnet
Consensus (consensus) PoS (CometBFT)
Launch date (launch_date) 2024-04
Project status (status) active
Token (standard) native
Token contract —
Token model (token_type) utility (payments + staking + governance)
Max supply 1,000,000,000
Issuance inflationary
Tokenomics (tokenomics, brief) provisioning fee bond for chainlets + staking rewards; there is a Protocol Controlled Reserve (PCR).
Governance DAO
Admins/keys validators + onchain governance
Audit —
Bug bounty —
Team (team) Rebecca Liao (CEO), Jacob McDorman (CTO), Jin Kwon (CSO) and others
Funding (investors/funding) —
AI component (ai_component) —
Use‑case (use_case) launch app-specific L1 (chainlets) with shared security
DecAI Fit — AI thesis fit 0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary ai_score 0 / onchain_score 3 / token_score 2 / evidence_score 2
Last verified 2026-02-11

General project overview

Saga is positioned as an L1 platform for the automated launch of dedicated application‑specific blockchains (“chainlets”). The idea: instead of competing for blockspace on a single monolithic L1, an application gets its own chain(s) with the ability to scale horizontally. The architecture describes a security chain (where the SAGA token is issued/staked and slashing is applied), a platform chain (where developers launch/manage chainlets), and the chainlets themselves (where the application runs).

Important for DecAI Fit: in Tier‑1 sources, Saga does not describe AI as a component of the protocol. The website has an ecosystem section with categories (including “AI Agents”), but this refers to applications in the ecosystem, not to an “AI layer” of Saga.

Features/modules

  • Security chain / staking: issuance of SAGA, staking and slashing for security.
  • Platform chain: launching and managing chainlets; shared security via CCV (Cross‑chain Validation).
  • Chainlets: dedicated chains for applications (EVM compatibility for chainlets is claimed).
  • Saga App/portal: a web interface for launching and managing chainlets.
  • SSC code: the open‑source implementation of the Saga Security Chain (Cosmos‑SDK + CometBFT).

Typical scenarios

  • Scenario 1 (dev): a team launches a chainlet → gets a dedicated network (RPC/WebSocket/explorer) for its dApp without competing for blockspace.
  • Scenario 2 (staker/validator): holders stake SAGA on the security chain → validators provide security and receive rewards/fees.
  • Scenario 3 (dApp user): interacts with an application in a specific chainlet; the UX may be “gasless” for end users (per the description of the economic model).

Getting started (wallet/network)

  • What you need: a web3 wallet (Keplr is mentioned in the guides) and access to the Saga App.
  • Network/chain: Saga (security chain / platform chain) + specific chainlets (depending on the project).
  • Fees: the fee model depends on the chainlet; the documentation describes a fixed gas price and a “gas return” mechanism for a fee‑free UX for end users.

Architecture/tech (non‑AI)

  • Components: security chain (Cosmos‑SDK), platform chain (Cosmos‑SDK), chainlets; validator infrastructure; Saga App/CLI; IBC/CCV.
  • Participant roles: chainlet developers, dApp end users, validators, delegators/stakers, governance participants.
  • Where logic runs: critical security/launch/accounting logic — onchain in the security/platform chain; dApp execution — in the corresponding chainlet.
  • Dependencies: Cosmos‑SDK/CometBFT, CCV (a variant of interchain security), ecosystem integrations/bridging (LIL is mentioned on the website).

Token/economics (expanded, no forecasts)

  • Token utility: SAGA is used for staking/slashing on the security chain; the launch plan and the litepaper describe a role of SAGA for provisioning chainlets (fee bond/subscriptions/deposits).
  • Protocol necessity drivers: the security of shared security relies on staking; the chainlet economy is tied to provisioning and paying for validator infrastructure.
  • Who pays fees: per the litepaper — developers pay for provisioning chainlets (not end users directly).
  • Where fees go: per the litepaper — fees from developers are intended to cover validators’ infrastructure costs; stakers receive rewards via inflation.
  • Issuance/burn: an inflationary model tunable to a target staking rate is described; the PCR and the possibility of a burn as a supply management tool are also described.
  • Security/incentive mechanisms: staking rewards + slashing for SLA violations/misbehavior; an auction/selection mechanism for validators (in the litepaper).
  • Distribution and token issuance schedule: the launch plan provides high‑level allocations (total supply 1B).
  • Treasury: Protocol Controlled Reserve (PCR) — a pool of tokens for the protocol’s “common needs” (trial credits, relayers, partnerships, etc.).

Governance

  • Who makes decisions: onchain governance (Cosmos‑SDK), validators and stake holders (in Cosmos ecosystem terms).
  • How protocol parameters change: via network software upgrades and governance processes (per the general design of Cosmos‑SDK chains; a detailed process for Saga is not recorded in Tier‑1 sources).
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: —. No public reports were found in Tier‑1 sources.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: PoS/validator risks (implementation bugs, infrastructure misconfigurations, CCV/IBC); the docs describe a phased launch to reduce risks.

Project status and timeline

  • Current status: mainnet (Pegasus release / progressive launch).
  • Key releases/milestones: there is the SSC repository and GitHub Releases; the docs describe the components and the phased launch.
  • Roadmap: the website has an events roadmap; the docs and blog describe plans (for example, LIL in Q1 2025 and progressive phases).

Ecosystem/integrations

  • Integrations: Keplr (mentioned in the guides), EVM runtime (mentioned in website/blog materials), chainlets with separate RPCs/explorers.
  • Partners: the website/blog mention integrations at the level of Uniswap/Oku/Squid Router (Mainnet 2.0) and partnerships with ecosystems (Polygon/Avalanche/Celestia, etc.).
  • Where it’s actually used: the Saga App for launching chainlets; the website lists ecosystem projects/chains (including gaming and DeFi).

AI component of the project

  • What is real AI here? Per Tier‑1 sources, no confirmation of an AI component at the level of the Saga protocol was found (it is L1 infrastructure for chainlets). AI projects may be part of the ecosystem, but this does not make Saga an “AI protocol”.
  • What is truly onchain? Security chain/platform chain + chainlets; staking/CCV/shared security/chainlet launches are described as onchain processes.
  • Why is a token needed? SAGA is described as a token for staking/slashing security and for provisioning chainlets (fee bond/payment for infrastructure) as the project moves to a permissionless model.
  • Red flags (based on the information found): AI‑washing (if Saga is positioned as an AI protocol without Tier‑1 artifacts); what to double‑check: specific onchain parameters of the token and governance mechanics on mainnet; the existence of public audits.

DecAI Fit component summary

  • DecAI Fit: 0/6 — no AI reality and no AI intent (ai_score=0)
Component Level Score
AI reality absent 0
Onchain necessity high 3
Token necessity medium 2
Evidence Tier‑1 present 2
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): No Tier‑1 roadmap/intent regarding an AI module of the Saga protocol was found.
  • Evidence: Tier‑1 — https://www.saga.xyz/saga-protocol, https://sagaxyz.cdn.prismic.io/sagaxyz/08e727f2-88a2-4c95-ad17-b0b9579d2b69_saga-litepaper-march-2022.pdf
  • Why sufficient / why not (one line): Tier‑1 describes L1 infrastructure for chainlets/shared security without an AI roadmap.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): AI functions at the protocol level are not confirmed.
  • Evidence: Tier‑1 — https://www.saga.xyz/saga-protocol
  • Why sufficient / why not (one line): the product description is L1/chainlets/shared security; an AI subsystem is not described as part of the protocol.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): an AI demo/guide for an AI component is not required, since AI_1=0 (this is not an AI protocol).
  • Evidence: Tier‑1 — https://www.saga.xyz/
  • Why sufficient / why not (one line): Tier‑1 has demos/guides for launching chainlets, but these are not AI demos.
  • 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.saga.xyz/
  • Why sufficient / why not (one line): AI metrics are not applicable (an AI subsystem is not confirmed).
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): there is a technical description, but it relates to chainlets/shared security, not to an AI component.
  • Evidence: Tier‑1 — https://docs.saga.xyz/introduction/cassiopeia-overview, https://sagaxyz.cdn.prismic.io/sagaxyz/08e727f2-88a2-4c95-ad17-b0b9579d2b69_saga-litepaper-march-2022.pdf
  • Why sufficient / why not (one line): the architecture is described, but there is no AI part → AI_4=0.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Saga
  • Addresses/identifiers: an explorer for the network; the SSC repository (code) + GitHub Releases.
  • Evidence: Tier‑1 — https://www.mintscan.io/saga, https://github.com/sagaxyz/ssc
  • Why sufficient / why not (one line): the network and its artifacts are verifiable via the explorer and the official repo.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: launching/accounting of chainlets (platform chain), shared security (CCV), staking/slashing (security chain).
  • Evidence: Tier‑1 — https://docs.saga.xyz/introduction/cassiopeia-overview, https://sagaxyz.cdn.prismic.io/sagaxyz/08e727f2-88a2-4c95-ad17-b0b9579d2b69_saga-litepaper-march-2022.pdf
  • Why sufficient / why not (one line): this is protocol‑level onchain logic that does not reduce to “just a token”.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without a blockchain there would be no trustless shared security (staking/slashing/CCV) and no independent validation of chainlets by validators.
  • Evidence: Tier‑1 — https://docs.saga.xyz/introduction/cassiopeia-overview
  • Why sufficient / why not (one line): the key property — security/verifiability of chainlets without trusting the operator — requires onchain consensus.
  • 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, SAGA.
  • Evidence: Tier‑1 — https://docs.saga.xyz/introduction/cassiopeia-overview
  • Why sufficient / why not (one line): Tier‑1 explicitly describes $SAGA as the security chain token (mint/stake/slash).
  • 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): provisioning chainlets requires a fee deposit / fee bond (in SAGA) per the litepaper/launch plan.
  • Evidence: Tier‑1 — https://sagaxyz.cdn.prismic.io/sagaxyz/08e727f2-88a2-4c95-ad17-b0b9579d2b69_saga-litepaper-march-2022.pdf, https://medium.com/sagaxyz/saga-mainnet-technical-launch-plan-c084b1426acc
  • Why sufficient / why not (one line): Tier‑1 describes the economics of developer fees and the fee bond for provisioning.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): staking SAGA is used for the security chain; slashing for validator misbehavior is provided for.
  • Evidence: Tier‑1 — https://docs.saga.xyz/introduction/cassiopeia-overview
  • Why sufficient / why not (one line): Tier‑1 explicitly states: $SAGA minted/staked/slashed.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): an explicit token‑governance role of SAGA is not confirmed in Tier‑1 sources.
  • Evidence: Tier‑1 — https://docs.saga.xyz/introduction/cassiopeia-overview
  • Why sufficient / why not (one line): there are mentions of governance processes/cases, but a direct role of the token in voting as a utility is not recorded.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the replaceability of the token is neither proven nor refuted per Tier‑1.
  • Evidence: Tier‑1 — https://sagaxyz.cdn.prismic.io/sagaxyz/08e727f2-88a2-4c95-ad17-b0b9579d2b69_saga-litepaper-march-2022.pdf
  • Why sufficient / why not (one line): the presence of staking/slashing usually requires a native token, but no direct proof of “irreplaceability” was found.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://sagaxyz.cdn.prismic.io/sagaxyz/08e727f2-88a2-4c95-ad17-b0b9579d2b69_saga-litepaper-march-2022.pdf Chainlets + shared security; token mechanism (developer fees, fee bond, inflation, PCR).
Tier‑1 https://docs.saga.xyz/introduction/cassiopeia-overview Pegasus architecture: security chain/platform chain/chainlets; staking and slashing; CCV/shared security.
Tier‑1 https://github.com/sagaxyz/ssc The official code of the Saga Security Chain (Cosmos‑SDK + CometBFT).
Tier‑1 https://github.com/sagaxyz/ssc/releases SSC releases/tags (changelog/release artifacts).
Tier‑1 https://medium.com/sagaxyz/saga-mainnet-technical-launch-plan-c084b1426acc Progressive launch phases + high‑level tokenomics (total supply 1B, allocations).
Tier‑1 https://medium.com/sagaxyz/launch-your-first-saga-chainlet-99541cc35ffa A reproducible guide for launching a chainlet via the Saga App (not an AI demo, but verifiability of the product).
Tier‑1 https://app.saga.xyz/launch/ Tier‑1 web‑app/portal for launching chainlets (product artifact).
Tier‑1 https://www.saga.xyz/saga-protocol High‑level description of the protocol (chainlets/EVM/gasless model), without an AI component.

No comments to display

Back to top