Cirus
Cirus — 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).
Cirus — an AI/Data | Infra project on the Ethereum network, token (symbol: CIRUS).
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 positioned as “User Owned Data for AI” and services around user data/insights.
- Who it’s for: users (for example, via a browser extension) and partners/services that need data/insights.
- Why onchain/token: the confirmed onchain artifact is the CIRUS ERC‑20 token on Ethereum; the criticality of onchain for the product is not established per Tier‑1.
- What you can actually touch (Tier‑1): Cirus Chrome Extension (download from the Chrome Web Store).
How it works (very briefly)
- The user does: installs and uses the browser extension (per the description on the website).
- The system does: collects/processes data and turns it into insights positioned as AI‑driven.
- The user gets: functionality/rewards claimed by the project (details are not established per Tier‑1).
- Where the blockchain is: the onchain component is confirmed by the existence of an ERC‑20 token on Ethereum.
- Token role (if any): CIRUS (ERC‑20); the token utility as a mandatory protocol mechanism is not established per Tier‑1.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Cirus |
| Also known as (aliases) | CIRUS |
| Logo (logo) | ../assets/733_cirus-foundation_logo.png |
| Token symbol (ticker) | CIRUS |
| Category | AI/Data | Infra |
| 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 | 0xa01199c61841fce3b3dafb83fefc1899715c8756 |
| Token model (token_type) | — |
| Max supply | — |
| Issuance | — |
| Tokenomics (tokenomics, brief) | — |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | "user-owned data" + AI-driven insights |
| Use‑case (use_case) | data collection/processing for AI insights |
| DecAI Fit — AI thesis fit | 3/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | ai_score 2 / onchain_score 1 / token_score 0 / evidence_score 3 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://www.cirusfoundation.com |
| Docs | https://cirusfoundation.notion.site/White-Paper-60e6f071affe417c9ae13a94723dea1c |
| GitHub | — |
| Releases / Changelog | — |
| Whitepaper | https://cirusfoundation.com/whitepaper |
| Roadmap | https://cirusfoundation.medium.com/the-evolution-of-cirus-roadmap-update-d9142a6a7a12 |
| Security advisories | https://support.cirusfoundation.com/en/knowledge/data-security |
| Explorer | https://etherscan.io/token/0xa01199c61841fce3b3dafb83fefc1899715c8756 |
| App / Demo | https://chromewebstore.google.com/detail/cirus-crypto-wallet-web3/kgdijkcfiglijhaglibaidbipiejjfdp |
| X | https://twitter.com/cirusfoundation |
| Discord | https://discord.com/invite/Vbawz2j7AW |
| Telegram | https://t.me/CirusAnnouncements |
| Medium | https://medium.com/the-cirus-foundation |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/cirus |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/cirus-foundation/ |
General project overview
Cirus is positioned on Tier‑1 pages as “User Owned Data for AI” and describes a process via a browser extension (“Surf n' Earn”) and the transformation of data into AI‑driven insights. Within this card, we record verifiable elements: the existence of public Tier‑1 project pages and the existence of an ERC‑20 token on Ethereum.
Features/modules
- A browser extension and a “surf/earn” flow (per the website’s description).
- Positioning: data → AI‑driven insights.
Typical scenarios
- Scenario 1: a user installs the extension → uses it in the browser → receives the claimed functionality/rewards (details not established).
- Scenario 2: a user interacts with the token → transactions are observable in the Ethereum explorer.
Getting started (wallet/network)
- What you need: access to the project’s website/pages; a wallet for EVM networks (for operations with the token).
- Network/chain: Ethereum (for the token).
- Fees: Ethereum network fees for token transactions.
Architecture/tech (non‑AI)
- Components: the ERC‑20 token on Ethereum; the browser extension and project services (offchain, details not established).
- Participant roles: extension/platform users and token holders.
- Where logic runs: the token — onchain (Ethereum); data collection/processing — not established (probably offchain).
- Dependencies: —.
Token/economics (expanded, no forecasts)
- Token utility: not established per Tier‑1 (a Tier‑1 description of the mechanics is needed).
- Who pays fees: for token transactions, the sender pays fees (Ethereum gas).
- Issuance/burn: —.
Governance
- Who makes decisions: —.
- How protocol parameters change: —.
Security and incidents
- Audits: —.
- Bug bounty: —.
- Incidents: —.
- Threat model: typical token risks and extension/service risks (details not established).
Project status and timeline
- Current status: mainnet (the token on Ethereum).
- Key releases/milestones: —.
- Roadmap: see links_* (a Medium post with a roadmap update).
Ecosystem/integrations
- Integrations: —.
- Partners: —.
- Where it’s actually used: —.
AI component of the project
- What is real AI here? per Tier‑1 pages, the project claims “AI‑driven insights” and the use of data “for AI”.
- What is truly onchain? the confirmed onchain artifact is the CIRUS ERC‑20 token on Ethereum.
- Why is a token needed? the role of the token as a mandatory protocol mechanism is not established per Tier‑1.
- Red flags (based on the information found): absence of public quality metrics/architecture of the AI part; mixing marketing wording and Tier‑1 evidence.
DecAI Fit component summary
- DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | high | 2 |
| Onchain necessity | low | 1 |
| 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): There are signs of AI reality per Tier‑1 (see AI_1..AI_4), so the AI_0 flag (intent‑only) does not apply.
- Evidence: Tier‑1 — see Evidence/links in AI_1..AI_4.
- Why sufficient / why not (one line): AI_0=1 is admissible only when AI_1..AI_4=0; here ai_score without AI_0 = 2.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): The transformation of data into “AI‑driven insights” is claimed per Tier‑1 pages.
- Evidence: Tier‑1 — https://www.cirusfoundation.com/ ; https://cirusfoundation.com/whitepaper
- Why sufficient / why not (one line): There is a description of the result (insights) and AI positioning, but without implementation details.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 1
- Claim (one line): There is a Tier‑1 “demo surface”: downloading/installing Cirus Chrome Extension from the Chrome Web Store.
- Evidence: Tier‑1 — https://chromewebstore.google.com/detail/cirus-crypto-wallet-web3/kgdijkcfiglijhaglibaidbipiejjfdp ; https://cirusfoundation.com/whitepaper
- Why sufficient / why not (one line): This is a reproducible user scenario “download and start using” (the project’s product surface).
- 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.cirusfoundation.com/
- Why sufficient / why not (one line): No quantitative quality metrics were found in the available Tier‑1 sources.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): The tech description/architecture of the AI part is not established per Tier‑1.
- Evidence: Tier‑1 — https://cirusfoundation.com/whitepaper
- Why sufficient / why not (one line): Explicit architectural details/versions are needed; not recorded per Tier‑1 sources.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum
- Addresses/identifiers: token contract 0xa01199c61841fce3b3dafb83fefc1899715c8756
- Evidence: Tier‑1 — https://etherscan.io/token/0xa01199c61841fce3b3dafb83fefc1899715c8756
- Why sufficient / why not (one line): The existence of the token and an observable contract in the explorer confirms an onchain artifact.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 0
- What useful logic is onchain: Tier‑1 confirmation of onchain logic of the product, other than the token, is not established.
- Evidence: Tier‑1 — https://www.cirusfoundation.com/
- Why sufficient / why not (one line): 1 requires addresses/descriptions of protocol/logic contracts, not just a token.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: it is not established that a key property of the product breaks down without onchain.
- Evidence: Tier‑1 — https://www.cirusfoundation.com/
- Why sufficient / why not (one line): There is no Tier‑1 justification of onchain criticality.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): The project has a token, CIRUS (ERC‑20).
- Evidence: Tier‑1 — https://etherscan.io/token/0xa01199c61841fce3b3dafb83fefc1899715c8756
- Why sufficient / why not (one line): The token and its contract are observable in the Tier‑1 explorer.
- 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): The use of the token as a mandatory payment for the service is not established per Tier‑1.
- Evidence: Tier‑1 — https://www.cirusfoundation.com/
- Why sufficient / why not (one line): 1 requires an explicit Tier‑1 payment/access mechanism.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): Mechanisms of incentives/collateral/penalties with the token are not established per Tier‑1.
- Evidence: Tier‑1 — https://www.cirusfoundation.com/
- Why sufficient / why not (one line): Specific rules/contracts/documentation are needed.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): No Tier‑1 confirmation of the governance role of the token was found.
- Evidence: Tier‑1 — https://www.cirusfoundation.com/
- Why sufficient / why not (one line): 1 requires an explicit governance process/documentation.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 0
- Claim (one line): The replaceability of the token without loss of meaning is not established per Tier‑1.
- Evidence: Tier‑1 — https://www.cirusfoundation.com/
- Why sufficient / why not (one line): There is insufficient data on the role of the token in the product.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://www.cirusfoundation.com/ | AI positioning (“User Owned Data for AI”, “AI‑driven insights”) and a description of the extension/process. |
| Tier‑1 | https://cirusfoundation.com/whitepaper | Whitepaper/whitepaper page (context and project claims). |
| Tier‑1 | https://chromewebstore.google.com/detail/cirus-crypto-wallet-web3/kgdijkcfiglijhaglibaidbipiejjfdp | “Demo surface”: installation/use of Cirus Chrome Extension (what you can touch). |
| Tier‑1 | https://etherscan.io/token/0xa01199c61841fce3b3dafb83fefc1899715c8756 | The existence of the CIRUS ERC‑20 token on Ethereum (contract/chain). |
| Tier‑2 | https://www.coingecko.com/en/coins/cirus | Token profile on an aggregator (context; not proof). |
| Tier‑3 | https://coinmarketcap.com/currencies/cirus-foundation/ | Token profile on an aggregator (context; not proof). |
No comments to display
No comments to display