Skip to main content

Jackal Protocol

Jackal 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).

Jackal Protocol — an Infra project: a Cosmos L1 blockchain for decentralized data storage; token (symbol: JKL). Per Tier‑1 sources, the AI component is not confirmed.

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 blockchain protocol for file storage, where storage providers must regularly prove that the data is preserved.
  • Who it’s for: users and dApp developers who need self‑custodial storage and access to it from other networks (IBC/integrations).
  • Why onchain/token: onchain stores metadata/contracts, runs the proof mechanics and distributes rewards/penalties; the JKL token is needed for storage payments, staking and governance.

How it works (very briefly)

  1. The user does: prepares a file and publishes an onchain storage contract with the merkle root and size.
  2. The provider does: stores the data and publishes a merkle proof within the challenge window for confirmation.
  3. The network does: validators verify the proofs; the provider receives a reward.
  4. If a proof is missed: the contract records a missed proof; after a threshold of misses — burn and redistribution/recovery.
  5. Token role: payment for storage/operations, staking/network security and voting in governance.

Quick links: AI thesis fit

Project passport

Field Value
Project name Jackal Protocol
Also known as (aliases) Jackal
Logo (logo) ../assets/507_jackal-protocol_logo.svg
Token symbol (ticker) JKL
Category Infra
Primary chain (chain) Jackal
Type Appchain
Network status mainnet
Consensus (consensus) PoS (CometBFT)
Launch date (launch_date) —
Project status (status) active
Token (standard) native
Token contract —
Token model (token_type) utility (payments + staking + governance)
Max supply —
Issuance —
Tokenomics (tokenomics, brief) JKL is used for storage payments, staking/network security and governance; also as collateral.
Governance onchain governance
Admins/keys —
Audit —
Bug bounty yes
Team (team) Jackal Labs
Funding (investors/funding) —
AI component (ai_component) —
Use‑case (use_case) decentralized data storage
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 3 / evidence_score 2
Last verified 2026-02-11

General project overview

Jackal describes itself as a trustless data layer: a blockchain where storage contracts (merkle root/size) are recorded onchain and challenges are run, while storage providers must regularly publish proofs of storage. The documentation describes the JPOP (proof‑of‑persistence) and IDOL (internal detection of loss) protocols and the blockchain modules.

Features/modules

  • Storage Module: JPOP + IDOL protocols with rewards/penalties.
  • Products/surfaces: Vault/Pin/Outpost (per the website) as interfaces/integrations for storage.
  • Governance: onchain governance via staked JKL.
  • Bug bounty: a public responsible vulnerability disclosure program.

Typical scenarios

  • Scenario 1: the user creates a storage contract → providers store the file and prove its preservation → the user gets access to the data.
  • Scenario 2: a storage provider runs a provider → takes contracts → publishes proofs → receives rewards.

Getting started (wallet/network)

  • What you need: a wallet in the Cosmos ecosystem (for example, Keplr/Leap) and JKL for operations/staking (see the docs).
  • Network/chain: Jackal.
  • Fees: Jackal network transaction fees + the cost of storage (in JKL).

Architecture/tech (non‑AI)

  • Components: Cosmos L1, validators, storage providers and modules (storage/file tree/mint/name service) — per the docs.
  • Participant roles: users, storage providers, validators, dApp developers.
  • Where logic runs: onchain — contracts/challenges/rewards/penalties; offchain — storage and delivery of data.
  • Dependencies: Cosmos SDK / a Tendermint‑like stack.

Token/economics (expanded, no forecasts)

  • Token utility (per the docs): payment for storage and transactions; delegation/staking for security; governance; collateral.
  • Incentive mechanisms: storage providers receive rewards for valid proofs; for misses — penalties and burn of contracts (per the storage module).

Governance

  • Who makes decisions: onchain governance via staked JKL (per the docs).
  • How protocol parameters change: via governance proposals (text/software/spend, etc.).
  • Where decisions are discussed/made: onchain governance + the project’s repositories/docs.
  • Keys/multisig: —.

Security and incidents

  • Audits: —.
  • Bug bounty: there is a public program (see links_*).
  • Incidents: —.
  • Threat model: risks of data loss/unavailability at providers; JPOP/IDOL introduce verifiability of storage and redistribution.

