Skip to main content

FABRK

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

FABRK — a protocol/platform for decentralized “human networks” (social network/social graph, user‑owned data) with a token on Ethereum.

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 open source, blockchain‑powered protocol for social products, where users own their data and receive tokens for online behavior/content (per the whitepaper).
  • Who it’s for: users of social products, content creators, developers of third-party social applications, delegate nodes.
  • Why onchain/token: onchain is needed for accounting/microtransactions and protocol rules; the FAB token is described as a means of micropayments and incentives (including node rewards).

How it works (very briefly)

  1. The user creates/consumes content: the protocol tracks views/interactions.
  2. Micropayments are distributed automatically: viewers “pay”, creators “earn” (per the description of the mechanics).
  3. Developers build social products on top of the protocol: access to the social graph/data with users’ consent.
  4. Where the blockchain is: the protocol’s ledger and consensus; smart contracts/accounting.
  5. Token role: incentives for users/nodes and the microtransaction economy.

Quick links: AI thesis fit

Project passport

Field Value
Project name FABRK
Also known as (aliases) FABRK Foundation
Logo (logo) —
Token symbol (ticker) FAB
Category 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 0x12683dc9eec95a5f742d40206e73319e6b9d8a91
Token model (token_type) utility (payments + staking + rewards)
Max supply —
Issuance —
Tokenomics (tokenomics, brief) The whitepaper describes “viewers pay / creators earn” micropayments and node rewards (delegate nodes) through FAB issuance.
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) Federated learning / AI applicability
Use‑case (use_case) user-owned social data + microtransactions
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 1 / onchain_score 2 / token_score 2 / evidence_score 3
Last verified 2026-02-11

General project overview

Per the Tier‑1 whitepaper, FABRK describes itself as an open source, blockchain‑powered decentralized social networking platform / “people protocol”, where users own data and can receive tokens for creating/consuming content, engagement and “digital labor”. The whitepaper also describes the goal of opening the social graph and data (with users’ consent) to third-party developers so they can compete by creating “true social products”.

The whitepaper separately discusses AI/ML topics in the context of privacy and learning from data (readiness for federated learning is mentioned), but this is presented as applicability/a direction, rather than a proven “AI component of the product”.

Features/modules

  • User‑owned data: the protocol as a “data brokerage”, where data remains with users (per the description).
  • Microtransactions: automatic micropayments between viewers and creators.
  • DPoV consensus/governance: Delegated Proof of Value is described (within the whitepaper).
  • Developer ecosystem: developer access to social data (with privacy/checks taken into account).

Typical scenarios

  • Scenario 1: a user consumes content → a micropayment occurs; the user can “break even” through rewards (per the whitepaper).
  • Scenario 2: a content creator receives rewards for views/engagement (per the whitepaper).
  • Scenario 3: a developer creates a product (feed/search/match‑making) on top of the protocol, using data according to permissions.

Getting started (wallet/network)

  • What you need: an Ethereum wallet for operations with the token and access to FABRK products/interfaces (per the website/whitepaper).
  • Network/chain: Ethereum (ERC‑20).
  • Fees: Ethereum network fees for onchain operations.

Architecture/tech (non‑AI)

  • Components: protocol/ledger, delegate nodes, the FAB token, offchain applications/content (per the description in the whitepaper).
  • Participant roles: users, content creators, product developers, delegate nodes.
  • Where logic runs: accounting/micropayments/consensus — onchain; content and applications — offchain (per the description).

Token/economics (expanded, no forecasts)

  • Token utility: micropayments and rewards for content/behavior; delegate node rewards through issuance (per the whitepaper).
  • Incentive mechanisms: staking + the “historical contribution” metric participate in the distribution of voting responsibility in DPoV (per the whitepaper).

Governance

  • Who makes decisions: not established per Tier‑1.
  • How protocol parameters change: not established per Tier‑1.
  • Where decisions are discussed/made: not established per Tier‑1.
  • Keys/multisig: not established per Tier‑1.

Security and incidents

  • Audits: not found in Tier‑1 sources.
  • Bug bounty: not found in Tier‑1 sources.
  • Incidents: not found in Tier‑1 sources.
  • Threat model: not established per Tier‑1.

Project status and timeline

  • Current status: —.
  • Key releases/milestones: not established per Tier‑1.
  • Roadmap: not found in Tier‑1 sources.

Ecosystem/integrations

  • Integrations: not established per Tier‑1.
  • Partners: not established per Tier‑1.
  • Where it’s actually used: not established per Tier‑1.

