Skip to main content

Bepro Network

Bepro Network (BEPRO) — 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).

Bepro Network describes a “task-based marketplace” (a marketplace of tasks/bounties) for organizations and builders/curators, where tasks are published with rewards, and part of the process (recognition of contribution, distribution/dispute logic) is positioned as onchain.

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 onchain‑oriented task marketplace (tasks/bounties) for organizations and builders, with curator roles and payout distribution mechanisms.
  • Who it’s for: organizations/DAO that need a transparent process for tasks and payouts; builders/curators who complete tasks and participate in distributions.
  • Why onchain/token: onchain is used as part of transparency and of the distribution/recognition rules; the BEPRO token is described as a utility ERC‑20, with a role in managing the network’s disputes. AI component is not identified in the card’s Tier‑1 sources, so ai_score = 0 ⇒ DecAI Fit = 0/6.

How it works (very briefly)

  1. The user does: an organization publishes a task and assigns a reward; builders complete it; curators/the community can participate in validation and distribution proposals.
  2. The system does: maintains the “task marketplace”, allows to “validate and reward”, and (per the website) issues an onchain non‑transferable NFT (ERC‑721) as recognition of participation.
  3. The user gets: a payout (in the organization’s token/USDC/another ERC‑20 — per the website) and onchain recognition.
  4. Where the blockchain is: the BEPRO token on Ethereum; the onchain part of the product is described in the documentation as the network protocol and its mechanics.
  5. Token role (if any): in the documentation, the BEPRO token is described as a “utility ERC20 token” for managing disputes and receiving rewards for contribution.

Quick links: AI thesis fit

Project passport

Field Value
Project name Bepro Network
Also known as (aliases) BEPRO; BetProtocolToken (historical name in Etherscan)
Logo (logo) ../assets/300_bepro-network_logo.svg
Token symbol (ticker) BEPRO
Category Dev/Marketplace | Infra
Primary chain (chain) Ethereum
Type EVM
Network status hybrid alpha
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) active (website/docs available)
Token (standard) ERC-20
Token contract 0xcf3c8be2e2c42331da80ef210e9b1b307c03d36a
Token model (token_type) utility (governance)
Max supply 10,000,000,000 BEPRO (Etherscan Max Total Supply)
Issuance fixed max total supply (per Etherscan)
Tokenomics (tokenomics, brief) tokenomics/distribution schedule are published in the official article
Governance self‑managed protocol, managed by BEPRO token (per the docs)
Admins/keys —
Audit yes (audit sections on the official website; public reports require separate verification)
Bug bounty yes
Team (team) —
Funding (investors/funding) —
AI component (ai_component) unknown
Use‑case (use_case) task + bounty marketplace
DecAI Fit — AI thesis fit 0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary 0 / 2 / 2 / 3
Last verified 2026-02-11

General project overview

The Bepro website describes a “task-based marketplace” where organizations create tasks with rewards, and builders and curators complete and review the work. Onchain recognition (non‑transferable NFT, ERC‑721) and the ability to pay with “your own token” or any ERC‑20 (including USDC) are claimed as additional properties.

The Bepro.Network documentation describes the protocol elements and the role of the BEPRO token: “self-managed protocol, managed by the BEPRO token”, where token holders can manage the network’s disputes and receive token rewards for contribution.

Features/modules

  • Task marketplace: publication of tasks and rewards.
  • Curators and payout distribution proposals.
  • “Validate and reward” (the process of accepting work and payouts).
  • Onchain non‑transferable NFT (ERC‑721) as recognition of participation (a claim on the website).

Typical scenarios

  • Scenario 1: an organization publishes a task → the community/builders complete it → the organization validates → payout.
  • Scenario 2: an organization delegates validation to curators → curators make a distribution proposal → the distribution takes place (within the network mechanics described in the docs).

Getting started (wallet/network)

  • What you need: an EVM wallet.
  • Network/chain: Ethereum (BEPRO token); for the onchain part of the protocol, Moonbeam mainnet is specified in the bug bounty scope.
  • Fees: network fees (gas) of the selected network.

Architecture/tech (non‑AI)

  • Components: the app.bepro.network web interface (mentioned in the bug bounty), the network’s protocol mechanics (docs).
  • Roles: organizations, builders, curators.
  • Where logic runs: part of the actions/state is described as onchain (docs); UI and communication — offchain.
  • Dependencies: —.

