Skip to main content

Big Data Protocol

Big Data Protocol (BDP) — 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).

Big Data Protocol — a Data / DeFi project on Ethereum, token BDP. An AI component as a key part of the product is not confirmed in the extracted Tier‑1.

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 token/protocol on Ethereum related to the data theme (data label on Etherscan).
  • Who it’s for: DeFi/ecosystem users interacting with the project’s token and smart contracts.
  • Why onchain/token: the main object is the onchain BDP token and the contracts; the token is needed for participation in the protocol’s mechanics (details in the extracted sources are limited).

How it works (very briefly)

  1. The user does: acquires/uses the BDP token and interacts with the protocol’s contracts.
  2. The system does: executes onchain operations (transfers/staking/pools) tied to the contract logic.
  3. The user gets: access to the economy/mechanics implemented by smart contracts.
  4. Where the blockchain is: Ethereum (the token contract and transactions).
  5. Token role (if any): utility within the protocol (within the available information — the token and contracts).

Quick links: AI thesis fit

Project passport

Field Value
Project name Big Data Protocol
Also known as (aliases) BDP
Logo (logo) ../assets/253_big-data-protocol_logo.ico
Token symbol (ticker) BDP
Category Data | DeFi
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) — (not confirmed by Tier‑1)
Project status (status) active (contracts and transfers exist)
Token (standard) ERC-20
Token contract 0xf3dcbc6D72a4E1892f7917b7C43b74131Df8480e
Token model (token_type) unknown
Max supply 64,923,252.851851851851851851 BDP (per Etherscan)
Issuance fixed (per max total supply on Etherscan)
Tokenomics (tokenomics, brief) the history of a reward mechanics incident and the “effective burn” of ~5.7M BDP is known (incident report).
Governance — (not found in the extracted Tier‑1)
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) unknown
Use‑case (use_case) data tokenization + DeFi mechanics
DecAI Fit — AI thesis fit 0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary 0 / 2 / 1 / 2
Last verified 2026-02-11

General project overview

Within the available Tier‑1 sources for this card, the existence of the BDP token on the Ethereum network and the smart contracts/transactions associated with it (Etherscan) are reliably confirmed, as well as a public incident report on a reward mechanism error in 2021.

Claims “about AI” as a key functionality of the protocol were not found in the extracted Tier‑1 sources, so DecAI Fit is forced to 0/6 (per the rule: if AI score = 0, the final DecAI Fit = 0).

Features/modules

  • BDP token (ERC‑20): the basic onchain artifact, confirmed by Etherscan.
  • Contract base: the public bdp-contracts repository (Tier‑1).
  • Incident report (reward mechanics): a public report on the reward logic bug and its consequences (Tier‑1 PDF).

Typical scenarios

  • Scenario 1: a user transfers/holds BDP and interacts with the onchain contracts (Etherscan).
  • Scenario 2: reads the incident report and assesses the risks/changes in the mechanics (Tier‑1 PDF).

Getting started (wallet/network)

  • What you need: an EVM wallet for ERC‑20 operations.
  • Network/chain: Ethereum.
  • Fees: Ethereum fees for transfers/contract calls.

Architecture/tech (non‑AI)

  • Components: the BDP token (ERC‑20), the protocol contracts (per the repository), the public incident report (PDF).
  • Participant roles: token holders and users of the protocol’s DeFi mechanics (if still relevant); the protocol team/operator.
  • Where logic runs: onchain (Ethereum) for the token/contracts; offchain components are not verified in the current Tier‑1 extractions.
  • Dependencies: Ethereum RPC, DeFi infrastructure.

Token/economics (expanded, no forecasts)

  • Token utility: — (not confirmed as “payment/access/governance” in the current extracted Tier‑1 for this card; the incentive context of the reward mechanics is confirmed).
  • Protocol necessity drivers: the reward mechanics in the contracts (incident report); the rest of the utility requires additional Tier‑1 verification.
  • Who pays fees: Ethereum users for onchain operations.
  • Where fees go: to Ethereum validators.
  • Issuance/burn: fixed (max total supply per Etherscan); the incident report describes an “effective burn” as a consequence of the reward mechanics bug.
  • Security/incentive mechanisms: reward minting/limits are described in the incident report; no other incentives/slashing were extracted.
  • 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: —.
  • Bug bounty: —.
  • Incidents: a public incident report on the reward mechanics (Tier‑1 PDF).
  • Threat model: risks of contract vulnerabilities and incentive mechanics errors; the need to verify whether the protocol/contracts are still current.

Project status and timeline

  • Current status: the token and contracts exist onchain; whether the product layer is still current requires separate verification.
  • Key releases/milestones: —.
  • Roadmap: —.

Ecosystem/integrations

  • Integrations: Ethereum (token/contracts), the GitHub repository, the public incident report.
  • Partners: —.
  • Where it’s actually used: — (the current Tier‑1 extractions contain no usage cases/metrics).

