Skip to main content

bitsCrunch

bitsCrunch (BCUT) — 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).

bitsCrunch — an AI/Analytics | Infra project (AI‑powered onchain analytics & forensics, focused on NFTs: wash‑trade/fraud/valuation), token (symbol: BCUT) on the Ethereum network.

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 platform/API for analytics and forensics of Web3 activity (especially NFTs), including detection of wash‑trading and counterfeits, valuation and transaction monitoring.
  • Who it’s for: Web3 developers/projects and users/analysts who need access to data/signals and investigation tools.
  • Why onchain/token: the BCUT token is used as the ecosystem’s utility token (access to services/staking, per the project’s claim); onchain — the token itself and the use of blockchain data as source material.

How it works (very briefly)

  1. The user does: requests analytics through the product/dashboard/API (for example, on an NFT collection/wallet/transaction).
  2. The system does: aggregates onchain data and applies ML/AI models to detect patterns (wash trading, counterfeit) and perform calculations.
  3. The user gets: signals/reports/estimates/indicators and data for investigations/products.
  4. Where the blockchain is: the input data is onchain events/transactions; the BCUT token is an ERC‑20 on Ethereum.
  5. Token role: a utility token for access/staking (per the project’s claim).

Quick links: AI thesis fit

Project passport

Field Value
Project name bitsCrunch
Also known as (aliases) BCUT, bitsCrunch Token
Logo (logo) ../assets/209_bitscrunch_logo.svg
Token symbol (ticker) BCUT
Category AI/Analytics | 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 0xBEF26Bd568e421D6708CCA55Ad6e35f8bfA0C406
Token model (token_type) utility (access + service access + staking)
Max supply 1,000,000,000 BCUT (max total supply; Etherscan)
Issuance fixed (max supply)
Tokenomics (tokenomics, brief) the ecosystem’s utility token; in the FAQ it is claimed as a “native digital utility token” for access to bitsCrunch services
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) the GitHub org README claims “Raised over $12 million …” (no details in this card)
AI component (ai_component) AI/ML for NFT forensics (wash trade, forgery, valuation)
Use‑case (use_case) NFT analytics/forensics + on-chain activity
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 1 / 1 / 2 / 2
Last verified 2026-02-06

General project overview

bitsCrunch is positioned as an AI‑powered platform for analytics and forensics of Web3 data, including NFTs, wallets and transactions, with access via an API and products/dashboards. The website lists tools for detecting wash‑trading patterns and NFT counterfeits, monitoring transactions and estimating NFT value. In the organization’s public README on GitHub, the project describes itself as a “decentralized, AI‑powered data network”, but the technical part of the decentralization (for example, a network of nodes with onchain logic) is not disclosed in the extracted Tier‑1 materials.

Features/modules

  • Wash trade detection: an AI/ML solution for detecting wash‑trading patterns (per the website).
  • Forgery / counterfeit detection: detection of fake NFTs/logos/brand imitations (per the website).
  • Price estimation: AI‑based estimation of NFT value based on sales/metadata and other factors (per the website).
  • Onchain analytics APIs / monitoring: access to data/analytics via an API (per the website and the GitHub org README).

Typical scenarios

  • Scenario 1 (dev): a project integrates the API → receives signals/data on NFTs/wallets → builds a product (scoring/anti‑fraud).
  • Scenario 2 (analyst): checks a collection/activity → receives indicators of wash‑trading/counterfeits/anomalies.

Getting started (wallet/network)

  • What you need: access to the bitsCrunch product/API (per the website).
  • Network/chain: the BCUT token — Ethereum.
  • Fees: Ethereum gas for operations with the token; API payment/terms — per the product.

Architecture/tech (non‑AI)

  • Components: —
  • Participant roles: —
  • Where logic runs: —
  • Dependencies: —

Token/economics (expanded, no forecasts)

  • Token utility: —
  • Protocol necessity drivers: —
  • Who pays fees: —
  • Where fees go: —
  • Issuance/burn: —
  • Security/incentive mechanisms: —
  • Distribution and token issuance schedule: —
  • Treasury: —

Governance

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

Security and incidents

  • Audits: — (if many — put a table below)
  • Bug bounty: —
  • Incidents: —
  • Threat model: —

Project status and timeline

  • Current status: —
  • Key releases/milestones: —
  • Roadmap: —

Ecosystem/integrations

  • Integrations: —
  • Partners: —
  • Where it’s actually used: —

