Skip to main content

AlphaScan

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

AlphaScan — an AI/Analytics project on the Arbitrum One network, token (symbol: ASCN).

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: an analytics platform (including signals/sentiment from Twitter and Telegram) + a Telegram bot for analytics and trading (claimed in Tier‑1 documentation).
  • Who it’s for: users who need an interface for analytics and trade execution via a Telegram bot (claimed).
  • Why onchain/token: the ASCN token is used for access to features, staking and governance (claimed in Tier‑1 documentation); the token contract on Arbitrum One is confirmed onchain.
  • What you can actually touch (Tier‑1): the dApp app.alphascan.xyz and the Telegram bot AlphaScanTradingBot (see links_*).

How it works (very briefly)

  1. The user does: chooses signals/filters of interest in the dApp or Telegram bot.
  2. The system does: aggregates data and produces analytical views/alerts (some features are claimed as AI‑based analytics).
  3. The user gets: analytical results and the ability to execute trades via the Telegram bot (claimed).
  4. Where the blockchain is: onchain — the ASCN token on the Arbitrum One network.
  5. Token role: access to features/terms of use (token‑gated), staking and governance (claimed in the documentation).

Quick links: AI thesis fit

Project passport

Field Value
Project name AlphaScan
Also known as (aliases) ASCN, AlphaScan AI
Logo (logo) ../assets/776_alphascan_logo.svg
Token symbol (ticker) ASCN
Category AI/Analytics | DeFi
Primary chain (chain) Arbitrum One
Type EVM
Network status mainnet
Consensus (consensus) L2 (Optimistic Rollup, Arbitrum One on Ethereum)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0x1B8d516E2146D7a32Aca0FcBf9482db85fD42c3a
Token model (token_type) —
Max supply 49,833,333.310025190590848336 ASCN
Issuance —
Tokenomics (tokenomics, brief) The token is positioned as utility+governance; there is staking (see docs).
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI-based analytics on social/on-chain data
Use‑case (use_case) signal analytics + Telegram trading
DecAI Fit — AI thesis fit 4/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 2 / onchain_score 1 / token_score 2 / evidence_score 3
Last verified 2026-02-11

General project overview

AlphaScan AI is described as a modular analytics platform combined with a Telegram bot. Per Tier‑1 documentation, the project aggregates data (social media/onchain) and offers the user customizable signals; some analytics are claimed as “AI‑based”. The ASCN token on Arbitrum One is positioned as a utility and governance token, including for access to advanced features and staking.

Features/modules

  • dApp: the app.alphascan.xyz interface (claimed in the docs).
  • Telegram bot: analytics and trading via AlphaScanTradingBot.
  • AI‑based analytics (claimed): analytics models described in the docs/roadmap.

Typical scenarios

  • Scenario 1: a user configures a signal/alert → receives notifications and analytical context (claimed).
  • Scenario 2: a user uses the Telegram bot to execute a trade (claimed).

Getting started (wallet/network)

  • What you need: access to the dApp/Telegram bot and an Arbitrum One wallet (if onchain features are used).
  • Network/chain: Arbitrum One.
  • Fees: Arbitrum One network fees for transactions.

Architecture/tech (non‑AI)

  • Components: dApp + Telegram bot (offchain), the ASCN token (onchain).
  • Participant roles: users, service operators, Arbitrum/Ethereum infrastructure.
  • Where logic runs: offchain — data collection/processing and analytics; onchain — the token and related operations.
  • Dependencies: Arbitrum One infrastructure (RPC/wallets), social media/onchain data sources (as claimed in the docs).

Token/economics (expanded, no forecasts)

  • Token utility: access to features (token‑gated), staking, governance (claimed in Tier‑1 docs).
  • Supply parameters: max total supply ~49.83M ASCN (onchain).
  • Who pays fees: users (Arbitrum One network fees) for transactions.
  • Where fees go: to validators/the sequencer and L2 infrastructure participants (within the network).
  • Issuance/burn: —.
  • Incentive mechanisms: staking is specified in Tier‑1 docs (for details — see links_* / Evidence).

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: risks of smart contracts and the offchain service/bot; detailed analysis requires public reports/postmortems.

Project status and timeline

  • Current status: mainnet (Arbitrum One); the dApp and Telegram bot are available via the links.
  • Key releases/milestones: —.
  • Roadmap: published in Tier‑1 docs (see links_*).