AI component of the project

  • What is real AI here? an AI component is not confirmed in the extracted Tier‑1 sources.
  • What is truly onchain? the ERC‑20 BDP token on Ethereum and the history of the incident in the reward contract logic (incident report).
  • Why is a token needed? for participation in the protocol economy/contracts (per the available sources, it is the “center” of the system).
  • Red flags (based on the information found): AI‑washing — if the project is marketed as “AI”, this needs to be confirmed by separate Tier‑1 materials; onchain‑washing — a minimal onchain set (a token) is not equal to a “protocol”; token‑washing — the utility needs to be verified against the full docs.

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 medium 1
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 intentions/roadmap were not found in the extracted Tier‑1.
  • Evidence: Tier‑1 — https://etherscan.io/token/0xf3dcbc6D72a4E1892f7917b7C43b74131Df8480e
  • Why sufficient / why not (one line): Etherscan confirms the token, but not the AI thesis.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): an AI function is not confirmed.
  • Evidence: Tier‑1 — https://bigdataprotocol.com/BDP_IncidentReport.pdf
  • Why sufficient / why not (one line): the incident report is about the reward mechanics, not about AI.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): no AI demo was found.
  • Evidence: Tier‑1 — https://bigdataprotocol.com/BDP_IncidentReport.pdf
  • Why sufficient / why not (one line): the document contains no 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://bigdataprotocol.com/BDP_IncidentReport.pdf
  • Why sufficient / why not (one line): there are no AI metrics.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): a technical description of AI is absent in the extracted Tier‑1.
  • Evidence: Tier‑1 — https://github.com/bigdataprotocol/bdp-contracts
  • Why sufficient / why not (one line): the GitHub repository is about contracts, not about AI models.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum.
  • Addresses/identifiers: the BDP token contract: 0xf3dcbc6D72a4E1892f7917b7C43b74131Df8480e.
  • Evidence: Tier‑1 — https://etherscan.io/token/0xf3dcbc6D72a4E1892f7917b7C43b74131Df8480e
  • Why sufficient / why not (one line): the contract and the network are confirmed by the explorer.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: the protocol logic of rewards/minting/pools existed and affected users (described in the incident report).
  • Evidence: Tier‑1 — https://bigdataprotocol.com/BDP_IncidentReport.pdf
  • Why sufficient / why not (one line): the existence of onchain logic is confirmed by the analysis of the bug in the contract mechanics.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: the extracted Tier‑1 contain no strict test of the irreplaceability of the blockchain (there is only the fact that the token/contracts are onchain).
  • Evidence: Tier‑1 — https://bigdataprotocol.com/BDP_IncidentReport.pdf
  • Why sufficient / why not (one line): the document confirms onchain execution, but does not prove that the product is impossible without a blockchain.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the BDP token exists (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0xf3dcbc6D72a4E1892f7917b7C43b74131Df8480e
  • Why sufficient / why not (one line): Etherscan confirms the token and the contract.
  • 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): a payment utility of the token is not confirmed in the extracted Tier‑1.
  • Evidence: Tier‑1 — https://bigdataprotocol.com/BDP_IncidentReport.pdf
  • Why sufficient / why not (one line): the document is about the reward incident, not about payments.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): the reward mechanics and token distribution via contracts are described (including the consequences of the bug).
  • Evidence: Tier‑1 — https://bigdataprotocol.com/BDP_IncidentReport.pdf
  • Why sufficient / why not (one line): the incident report directly describes reward minting/limits and the outcomes.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): the governance role of the token is not confirmed in the extracted Tier‑1.
  • Evidence: Tier‑1 — https://etherscan.io/token/0xf3dcbc6D72a4E1892f7917b7C43b74131Df8480e
  • Why sufficient / why not (one line): the explorer does not prove governance.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the irreplaceability of the token is not proven in the extracted Tier‑1.
  • Evidence: Tier‑1 — https://bigdataprotocol.com/BDP_IncidentReport.pdf
  • Why sufficient / why not (one line): without a full description of the protocol, irreplaceability cannot be strictly asserted.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://etherscan.io/token/0xf3dcbc6D72a4E1892f7917b7C43b74131Df8480e The BDP token address and max supply.
Tier‑1 https://github.com/bigdataprotocol/bdp-contracts The existence of contract code (level of proof — the repo sources).
Tier‑1 https://bigdataprotocol.com/BDP_IncidentReport.pdf Postmortem/incident report on the reward mechanism bug and the “effective burn” of ~5.7M BDP.
Tier‑2 https://coinmarketcap.com/currencies/big-data-protocol/ Reference profile.
Tier‑1 https://bigdataprotocol.com/docs Project documentation (Tier‑1); the content was not verified.

No comments to display

Back to top