Token/economics (expanded, no forecasts)

  • Token utility: per the docs, BEPRO allows holders to manage the network’s disputes and receive rewards for contribution.
  • Who pays fees: per the website, an organization can pay with “its own token” or any ERC‑20.
  • Issuance/burn: max total supply is fixed in Etherscan (10B).
  • Distribution and token issuance schedule: published in the official article (without an extracted table of parameters within this card).

Governance

  • Who makes decisions: the protocol is described as self‑managed, managed by BEPRO token (the dispute layer in the docs).
  • How protocol parameters change: — (not established per the card’s Tier‑1 sources).

Security and incidents

  • Audits: the website has an “Audited and Verified” section with links to auditors; the specific PDF reports require a separate availability check.
  • Bug bounty: there is a bug bounty page in the docs.
  • Incidents: —.

Project status and timeline

  • Current status: the docs call the current version “hybrid alpha” before the mainnet release.
  • Roadmap: — (there is an external roadmap page, link above).

Ecosystem/integrations

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

AI component of the project

  • What is real AI here? The card’s Tier‑1 sources contain no description of an AI module/AI features.
  • What is truly onchain? The BEPRO token (ERC‑20) and the network’s onchain mechanics (described in the docs and the bug bounty scope).
  • Why is a token needed? In the docs it is described as a utility token for managing disputes and rewards.
  • Red flags (based on the information found): if the project is positioned anywhere as an AI project, this requires separate Tier‑1 evidence (not identified within this card).

DecAI Fit component summary

  • DecAI Fit: 0/6 — no AI reality and no AI intent (ai_score=0)
Component Level Score
AI reality no data 0
Onchain necessity medium 2
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
  • Evidence: —
  • Why sufficient / why not (one line): the card’s Tier‑1 sources contain no AI intent/AI roadmap.

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0

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

  • AI_4 (decision): 0

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum (token)
  • Addresses/identifiers: BEPRO token (Ethereum): 0xcf3c8be2e2c42331da80ef210e9b1b307c03d36a
  • Evidence: Tier‑1 — https://etherscan.io/token/0xcf3c8be2e2c42331da80ef210e9b1b307c03d36a
  • Why sufficient / why not (one line): we confirm the token’s onchain contract in the explorer.

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

  • OC_2 (decision): 1
  • What useful logic is onchain: the network/protocol mechanics (tasks/disputes/oracle reporting) are described in the docs; the bug bounty scope includes the on-chain protocol on Moonbeam mainnet.
  • Evidence: Tier‑1 — https://docs.bepro.network/ ; https://docs.bepro.network/getting-started/the-network ; https://docs.bepro.network/getting-started/bug-bounty
  • Why sufficient / why not (one line): there is a description of protocol logic beyond the token in the official docs.

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • Evidence: —
  • Why sufficient / why not (one line): the card’s sources contain no strict “without the blockchain the product breaks down” test.

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Evidence: Tier‑1 — https://etherscan.io/token/0xcf3c8be2e2c42331da80ef210e9b1b307c03d36a

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 0
  • Evidence: —
  • Why sufficient / why not (one line): mandatory payment for services in BEPRO is not established in the card’s sources.

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

  • TK_2 (decision): 1
  • Claim (one line): the docs describe lock/threshold and a rewards mechanic for participation in the network.
  • Evidence: Tier‑1 — https://docs.bepro.network/getting-started/the-network
  • Why sufficient / why not (one line): participation in the network mechanics is tied to holding/locking the token.

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): the docs state “managed by the BEPRO token” and the token’s role in managing disputes.
  • Evidence: Tier‑1 — https://docs.bepro.network/
  • Why sufficient / why not (one line): the governance role of the token is described in the official documentation.

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Evidence: —
  • Why sufficient / why not (one line): the token is described as part of the network mechanics (disputes/rewards); replaceability is not asserted.

Evidence (table)

Tier Source What it proves
Tier‑1 https://bepro.network/ The “OnChain Task Marketplace” positioning, scenarios (tasks/curators) and the claim about the onchain NFT.
Tier‑1 https://docs.bepro.network/ Description of the BEPRO token and the network/protocol (managed by token, disputes).
Tier‑1 https://docs.bepro.network/getting-started/the-network The network mechanics, including lock/threshold and roles.
Tier‑1 https://docs.bepro.network/getting-started/bug-bounty Scope: on-chain protocol (Moonbeam mainnet) and the application.
Tier‑1 https://etherscan.io/token/0xcf3c8be2e2c42331da80ef210e9b1b307c03d36a The BEPRO contract and max total supply 10B.
Tier‑1 https://bepronetwork.medium.com/tokenomics-afdb24ea3303 The official tokenomics/distribution schedule publication.

No comments to display

Back to top