Project status and timeline

  • Current status: mainnet.
  • Key releases/milestones: —.
  • Roadmap: milestones/repositories (see links_* Roadmap).

Ecosystem/integrations

  • Integrations: apps (Vault/Pin/Outpost) and dev tooling (Jackal.js) per the docs.
  • Partners: —.
  • Where it’s actually used: the product pages and docs demonstrate storage and integration cases.

AI component of the project

  • What is real AI here? per Tier‑1 sources, the project is about storage; the AI component is not established.
  • What is truly onchain? onchain contracts/metadata and the JPOP/IDOL challenge mechanics + PoS security.
  • Why is a token needed? JKL is needed for payment for storage/fees, staking and governance.
  • Red flags (based on the information found): for DecAIHub it is important that the AI component is not confirmed by Tier‑1.

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 high 3
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 declaration of AI intentions was found (focus on storage).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without a Tier‑1 source we do not confirm intent.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): AI functionality of the product is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): The Tier‑1 docs describe the storage modules and the token, but not AI.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): There is no Tier‑1 demo/example of the AI component’s operation (no AI component was found).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): AI is not established.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): An AI component is not established.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): A tech description of AI models/versions is absent.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): An AI component is not established.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Jackal (Cosmos L1)
  • Addresses/identifiers: —
  • Evidence: Tier‑1 — https://docs.jackalprotocol.com/get-started-with-jackal/the-usdjkl-token.html
  • Why sufficient / why not (one line): The docs record that Jackal is a PoS Cosmos L1.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: storage contracts and onchain challenges/verification of proofs (JPOP/IDOL).
  • Evidence: Tier‑1 — https://docs.jackalprotocol.com/the-blockchain/storage-module.html
  • Why sufficient / why not (one line): The storage module describes protocol logic beyond the token.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without onchain contracts/challenges, trustless proof of storage and the distribution of rewards/penalties are impossible.
  • Evidence: Tier‑1 — https://docs.jackalprotocol.com/the-blockchain/storage-module.html
  • Why sufficient / why not (one line): JPOP/IDOL rely on the blockchain layer.
  • 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, JKL.
  • Evidence: Tier‑1 — https://docs.jackalprotocol.com/get-started-with-jackal/the-usdjkl-token.html
  • Why sufficient / why not (one line): The docs describe JKL as the native token.
  • 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): JKL is the means of payment for data storage.
  • Evidence: Tier‑1 — https://docs.jackalprotocol.com/get-started-with-jackal/the-usdjkl-token.html
  • Why sufficient / why not (one line): The “Data Storage” section fixes this.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): JKL is used for staking/delegation and collateral; storage providers receive rewards and penalties based on proofs.
  • Evidence: Tier‑1 — https://docs.jackalprotocol.com/get-started-with-jackal/the-usdjkl-token.html ; https://docs.jackalprotocol.com/the-blockchain/storage-module.html
  • Why sufficient / why not (one line): The docs describe staking/collateral and the rewards/penalties mechanism.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): Staked JKL gives the right to vote in onchain governance.
  • Evidence: Tier‑1 — https://docs.jackalprotocol.com/get-started-with-jackal/the-usdjkl-token.html
  • Why sufficient / why not (one line): The “Governance” section fixes this.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): The replaceability of the token is not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no explicit comparison “can be replaced with USDC/a subscription”.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.jackalprotocol.com/the-blockchain/storage-module.html Protocol logic of storage: JPOP/IDOL, onchain challenge windows, rewards/penalties.
Tier‑1 https://docs.jackalprotocol.com/get-started-with-jackal/the-usdjkl-token.html Role of the JKL token: storage payments, staking/security, governance, collateral.
Tier‑1 https://www.jackalprotocol.com/blog/announcement-jackal-protocol-bug-bounty-program Public bug bounty program and the scope of repositories.
Tier‑1 — No Tier‑1 source for the claim about an AI component was found.
Tier‑2 https://coinmarketcap.com/currencies/jackal-protocol/ Token profile/metadata (for reference).
Tier‑2 https://www.coingecko.com/en/coins/jackal-protocol Token profile/metadata (for reference).

No comments to display

Back to top