PIBBLE

PIBBLE (PIB) — 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).

PIBBLE — an AI/Content project that positions PIBBLE 2.0 as an AI‑based platform for copyright management and monetization of digital content (including AI‑generated) using blockchain/NFT to account for ownership and licenses; the PIB token (ERC‑20, Ethereum) is the ecosystem’s utility token.

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 for authors/rights holders: accounting of rights to content, licensing and monetization (as the goal of PIBBLE 2.0).
• Who it’s for: content creators, rights holders and companies/license buyers.
• Why onchain/token: onchain accounting of the token and (by design) NFT recording of ownership/licenses; the role of the PIB token in mandatory scenarios is described in general terms.

How it works (very briefly)

1. The author/rights holder does: publishes content and records the rights/terms of use.
2. The system does: keeps records of rights and (per the PIBBLE 2.0 description) automates licensing and royalty flows.
3. The user gets: transparent accounting of ownership/licenses and a mechanism for monetization/resale of rights.
4. Where the blockchain is: the PIB token is an ERC‑20 on Ethereum; the model of recording rights via NFT is described in the whitepaper as an architectural approach.
5. Token role: the ecosystem’s utility token; specific tariffs/the payment layer are not specified in the open sources.

Quick links: AI thesis fit

Project passport

Field	Value
Project name	PIBBLE
Also known as (aliases)	PIB, PIBBLE 2.0, AI PIBBLE
Logo (logo)	../assets/221_pibble_logo.png
Token symbol (ticker)	PIB
Category	AI/Content
Primary chain (chain)	Ethereum
Type	EVM
Network status	mainnet
Consensus (consensus)	PoS (Ethereum)
Launch date (launch_date)	2018 (contract verification on Etherscan: 2018‑03‑23)
Project status (status)	active
Token (standard)	ERC-20
Token contract	0x1864ce27e9f7517047933caae530674e8c70b8a7
Token model (token_type)	utility (governance)
Max supply	~7.23B PIB (Etherscan Max Total Supply); INITIAL_SUPPLY=10B (contract code)
Issuance	unknown (the contract contains mint/burn; the policy depends on owner/minting)
Tokenomics (tokenomics, brief)	ecosystem token; the necessity of the token for licensing/marketplace is not confirmed by parameters
Governance	company (PIBBLE PTE. LTD. is listed on the website)
Admins/keys	—
Audit	—
Bug bounty	—
Team (team)	—
Funding (investors/funding)	—
AI component (ai_component)	AI content hub, chatbots, copyright tools
Use‑case (use_case)	licensing + monetization of digital content
DecAI Fit — AI thesis fit	3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary	2 / 1 / 0 / 3
Last verified	2026-02-11

Links (links_*)

Type	Link
Website	https://pibble.io
Docs	https://pibble.gitbook.io/pibble-whitepaper
GitHub	https://github.com/Pibble-io/TGE
Releases / Changelog	https://pibbleapp.io/notice
Whitepaper	https://pibble.gitbook.io/pibble-whitepaper
Roadmap	https://pibble.gitbook.io/pibble-whitepaper/roadmap/
Security advisories	https://github.com/Pibble-io/TGE/security
Explorer	https://etherscan.io/token/0x1864ce27e9f7517047933caae530674e8c70b8a7
X	https://twitter.com/pibbleio
Discord	—
Telegram	https://t.me/pibbleglobal
Medium	https://medium.com/@pibbleio
Audit report(s)	—
Bug bounty	—
CoinGecko (profile, reference)	https://www.coingecko.com/en/coins/pibble
CoinMarketCap (profile, reference)	https://coinmarketcap.com/currencies/pibble/

General project overview

PIBBLE describes the transition from PIBBLE 1.0 (an image‑centric blockchain social platform) to PIBBLE 2.0 as an “AI‑based copyright revenue generation platform”. The GitBook whitepaper focuses on the problem of piracy and rights management for digital content (including AI‑generated) and on building a system of transparent accounting of ownership/licenses and payouts to rights holders.

The website lists AI directions (generative content, “150 AI bots”, analytics/insights) and a set of blockchain components (bridge/DEX/staking/payments), but some items are marked as “in progress / in development”, so this should be treated as roadmap claims.

Features/modules

• PIBBLE 2.0: copyright management: recording/management of rights and monetization/licensing (whitepaper).
• AI‑oriented architecture: NLP/an interactive interface (ChatGPT) and AI services around content (whitepaper + website).
• NFT approach to ownership: the idea of recording content ownership/transactions via NFT (whitepaper).

Typical scenarios

• Scenario 1 (rights registration): an author records ownership/terms → gets transparent accounting and a basis for licensing.
• Scenario 2 (licensing): a rights holder sets the terms → a consumer gets a license → the project declares tracking/royalty flows.
• Scenario 3 (AI content): a user creates/modifies content with AI → accounts for primary and secondary rights (as the goal of PIBBLE 2.0).

Getting started (wallet/network)