AI component of the project

  • What is real AI here? In the Tier‑1 whitepaper, AI/ML is discussed as context (the problem of centralized ML on data and the applicability of federated learning), but no Tier‑1 confirmation of a working AI component of the product was found.
  • What is truly onchain? the FAB token on Ethereum and the protocol/consensus/micropayments described in the whitepaper.
  • Why is a token needed? for micropayments and incentives (viewers/creators/nodes) per the whitepaper.
  • Red flags (based on the information found): AI mentions serve as context/a direction; this should not be interpreted as proof of “AI in the product” without specific artifacts/demos/metrics.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality low 1
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): 1
  • Claim (one line): The whitepaper discusses AI/ML (including federated learning) as an important use case/direction of the protocol.
  • Evidence: Tier‑1 — https://www.fabrk.io/FABRK_Whitepaper_v1.0.pdf
  • Why sufficient / why not (one line): This records AI intent/applicability, but does not prove a working AI component.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): A specific AI feature as a component of the product is not established per Tier‑1.
  • Evidence: Tier‑1 — https://www.fabrk.io/FABRK_Whitepaper_v1.0.pdf
  • Why sufficient / why not (one line): Mentions of AI/ML serve as context/applicability.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): No AI demo was found per Tier‑1.
  • Evidence: Tier‑1 — https://www.fabrk.io/
  • Why sufficient / why not (one line): AI_2=1 requires a verifiable demo surface of the AI part.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://www.fabrk.io/FABRK_Whitepaper_v1.0.pdf
  • Why sufficient / why not (one line): No reproducible set of AI metrics was found per Tier‑1.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): A tech description of the AI model/versions is not established per Tier‑1.
  • Evidence: Tier‑1 — https://www.fabrk.io/FABRK_Whitepaper_v1.0.pdf
  • Why sufficient / why not (one line): The whitepaper describes the protocol/consensus/economy, but not AI model versions.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: ERC‑20: 0x12683dc9eec95a5f742d40206e73319e6b9d8a91
  • Evidence: Tier‑1 — https://etherscan.io/token/0x12683dc9eec95a5f742d40206e73319e6b9d8a91
  • Why sufficient / why not (one line): The onchain fact of the token contract is 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 social graph/data and micropayment protocol; DPoV consensus; accounting/payouts in the token (per the description).
  • Evidence: Tier‑1 — https://www.fabrk.io/FABRK_Whitepaper_v1.0.pdf
  • Why sufficient / why not (one line): The whitepaper describes the protocol as a blockchain‑powered social platform, rather than just a token.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: an explicit “replacement test” was not found per Tier‑1.
  • Evidence: Tier‑1 — https://www.fabrk.io/FABRK_Whitepaper_v1.0.pdf
  • Why sufficient / why not (one line): OC_3=1 requires an explicit argument for onchain criticality (rather than “it is possible without it”).
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, FAB.
  • Evidence: Tier‑1 — https://www.fabrk.io/FABRK_Whitepaper_v1.0.pdf ; https://etherscan.io/token/0x12683dc9eec95a5f742d40206e73319e6b9d8a91
  • Why sufficient / why not (one line): The whitepaper describes the FAB token; the contract is observable in 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): The whitepaper describes a micropayment economy for content (“viewers pay / creators earn”).
  • Evidence: Tier‑1 — https://www.fabrk.io/FABRK_Whitepaper_v1.0.pdf
  • Why sufficient / why not (one line): This describes a pay‑flow as part of the protocol.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): Delegate Nodes can receive newly emitted FAB tokens; voting responsibility depends on staking and the contribution metric.
  • Evidence: Tier‑1 — https://www.fabrk.io/FABRK_Whitepaper_v1.0.pdf
  • Why sufficient / why not (one line): The whitepaper describes incentives and a staking component.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): Token‑governance mechanics are not established per Tier‑1 (there is staking/voting share, but without explicit “governance voting with the token”).
  • Evidence: Tier‑1 — https://www.fabrk.io/FABRK_Whitepaper_v1.0.pdf
  • Why sufficient / why not (one line): TK_3=1 requires an explicit governance process tied to 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 is not established per Tier‑1.
  • Evidence: Tier‑1 — https://www.fabrk.io/FABRK_Whitepaper_v1.0.pdf
  • Why sufficient / why not (one line): An explicit argument about replaceability/irreplaceability is required.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://www.fabrk.io/FABRK_Whitepaper_v1.0.pdf The purpose of the protocol, the FAB token, micropayments and node incentives; mention of AI/ML as an area of applicability (federated learning).
Tier‑1 https://www.fabrk.io/ Tier‑1 website: FABRK Foundation positioning and project context.
Tier‑1 https://etherscan.io/token/0x12683dc9eec95a5f742d40206e73319e6b9d8a91 Onchain fact of the FAB ERC‑20 token contract.

No comments to display

Back to top