Ecosystem/integrations

  • Integrations: the Telegram bot and dApp (see links_*).
  • Partners: —.
  • Where it’s actually used: within the described dApp/bot scenarios (additional cases — not established per Tier‑1).

AI component of the project

  • What is real AI here? In Tier‑1 docs, “AI‑based analytics models” are claimed as part of analytics; detailed quality metrics and a tech description of the models were not found per Tier‑1.
  • What is truly onchain? The ASCN token on the Arbitrum One network is confirmed onchain.
  • Why is a token needed? In Tier‑1 docs, the token is described as utility+governance (access to features, staking).
  • Red flags (based on the information found): absence of AI model quality metrics/benchmarks and their tech description; a substantial part of the functionality is offchain (bot/service).

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): AI is described as part of analytics (not only intent/roadmap).
  • Evidence: Tier‑1 — https://alphascan.gitbook.io/docs
  • Why sufficient / why not (one line): A Tier‑1 description of AI‑based analytics is available; the intent flag is not used.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): The documentation describes AI‑based analytics models as an additional layer of analysis.
  • Evidence: Tier‑1 — https://alphascan.gitbook.io/docs ; https://alphascan.gitbook.io/docs/economics/roadmap
  • Why sufficient / why not (one line): There are Tier‑1 claims about the use of AI in analytics.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): There are available product surfaces: a dApp and a Telegram bot.
  • Evidence: Tier‑1 — https://app.alphascan.xyz/ ; https://t.me/AlphaScanTradingBot
  • Why sufficient / why not (one line): The presence of a working interface/bot satisfies the demo surface criterion.
  • 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): No Tier‑1 AI model quality benchmark/metric was found.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): The tech description/architecture of AI models and their versions are not established in Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without architecture/versions, the flag remains 0.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Arbitrum One
  • Addresses/identifiers: ASCN ERC‑20 token contract: 0x1B8d516E2146D7a32Aca0FcBf9482db85fD42c3a
  • Evidence: Tier‑1 — https://arbiscan.io/token/0x1B8d516E2146D7a32Aca0FcBf9482db85fD42c3a
  • Why sufficient / why not (one line): The token contract and supply parameters are verifiable onchain.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: not established (other than the token).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): No Tier‑1 confirmation of key onchain logic of the product, beyond the token, was found.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 justification that onchain is critical.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, ASCN, on the Arbitrum One network.
  • Evidence: Tier‑1 — https://arbiscan.io/token/0x1B8d516E2146D7a32Aca0FcBf9482db85fD42c3a
  • 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): The use of ASCN specifically as a payment token for the service is not established in Tier‑1.
  • Evidence: Tier‑1 — https://alphascan.gitbook.io/docs/ascn/utility
  • Why sufficient / why not (one line): Utility describes access/terms and staking, but not mandatory payment for services with the token.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): In Tier‑1 docs, ASCN staking and access to staking pools are described.
  • Evidence: Tier‑1 — https://alphascan.gitbook.io/docs/ascn/utility
  • Why sufficient / why not (one line): Staking is part of the token mechanics (incentives).
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): In Tier‑1 docs, the ASCN token is described as a governance token.
  • Evidence: Tier‑1 — https://alphascan.gitbook.io/docs/ascn/utility
  • Why sufficient / why not (one line): A direct Tier‑1 claim about the governance role of the token.
  • 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 the claimed features (access/staking/governance) is not established.
  • Evidence: Tier‑1 — https://alphascan.gitbook.io/docs/ascn/utility
  • Why sufficient / why not (one line): Additional details of the mechanics are needed to confidently assert replaceability.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://alphascan.gitbook.io/docs General description of the product (dApp + Telegram bot) and its purpose (analytics/signals).
Tier‑1 https://alphascan.gitbook.io/docs/economics/roadmap The presence of AI‑based analytics models (roadmap).
Tier‑1 https://alphascan.gitbook.io/docs/ascn/utility ASCN token utility: access to features, staking, governance (claimed).
Tier‑1 https://arbiscan.io/token/0x1B8d516E2146D7a32Aca0FcBf9482db85fD42c3a Onchain facts: the ASCN token, Arbitrum One network, contract, max supply.
Tier‑1 https://app.alphascan.xyz/ Demo surface: dApp.
Tier‑1 https://t.me/AlphaScanTradingBot Demo surface: Telegram bot.
Tier‑2 https://coinmarketcap.com/currencies/alphascan/ Aggregator profile (for reference).

No comments to display

Back to top