AI component of the project

  • What is real AI here? On the website and in the GitHub org README, the project claims AI/ML components for detecting wash‑trading/counterfeits and for NFT analytics.
  • What is truly onchain? The BCUT token is an ERC‑20 on Ethereum; the data for analytics is taken from public blockchains.
  • Why is a token needed? In the project’s FAQ, BCUT is described as a utility token that gives access to bitsCrunch services; a staking‑based access model is also mentioned.
  • Red flags (based on the information found): there are few technical details of the models/metrics/benchmarks in Tier‑1 (AI_3=0); a “decentralized data network” is claimed in the README, but the decentralization mechanism (nodes/protocol) is not verified in the extracted materials.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality low 1
Onchain necessity low 1
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): AI is described as part of the current product, not as a plan to “add AI in the future”.
  • Evidence: Tier‑1 — https://bitscrunch.com/
  • Why sufficient / why not (one line): this is a product description, not a roadmap.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): AI/ML is used to detect wash‑trading and NFT counterfeits and to estimate NFT value.
  • Evidence: Tier‑1 — https://bitscrunch.com/ ; https://github.com/bitscrunch-protocol
  • Why sufficient / why not (one line): the website describes the AI tools; the GitHub README confirms an “AI-enabled … protocol”.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): a public reproducible demo artifact (a dataset/example queries with expected results/a model repo) is not presented in the extracted Tier‑1 sources.
  • Evidence: Tier‑1 — https://bitscrunch.com/ ; https://github.com/bitscrunch-protocol
  • Why sufficient / why not (one line): there is a description, but 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 — https://bitscrunch.com/
  • Why sufficient / why not (one line): accuracy/quality metrics of the models are not published in the extracted Tier‑1 materials.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): the architecture/versions of the models and the technical details of the AI implementation are not disclosed in Tier‑1 at a level sufficient for verification.
  • Evidence: Tier‑1 — https://bitscrunch.com/ ; https://github.com/bitscrunch-protocol
  • Why sufficient / why not (one line): there is a high‑level description, but no technical details.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: 0xBEF26Bd568e421D6708CCA55Ad6e35f8bfA0C406
  • Evidence: Tier‑1 — https://etherscan.io/token/0xBEF26Bd568e421D6708CCA55Ad6e35f8bfA0C406
  • Why sufficient / why not (one line): Etherscan confirms the contract and max supply.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: the extracted Tier‑1 sources do not show that the core analytics/forensics is executed by smart contracts (rather an offchain service based on blockchain data).
  • Evidence: Tier‑1 — https://bitscrunch.com/ ; https://github.com/bitscrunch-protocol
  • Why sufficient / why not (one line): the product description points to a SaaS/API approach.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: the product analyzes onchain data, but it can be imagined as a centralized/offchain service; there is no Tier‑1 proof of the criticality of the onchain logic.
  • Evidence: Tier‑1 — https://bitscrunch.com/
  • Why sufficient / why not (one line): there are insufficient arguments that onchain is a necessary computation layer.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, BCUT.
  • Evidence: Tier‑1 — https://etherscan.io/token/0xBEF26Bd568e421D6708CCA55Ad6e35f8bfA0C406
  • Why sufficient / why not (one line): confirmed by the explorer.
  • 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): in the FAQ on the website, BCUT is described as a utility token that gives access to bitsCrunch services.
  • Evidence: Tier‑1 — https://bitscrunch.com/
  • Why sufficient / why not (one line): the page has an FAQ describing the token’s utility.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): the FAQ mentions a staking‑based model of access to services (“stake a certain amount … to avail our services”).
  • Evidence: Tier‑1 — https://bitscrunch.com/
  • Why sufficient / why not (one line): staking links incentives/access to the token.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): governance mechanics with the token is not confirmed in the extracted Tier‑1 sources.
  • Evidence: Tier‑1 — https://github.com/bitscrunch-protocol
  • Why sufficient / why not (one line): the README does not describe token governance.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the token is built into the access/staking model, but could theoretically be replaced with a subscription/fiat; there is no proof of irreplaceability in Tier‑1.
  • Evidence: Tier‑1 — https://bitscrunch.com/
  • Why sufficient / why not (one line): there is no formal argument that “without the token the core breaks down”.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://bitscrunch.com/ product modules + FAQ on BCUT utilities/staking
Tier‑1 https://github.com/bitscrunch-protocol description of the project as an “AI-enabled … protocol” and a mention of the token/contracts
Tier‑1 https://etherscan.io/token/0xBEF26Bd568e421D6708CCA55Ad6e35f8bfA0C406 the BCUT contract and max supply
Tier‑1 — the whitepaper PDF in links_* is unavailable from the available sources.

No comments to display

Back to top