ProChain
ProChain — 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).
ProChain — an Infra project on the Ethereum network, token (symbol: PRA).
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 with an onchain token and public repositories (an ERC‑20 contract and a bounty program repository; per Tier‑1 GitHub).
- Who it’s for: developers/contributors (the bounty program and node development on Substrate — per Tier‑1).
- Why onchain/token: the token contract exists on Ethereum; the bounty program states that rewards may be paid in the PRA token.
How it works (very briefly)
- The user does: participates in development/completes bounty program tasks.
- The system does: accepts reports/decisions via GitHub issues (per the bounty program description).
- The user gets: a reward (in ERC‑20 or the PRA token — as claimed in the bounty program).
- Where the blockchain is: the PRA token (ERC‑20) on Ethereum.
- Token role: bounty payouts and (possibly) other roles — not established per Tier‑1.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | ProChain |
| Also known as (aliases) | PRA, Prochain |
| Logo (logo) | ../assets/680_prochain_logo.svg |
| Token symbol (ticker) | PRA |
| Category | Infra |
| Primary chain (chain) | Ethereum |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Ethereum) |
| Launch date (launch_date) | — |
| Project status (status) | — |
| Token (standard) | ERC-20 |
| Token contract | 0x9041Fe5B3FDEA0f5e4afDC17e75180738D877A01 |
| Token model (token_type) | — |
| Max supply | — |
| Issuance | — |
| Tokenomics (tokenomics, brief) | Tier‑1: the PRA token is mentioned as the bounty payout currency; supply parameters are not established. |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | yes |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | — |
| Use‑case (use_case) | development/contributions (bounties) |
| DecAI Fit — AI thesis fit | 0/6 — no AI reality and no AI intent (ai_score=0) |
| DecAI Fit component summary | ai_score 0 / onchain_score 1 / token_score 1 / evidence_score 2 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://chain.pro/ |
| Docs | https://github.com/ProChain/WhitePaper |
| GitHub | https://github.com/ProChain |
| Releases / Changelog | https://github.com/ProChain/TokenContract |
| Whitepaper | https://github.com/ProChain/WhitePaper/blob/master/ProChainWhitePaper1206.pdf |
| Roadmap | — |
| Security advisories | — |
| Explorer | https://etherscan.io/token/0x9041Fe5B3FDEA0f5e4afDC17e75180738D877A01 |
| App / Demo | — |
| X | https://twitter.com/prochaintech |
| Discord | — |
| Telegram | https://t.me/ProChainTech |
| Medium | — |
| Audit report(s) | — |
| Bug bounty | https://github.com/ProChain/prochain-bounty-program |
| CoinGecko (profile, reference) | — |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/prochain/ |
General project overview
The Tier‑1 ProChain repositories contain the source code of the ERC‑20 contract, a bounty program repository for developers (including Substrate tasks) and a separate WhitePaper repository (PDF). We use the whitepaper as the Tier‑1 description of the project’s purpose/mechanics. No AI component was found in Tier‑1, so DecAI Fit = 0/6.
Features/modules
- ERC‑20 contract: a repository with the token code.
- Bounty program: tasks/rules for contributors, payouts in ERC‑20 or PRA (as claimed).
- Substrate development: a mention of a Substrate node and development tasks (as context).
Typical scenarios
- Scenario 1: a contributor takes a bounty task → submits a solution → receives a payout (per the bounty program rules).
- Scenario 2: a developer reads/uses the ERC‑20 contract code as a project artifact.
Getting started (wallet/network)
- What you need: a GitHub account (to participate in the bounty) and development skills (Rust/git — per the list in the bounty program).
- Network/chain: Ethereum (for the token).
- Fees: Ethereum fees apply to operations with the PRA token.
Architecture/tech (non‑AI)
- Components: the ERC‑20 contract (onchain), development/contribution repositories (offchain).
- Participant roles: contributors/developers, token holders.
- Where logic runs: the token — onchain; the bounty/development process — offchain.
- Dependencies: Ethereum.
Token/economics (expanded, no forecasts)
- Token utility: bounty payouts (per the Tier‑1 description).
- Protocol necessity drivers: not established.
- Who pays fees: token users in transactions (gas).
- Where fees go: to Ethereum validators (gas).
- Issuance/burn: — (not established).
- Security/incentive mechanisms: — (not established).
- Distribution and token issuance schedule: — (not established).
- Treasury: — (not established).
Governance
- Who makes decisions: — (not established).
- How protocol parameters change: — (not established).
- Where decisions are discussed/made: —.
- Keys/multisig: —.
Security and incidents
- Audits: —.
- Bug bounty: there is a bounties program (see links_*).
- Incidents: —.
- Threat model: the absence of public audits and limited Tier‑1 tech docs/addresses of key contracts (other than the token).
Project status and timeline
- Current status: — (not established).
- Key releases/milestones: —.
- Roadmap: —.
Ecosystem/integrations
- Integrations: — (not established).
- Partners: — (not established).
- Where it’s actually used: — (not established).
AI component of the project
- What is real AI here? No Tier‑1 confirmation of an AI component was found.
- What is truly onchain? the ERC‑20 token (the contract on Etherscan).
- Why is a token needed? Tier‑1: bounty payouts may be made in the PRA token.
- Red flags (based on the information found): token‑washing (the role of the token outside bounties/payments is not established); part of the details requires re‑checking against onchain data (token metadata/current interfaces).
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 | low | 1 |
| Token necessity | low | 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): No Tier‑1 AI intent was found.
- Evidence: Tier‑1 — https://github.com/ProChain/prochain-bounty-program
- Why sufficient / why not (one line): The repository describes bounties/development, not an AI roadmap.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 0
- Claim (one line): AI features are not described in Tier‑1.
- Evidence: Tier‑1 — https://github.com/ProChain/prochain-bounty-program
- Why sufficient / why not (one line): There is no description of an AI module/model.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): No demo of an AI component was found (an AI component is not established).
- Evidence: Tier‑1 — https://github.com/ProChain/prochain-bounty-program
- Why sufficient / why not (one line): AI_2 requires a demo surface of AI.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —
- Context (version/date/how measured): —
- Evidence: Tier‑1 — https://github.com/ProChain/prochain-bounty-program
- Why sufficient / why not (one line): AI metrics are not applicable (an AI component is not established).
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): No tech description of an AI component was found.
- Evidence: Tier‑1 — https://github.com/ProChain/prochain-bounty-program
- Why sufficient / why not (one line): The repositories do not describe an AI module.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum
- Addresses/identifiers: ERC‑20 contract: 0x9041Fe5B3FDEA0f5e4afDC17e75180738D877A01
- Evidence: Tier‑1 — https://github.com/ProChain/TokenContract
- Why sufficient / why not (one line): The Tier‑1 repository directly points to the contract’s web interface on Etherscan.
- 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 — https://github.com/ProChain/TokenContract
- Why sufficient / why not (one line): 1 requires Tier‑1 artifacts of protocol logic; not found per Tier‑1.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: not established.
- Evidence: Tier‑1 — https://github.com/ProChain/TokenContract
- Why sufficient / why not (one line): There is no Tier‑1 argument for onchain criticality.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): The PRA token is mentioned in Tier‑1.
- Evidence: Tier‑1 — https://github.com/ProChain/prochain-bounty-program
- Why sufficient / why not (one line): The bounty program says “paid out in … PRA token”.
- 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): The Tier‑1 whitepaper describes payments/settlement in PRO tokens for completing advertising tasks via smart contracts.
- Evidence: Tier‑1 — https://raw.githubusercontent.com/ProChain/WhitePaper/master/README.md ; https://github.com/ProChain/WhitePaper/blob/master/ProChainWhitePaper1206.pdf
- Why sufficient / why not (one line): Tier‑1 describes the “serving task = smart contract” model and settlement in the token (payments).
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): Staking/slashing/protocol incentives with the token are not established.
- Evidence: Tier‑1 — https://github.com/ProChain/prochain-bounty-program
- Why sufficient / why not (one line): There is no description of such a mechanism.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): A governance role of the token is not established.
- Evidence: Tier‑1 — https://github.com/ProChain/prochain-bounty-program
- Why sufficient / why not (one line): There is no Tier‑1 description of governance.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 0
- Claim (one line): The replaceability of the token is not established.
- Evidence: Tier‑1 — https://github.com/ProChain/prochain-bounty-program
- Why sufficient / why not (one line): Insufficient data.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://github.com/ProChain/TokenContract | Tier‑1: the ERC‑20 contract repository; a link to the contract on Etherscan. |
| Tier‑1 | https://github.com/ProChain/prochain-bounty-program | Tier‑1: bounty program; payouts in ERC‑20 or the PRA token; contacts/repositories. |
| Tier‑1 | https://github.com/ProChain/WhitePaper | Tier‑1: whitepaper repository (PDF) + introduction/description of the project’s goals. |
| Tier‑1 | — | No Tier‑1 source for claim “the project’s AI component” was found. |
No comments to display
No comments to display