• What you need: access to PIBBLE products/services (website/app); for onchain operations — an EVM wallet.
• Network/chain: Ethereum (PIB token).
• Fees: Ethereum fees for onchain transactions.

Architecture/tech (non‑AI)

• Components: web/app layer; AI tools/interfaces (offchain); the PIB token (ERC‑20, Ethereum); the claimed NFT model of rights (whitepaper).
• Participant roles: authors/rights holders; license buyers; the platform operator (company).
• Where logic runs: AI and the user UX — offchain; the token and potential content NFT/licenses — onchain (by design).
• Dependencies: Ethereum RPC; external AI models/infrastructure (not disclosed).

Token/economics (expanded, no forecasts)

• Token utility: the PIB ecosystem token (mentioned on the website and in the whitepaper as part of the economy).
• Protocol necessity drivers: there are no verifiable conditions of the kind “without PIB the service does not work” in the open materials; the necessity remains partly at the level of claims.
• Who pays fees: Ethereum users for transactions with the ERC‑20.
• Where fees go: —.
• Issuance/burn: the verifiable supply figures conflict between sources (see the passport); the contract contains mint/burn.
• Security/incentive mechanisms: — (staking/incentives parameters are not confirmed).
• Distribution and token issuance schedule: —.
• Treasury: —.

Governance

• Who makes decisions: the company/project team.
• How protocol parameters change: —.
• Where decisions are discussed/made: public channels (X/Telegram/Medium) and notice pages.
• Keys/multisig: —.

Security and incidents

• Audits: — (Etherscan shows “No Contract Security Audit Submitted”).
• Bug bounty: —.
• Incidents: —.
• Threat model: some functions remain in the “in progress” status; the risks of onchain contracts and token policy (mint/burn) also remain, as well as legal risks around copyright and AI content.

Project status and timeline

• Current status: active; PIBBLE 2.0 is described as a platform update.
• Key releases/milestones: the whitepaper states that PIBBLE 2.0 was “renewed in 2023”.
• Roadmap: the GitBook roadmap section (see links_*).

Ecosystem/integrations

• Integrations: Ethereum (PIB token); ecosystem products/services on the website (AI PIBBLE, etc.).
• Partners: —.
• Where it’s actually used: as a content platform/ecosystem per the claims; without public KPIs.

AI component of the project

• What is real AI here? Tier‑1 sources describe AI functions around content (a generative AI engine, “150 AI bots”, an NLP/ChatGPT interface) and an AI‑oriented model of copyright services; quality metrics/demos of individual models were not found.
• What is truly onchain? The PIB ERC‑20 token on Ethereum; the onchain model of NFT ownership/licenses is described in the whitepaper, but addresses/contracts (other than the token) are not provided.
• Why is a token needed? It is mentioned as the ecosystem token, but its necessity in “must‑have” scenarios is not proven by parameters/tariffs.
• Red flags (based on the information found): AI‑washing (many general promises), token‑washing (the mandatory nature of PIB is unclear), a conflict of supply figures between sources.

DecAI Fit component summary

• DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis

Component	Level	Score
AI reality	medium	2
Onchain necessity	low‑medium	1
Token necessity	low‑medium	0
Evidence	Tier‑1 present	3

Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

• AI_0 (decision): 0
• Claim (one line): There are signs of AI reality per Tier‑1 (see AI_1..AI_4), so the AI_0 flag (intent‑only) does not apply.
• Evidence: Tier‑1 — see Evidence/links in AI_1..AI_4.
• Why sufficient / why not (one line): AI_0=1 is admissible only when AI_1..AI_4=0; here ai_score without AI_0 = 2.
• Conflict note (if any): none.

AI_1 — what the AI does (1/0)

• AI_1 (decision): 1
• Claim (one line): generation of multimodal content and a set of AI bots, as well as an NLP interface (ChatGPT), are claimed.
• Evidence: Tier‑1 — https://pibble.io/technology ; https://pibble.gitbook.io/pibble-whitepaper/pibble-2.0/ai-pibble-business-architecture
• Why sufficient / why not (one line): there is a Tier‑1 description of the functions, but without verifiable details of models/metrics.
• Conflict note (if any): some of the functionality is marked as “in progress / in development”.

AI_2 — demos/examples (1/0)

• AI_2 (decision): 0
• Claim (one line): no Tier‑1 demo artifact that allows verifying a specific AI module/output was found.
• Evidence: Tier‑1 — https://pibble.io/ ; https://pibble.io/technology
• Why sufficient / why not (one line): product pages are available, but without verifiable AI demos/a repository.
• Conflict note (if any): none.

AI_3 — metrics/quality (1/0)

• AI_3 (decision): 0
• Metrics: —.
• Context (version/date/how measured): —.
• Evidence: Tier‑1 — https://pibble.io/technology
• Why sufficient / why not (one line): no public quality metrics for the AI modules were found.
• Conflict note (if any): none.

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

