Skip to main content

Cipher Protocol

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

Cipher Protocol — an Infra project on Ethereum, token (symbol: CIPHER).

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 project with an ERC‑20 token, CIPHER, on the Ethereum network and a public cipher-core repository (circuits + smart contracts).
  • Who it’s for: developers and protocol users (exact roles/scenarios are not established per Tier‑1 sources).
  • Why onchain/token: the onchain part envisages smart contracts; the role of the CIPHER token (payment/incentives/governance) is not established per Tier‑1 sources.

How it works (very briefly)

  1. The user does: interacts with the protocol/contracts (the specific UX is not established).
  2. The system does: uses a chain of smart contracts and corresponding circuits/verifier contracts (per the repository structure).
  3. The user gets: the result of a protocol operation (not established).
  4. Where the blockchain is: Ethereum (ERC‑20 token; the existence of contract code in the repository).
  5. Token role: not established per Tier‑1.

Quick links: AI thesis fit

Project passport

Field Value
Project name Cipher Protocol
Also known as (aliases) CIPHER
Logo (logo) ../assets/773_cipher-protocol_logo.svg
Token symbol (ticker) CIPHER
Category Infra
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) —
Token (standard) ERC-20
Token contract 0xfc93e5844a2015ceef26bf6cae6689ff031509f4
Token model (token_type) —
Max supply 10 000 000 CIPHER
Issuance —
Tokenomics (tokenomics, brief) —
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) —
Use‑case (use_case) circuits + smart contracts (UTXO-style)
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 2 / token_score 0 / evidence_score 3
Last verified 2026-02-11

General project overview

Cipher Protocol is a project with an ERC‑20 token, CIPHER, on the Ethereum network. links_* includes a Tier‑1 cipher-core repository containing circuits/ and contracts/ directories, as well as build and test instructions. A Tier‑1 description of the product (from docs/website) is not established, so conclusions about its purpose and the role of the token remain conservative.

Features/modules

  • Cipher core (codebase): circuits and smart contracts (per the repository structure).
  • Dev tooling: build instructions (Node.js 16+, build:circuit, build:contract, test:contract).

Typical scenarios

  • Scenario 1: a developer builds circuits and contracts from the repository → receives build artifacts (solidity verifier contract etc.).
  • Scenario 2: a user interacts with the CIPHER token → operations are visible onchain.

Getting started (wallet/network)

  • What you need: a wallet for Ethereum and ETH for fees (for onchain operations with the token).
  • Network/chain: Ethereum mainnet.
  • Fees: Ethereum network fees for transactions.

Architecture/tech (non‑AI)

  • Components: smart contracts + circuits (per the cipher-core repository), the CIPHER ERC‑20 token.
  • Participant roles: developers, users, Ethereum infrastructure providers (RPC/DEX).
  • Where logic runs: onchain — protocol contracts (if deployed) and the token; offchain — proof generation/verification (based on the presence of circuits).
  • Dependencies: Ethereum infrastructure; the build toolchain (Node.js).

Token/economics (expanded, no forecasts)

  • Token utility: not established per Tier‑1 sources.
  • Supply parameters: max total supply 10 000 000 CIPHER (onchain).
  • Who pays fees: users (gas in ETH) for transactions.
  • Where fees go: to Ethereum network validators/stakers (within the network mechanics).
  • Issuance/burn: —.
  • Security/incentive mechanisms: —.

Governance

  • Who makes decisions: —.
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: not found per Tier‑1.
  • Bug bounty: not found per Tier‑1.
  • Incidents: —.
  • Threat model: smart contract risks and risks to the correctness of circuits; without a Tier‑1 description of deployments/audits, the assessment is conservative.

Project status and timeline

  • Current status: the token on Ethereum mainnet; the status of the protocol as a product is not established.
  • Key releases/milestones: —.
  • Roadmap: —.

Ecosystem/integrations

  • Integrations: —.
  • Partners: —.
  • Where it’s actually used: not established per Tier‑1.

AI component of the project

  • What is real AI here? No AI component is identified per Tier‑1 sources.
  • What is truly onchain? The CIPHER ERC‑20 token is confirmed onchain and there is a public repository with smart contracts/circuits.
  • Why is a token needed? Not established per Tier‑1 sources.
  • Red flags (based on the information found): absence of an accessible Tier‑1 description of the product (confirmation from docs/website is needed); the role of the token is not confirmed.

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 medium 2
Token necessity low 0
Evidence Tier‑1 present 3
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 intent was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): The available Tier‑1 sources do not confirm AI intent.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): No Tier‑1 description of AI features/tasks was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): An AI component is not confirmed.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): No Tier‑1 demo/app was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no verifiable demo.
  • 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): Metrics/benchmarks were not found.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): Tier‑1: no tech description of the AI part was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): The AI part is not confirmed.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: CIPHER ERC‑20 token contract: 0xfc93e5844a2015ceef26bf6cae6689ff031509f4
  • Evidence: Tier‑1 — https://etherscan.io/token/0xfc93e5844a2015ceef26bf6cae6689ff031509f4
  • Why sufficient / why not (one line): The token parameters are verifiable onchain.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: protocol smart contracts (source code in the cipher-core repository).
  • Evidence: Tier‑1 — https://github.com/Cipher-Protocol/cipher-core
  • Why sufficient / why not (one line): The existence of protocol contract code is onchain logic beyond “just a token”.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 justification that the blockchain is critical (docs/a description of the trust model are needed).
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has an ERC‑20 token, CIPHER, on the Ethereum network.
  • Evidence: Tier‑1 — https://etherscan.io/token/0xfc93e5844a2015ceef26bf6cae6689ff031509f4
  • Why sufficient / why not (one line): The existence of the token is verifiable onchain.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 0
  • Claim (one line): No Tier‑1 confirmation of payment for the service with the CIPHER token was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no description of payment mechanics.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): No Tier‑1 description of incentives/collateral/penalties for CIPHER was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There are no confirmed economic mechanics.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): No Tier‑1 description of the use of the CIPHER token for governance was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no confirmation of governance mechanics.
  • 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.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without a Tier‑1 description of the role of the token, no conclusion can be drawn.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://etherscan.io/token/0xfc93e5844a2015ceef26bf6cae6689ff031509f4 Onchain facts: the Cipher Protocol (CIPHER) token, Ethereum network, contract, decimals, max supply.
Tier‑1 https://github.com/Cipher-Protocol/cipher-core Tier‑1 codebase: the existence of circuits/ and contracts/, build and test instructions.
Tier‑2 https://coinmarketcap.com/currencies/cipher-protocol/ Aggregator profile (for reference; not Tier‑1 proof).

No comments to display

Back to top