Chirpley
Chirpley — 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).
Chirpley — an AI/Other project on Ethereum, token (symbol: CHRP).
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 and marketplace for campaigns with micro‑ and nano‑influencers (influencer marketing), with automated selection and evaluation.
- Who it’s for: brands/marketers and content creators (influencers).
- Why onchain/token: the token is used as the internal unit of settlement/payouts and as an element of staking/incentive mechanics (per the project’s description).
- What you can actually touch (Tier‑1): the platform is listed in the official materials as
https://app.chirpley.ai.
How it works (very briefly)
- The user does: a brand creates a campaign and sets the audience/task parameters.
- The system does: selects influencers and evaluates them (claimed: via AI/ML and data modeling) and automates part of the campaign processes.
- The user gets: a list/set of performers and the campaign results (within the platform’s functionality).
- Where the blockchain is: the onchain part in this card is confirmed at minimum by the existence of the token (ERC‑20) and its contract; the rest of the logic requires separate verification.
- Token role (if any): the ecosystem’s utility token for settlement/payouts and the claimed staking/incentive mechanics.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Chirpley |
| Also known as (aliases) | CHRP |
| Logo (logo) | — |
| Token symbol (ticker) | CHRP |
| Category | AI/Other | AdTech |
| 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 | 0x70Bc0DC6414EB8974BC70685F798838a87d8CCe4 |
| Token model (token_type) | utility (payments + staking + governance) |
| Max supply | — |
| Issuance | — |
| Tokenomics (tokenomics, brief) | payouts to influencers in CHRP; burn and staking rewards are claimed |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | AI matching + influencer evaluation |
| Use‑case (use_case) | influencer marketing automation |
| DecAI Fit — AI thesis fit | 5/6 — high alignment with the Decentralized AI thesis |
| DecAI Fit component summary | ai_score 3 / onchain_score 1 / token_score 2 / evidence_score 3 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://chirpley.ai |
| App / Demo | https://app.chirpley.ai |
| Docs | https://chirpley.gitbook.io |
| GitHub | https://github.com/chirpley |
| Releases / Changelog | https://twitter.com/chirpley |
| Whitepaper | https://chirpley.gitbook.io |
| Roadmap | — |
| Security advisories | https://github.com/chirpley/token/security |
| Explorer | https://etherscan.io/token/0x70Bc0DC6414EB8974BC70685F798838a87d8CCe4 |
| X | https://twitter.com/chirpley |
| Discord | https://discord.gg/chirpley |
| Telegram | https://t.me/chirpley |
| Medium | https://chirpley.medium.com/ |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/chirpley |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/chirpley/ |
General project overview
Chirpley describes itself as a platform for marketing campaigns with micro‑ and nano‑influencers. The official documentation claims automated matchmaking and “data driven influencer valuation”, as well as a separate AI engine that interacts with microservices and runs the algorithms.
Features/modules
- Campaigns and automation: launching and managing campaigns inside the platform.
- AI‑matching: selection of influencers for a campaign (claimed: AI/ML + analytics/data modeling).
- Influencer evaluation: data‑driven valuation based on the connected social networks (claimed).
- Payments/payouts (token economy): the mechanics of payouts in CHRP and the described burn/margin rules (claimed).
Typical scenarios
- Scenario 1: a brand sets the campaign parameters → the platform selects a set of influencers → the campaign is executed → the results are recorded.
- Scenario 2: an influencer connects social networks → receives tasks within campaigns → receives payouts per the platform’s rules.
- Scenario 3: a brand/team analyzes campaign effectiveness and adjusts the parameters of the next iteration (based on the platform’s data).
Getting started (wallet/network)
- What you need: an account/access to the platform, connection of social networks (per the scenario), and when working with the token — a compatible wallet.
- Network/chain: Ethereum (ERC‑20 token); the rest of the application infrastructure is described as a web platform.
- Fees: Ethereum network fees on onchain operations with the token; fees inside the platform require separate verification.
Architecture/tech (non‑AI)
- Components (claimed): web application + backend on microservices; a separate AI engine.
- Participant roles: brands/marketers, influencers, platform operators.
- Where logic runs: the selection/evaluation and campaign logic — offchain; onchain in this card is confirmed at minimum by the existence of the ERC‑20 token.
- Dependencies: social platforms (data/accounts), the web application infrastructure; for the token — the Ethereum network and access to it.
Token/economics (expanded, no forecasts)
- Token utility (Tier‑1, claimed): settlement/payouts in the ecosystem; staking with rewards; governance is described as “in the future” upon the transition to a DAO.
- Protocol necessity drivers: the mechanics of payouts to influencers are described as tied to CHRP (conversion in the backend and payouts).
- Who pays fees: users on onchain operations with the token (Ethereum).
- Where fees go: network fees — to Ethereum validators; additionally, a burn of part of the margin as part of the platform’s operation is described (requires separate verification of the implementation).
- Issuance/burn: Tier‑1 describes a burn mechanic; issuance/distribution parameters require separate verification.
- Incentive mechanisms: Tier‑1 describes staking and rewards.
- Distribution/vesting: mentioned in Tier‑1, but detailed tables/figures require separate verification.
- Treasury: not established per Tier‑1.
Governance
- Who makes decisions: not established; in Tier‑1, governance is tied to staking and described as part of “in the future” under a DAO model.
- How product parameters change: platform updates (offchain); the governance mechanism requires separate verification.
- Where decisions are discussed/made: not established per Tier‑1.
- Keys/multisig: not established per Tier‑1.
Security and incidents
- Audits: no confirmation of public audits was found per Tier‑1.
- Bug bounty: not found per Tier‑1.
- Incidents: the documentation mentions an incident with a bot attack on the system, but no details/postmortem were found per Tier‑1.
- Threat model (what to double‑check): centralization of the execution of AI/algorithms (offchain), the correctness of the claims about a “decentralized organization”, the implementation of burn/staking and the security of the contracts/integrations.
Project status and timeline
- Current status: documentation and the website are available; the status of the product/versions requires separate verification.
- Key releases/milestones: not established per Tier‑1.
- Roadmap: no explicit Tier‑1 roadmap page was found.
Ecosystem/integrations
AI component of the project
- What is real AI here? AI/ML are claimed as the basis of automated matchmaking and of part of the analytics/data modeling for influencer selection.
- What is truly onchain? per Tier‑1, the ERC‑20 token and its contract are confirmed; the rest of the “Web3 enabled” logic requires separate verification.
- Why is a token needed? Tier‑1 describes CHRP as a utility token for payouts/settlement, the burn mechanic and staking rewards; governance is mentioned as a future model.
- Red flags (what to double‑check): which parts of the product actually use the blockchain other than the token; how burn/staking are implemented; which AI algorithms are used and where they are executed; how the “decentralized organization” is confirmed in practice.
DecAI Fit component summary
- DecAI Fit: 5/6 — high alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | high | 3 |
| Onchain necessity | low | 1 |
| 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
- Claim (one line): the AI component is described as part of the product, so AI_0 is not used as “intent only”.
- Evidence: Tier‑1 — https://chirpley.gitbook.io/project
- Why sufficient / why not (one line): there is a description of the AI component and its role in the product.
- Conflict note: —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): AI/ML is used for automated matchmaking and influencer selection via analytics/data modeling.
- Evidence: Tier‑1 — https://chirpley.gitbook.io/project ; https://chirpley.ai
- Why sufficient / why not (one line): the Tier‑1 materials directly describe the purpose of the AI component (matchmaking/valuation).
- Conflict note: —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 1
- Claim (one line): the official documentation specifies the platform URL
https://app.chirpley.aias the entry point. - Evidence: Tier‑1 — https://chirpley.gitbook.io/project
- Why sufficient / why not (one line): the Tier‑1 documentation contains a direct link to the platform (App/Platform).
- Conflict note: —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —
- Context (version/date/how measured): —
- Evidence: Tier‑1 — https://chirpley.gitbook.io/project
- Why sufficient / why not (one line): Tier‑1 describes features and technologies, but there are no quantitative quality metrics/benchmarks.
- Conflict note: —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 1
- Claim (one line): Tier‑1 describes elements of the architecture (microservices, a separate AI engine, the development stack).
- Evidence: Tier‑1 — https://chirpley.gitbook.io/project
- Why sufficient / why not (one line): there is a tech description at the level of components/architecture and the role of the AI engine.
- Conflict note: —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum
- Addresses/identifiers: ERC‑20
0x70Bc0DC6414EB8974BC70685F798838a87d8CCe4 - Evidence: Tier‑1 — https://etherscan.io/token/0x70Bc0DC6414EB8974BC70685F798838a87d8CCe4
- Why sufficient / why not (one line): onchain fact: the token address and contract in the network explorer.
- Conflict note: —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 0
- What useful logic is onchain: no confirmation of onchain logic not reducible to the token was found per Tier‑1.
- Evidence: Tier‑1 — https://chirpley.gitbook.io/project
- Why sufficient / why not (one line): Tier‑1 has general wording about “Web 3.0 enabled”, but without specific addresses/contracts for the product logic.
- Conflict note: —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: no Tier‑1 justification of onchain criticality for the platform’s key properties was found.
- Evidence: Tier‑1 — https://chirpley.gitbook.io/project
- Why sufficient / why not (one line): there is no explicit “without the blockchain the product breaks down” test.
- Conflict note: —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): the project has a token, $CHRP (ERC‑20).
- Evidence: Tier‑1 — https://chirpley.gitbook.io/project/token
- Why sufficient / why not (one line): the Tier‑1 documentation describes $CHRP as the ecosystem’s utility token.
- Conflict note: —
TK_1..TK_4 (1/0)
TK_1 — payment for the service (1/0)
- TK_1 (decision): 1
- Claim (one line): payouts in the ecosystem are described as carried out in CHRP (conversion in the backend and payouts to influencers).
- Evidence: Tier‑1 — https://chirpley.gitbook.io/project/token
- Why sufficient / why not (one line): Tier‑1 describes the conversion into CHRP and payouts to influencers.
- Conflict note: —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 1
- Claim (one line): staking of CHRP with rewards and lock periods is described.
- Evidence: Tier‑1 — https://chirpley.gitbook.io/project/token
- Why sufficient / why not (one line): Tier‑1 describes staking and rewards.
- Conflict note: —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): governance is mentioned as a future scenario upon the transition to a DAO; as a working onchain mechanic it is not confirmed by Tier‑1 sources.
- Evidence: Tier‑1 — https://chirpley.gitbook.io/project/token
- Why sufficient / why not (one line): the existence of an “in the future” mention is not enough to consider governance implemented.
- Conflict note: —
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://chirpley.gitbook.io/project/token
- Why sufficient / why not (one line): without protocol specifications, “replaceable/irreplaceable” cannot be strictly substantiated.
- Conflict note: —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://chirpley.gitbook.io/project | Tier‑1 description of the product, AI matchmaking and elements of the architecture (including a separate AI engine) |
| Tier‑1 | https://chirpley.ai | Tier‑1 mentions of AI/ML and A.I. matching on the official website |
| Tier‑1 | https://chirpley.gitbook.io/project/token | Tier‑1 description of the token’s utility (payouts/conversion, burn mechanic, staking) |
| Tier‑1 | https://etherscan.io/token/0x70Bc0DC6414EB8974BC70685F798838a87d8CCe4 | onchain fact: the CHRP token contract on Ethereum |
| Tier‑1 | https://app.chirpley.ai | link to the platform/entry point (demo) |
| Tier‑2 | https://www.coingecko.com/en/coins/chirpley | reference token card (aggregator; not proof of technology) |
| Tier‑2 | https://coinmarketcap.com/currencies/chirpley/ | reference token card (aggregator; not proof of technology) |
No comments to display
No comments to display