• AI_4 (decision): 1
• Claim (one line): the whitepaper describes the AI‑oriented business architecture of PIBBLE 2.0 (copyright, marketplace, co‑creation) and mentions a ChatGPT interface.
• Evidence: Tier‑1 — https://pibble.gitbook.io/pibble-whitepaper/pibble-2.0/ai-pibble-business-architecture
• Why sufficient / why not (one line): sufficient for a high‑level understanding, but not for verification of the models.
• Conflict note (if any): none.

Onchain necessity

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

• OC_1 (decision): 1
• Chain: Ethereum mainnet
• Addresses/identifiers: ERC‑20 PIB: 0x1864ce27e9f7517047933caae530674e8c70b8a7
• Evidence: Tier‑1 — https://etherscan.io/token/0x1864ce27e9f7517047933caae530674e8c70b8a7
• Why sufficient / why not (one line): Etherscan confirms the contract and decimals=18.
• Conflict note (if any): none.

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

• OC_2 (decision): 0
• What useful logic is onchain: separate addresses/contracts of the NFT registry/licensing (other than the PIB token) are not confirmed by Tier‑1 sources; the verifiable onchain artifact is the PIB token.
• Evidence: Tier‑1 — https://pibble.gitbook.io/pibble-whitepaper
• Why sufficient / why not (one line): the whitepaper describes the NFT approach, but does not provide an onchain SSOT (addresses).
• Conflict note (if any): none.

OC_3 — onchain is critical (1/0)

• OC_3 (decision): 0
• “Replace the blockchain” test: accounting of rights/licenses can be implemented in a centralized way; onchain adds transparency, but criticality is not proven.
• Evidence: Tier‑1 — https://pibble.gitbook.io/pibble-whitepaper
• Why sufficient / why not (one line): verification of the necessity of onchain for the core functions is absent.
• Conflict note (if any): none.

Token necessity

TK_0 — no token (1/0)

• TK_0 (decision): 0
• Claim (one line): the project has a token, PIB (ERC‑20, Ethereum).
• Evidence: Tier‑1 — https://etherscan.io/token/0x1864ce27e9f7517047933caae530674e8c70b8a7
• Why sufficient / why not (one line): the token contract is confirmed by the explorer.
• Conflict note (if any): none.

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

• TK_1 (decision): 0
• Claim (one line): there is no verifiable tariff/mechanics of the kind “pay PIB for X” in the open Tier‑1 sources.
• Evidence: Tier‑1 — https://pibble.io/technology ; https://pibble.gitbook.io/pibble-whitepaper
• Why sufficient / why not (one line): the descriptions do not record a working payment layer in the token.
• Conflict note (if any): none.

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

• TK_2 (decision): 0
• Claim (one line): staking/DEX/bridge are mentioned, but the parameters of incentives/collateral/penalties are not described as a verifiable mechanism.
• Evidence: Tier‑1 — https://pibble.io/technology
• Why sufficient / why not (one line): there are no parameters/contracts/rules for incentives.
• Conflict note (if any): none.

TK_3 — governance (1/0)

• TK_3 (decision): 0
• Claim (one line): the governance role of the token is not confirmed in the open Tier‑1 sources.
• Evidence: Tier‑1 — https://pibble.io/ ; https://pibble.gitbook.io/pibble-whitepaper
• Why sufficient / why not (one line): there is no description of a DAO/voting with the token.
• Conflict note (if any): none.

TK_4 — token is replaceable (1/0)

• TK_4 (decision): 1
• Claim (one line): in the absence of a proven mandatory utility, the token looks partially replaceable (stablecoin/fiat/subscription).
• Evidence: Tier‑1 — https://pibble.io/technology
• Why sufficient / why not (one line): there is no confirmation that the product does not work without the PIB token.
• Conflict note (if any): none.

Evidence (table)

Tier	Source	What it proves
Tier‑1	https://pibble.gitbook.io/pibble-whitepaper	The goal of PIBBLE 2.0: AI‑based copyright revenue generation platform; a mention of “renewed in 2023”.
Tier‑1	https://pibble.gitbook.io/pibble-whitepaper/pibble-2.0/ai-pibble-business-architecture	Architectural blocks of PIBBLE 2.0 (copyright/NFT/marketplace/co‑creation) and a mention of a ChatGPT interface.
Tier‑1	https://pibble.io/	Positioning “Where AI & Blockchain”, description of the AI PIBBLE services and the ecosystem.
Tier‑1	https://pibble.io/technology	List of the claimed AI modules and blockchain components (some “in progress / in development”).
Tier‑1	https://etherscan.io/token/0x1864ce27e9f7517047933caae530674e8c70b8a7	The ERC‑20 contract of the PIB token, decimals=18; absence of a submitted audit on the page.
Tier‑2	https://coinmarketcap.com/currencies/pibble/	Aggregator: reference profile and navigation links.
Tier‑1	—	No Tier‑1 addresses/contracts of content NFT/licensing (other than the PIB token) were found.