Dolos (Dolos the Bully)

Dolos (Dolos the Bully) — 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).

Dolos — an AI/Agents project (an LLM persona/agent for X and Telegram), token on Solana.

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 AI agent/chat persona, described as an LLM based on Llama 3.1, with integrations for posting/replying on X and chatting on Telegram (per the documentation).
Who it’s for: users/communities on X and Telegram who need an “AI persona/bot” for communication and content.
Why onchain/token: per Tier‑1 sources, no description of a specific token utility in the product was found (other than the fact that the token exists on the network).
What you can actually touch (Tier‑1): the Telegram integration is officially described; the link to the portal/chat is in links_*.

How it works (very briefly)

The user does: writes in a Telegram chat/group or interacts with the account on X.
The system does: generates a reply/post on behalf of “Dolos” (per the description in the documentation).
The user gets: a text reply/content and interaction with the AI persona.
Where the blockchain is: in this card we record an SPL token on the Solana network (an onchain artifact).
Token role: not established per Tier‑1 sources.

Quick links: AI thesis fit

Project passport

Field	Value
Project name	Dolos (Dolos the Bully)
Also known as (aliases)	Dolos
Logo (logo)	—
Token symbol (ticker)	—
Category	AI/Agents \| Meme
Primary chain (chain)	Solana
Type	non-EVM
Network status	mainnet
Consensus (consensus)	PoS (Solana)
Launch date (launch_date)	—
Project status (status)	active
Token (standard)	SPL
Token contract	79yTpy8uwmAkrdgZdq6ZSBTvxKsgPrNqTLvYQBh1pump
Token model (token_type)	—
Max supply	—
Issuance	—
Tokenomics (tokenomics, brief)	—
Governance	—
Admins/keys	—
Audit	—
Bug bounty	—
Team (team)	—
Funding (investors/funding)	—
AI component (ai_component)	LLM persona for X + Telegram
Use‑case (use_case)	chat + content agent
DecAI Fit — AI thesis fit	3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary	ai_score 3 / onchain_score 1 / token_score 0 / evidence_score 2
Last verified	2026-02-11

Links (links_*)

Type	Link
Website	https://www.dolosdiary.com/
Docs	https://docs.dolosdiary.com/dolos/roadmap-and-vision
GitHub	—
Releases / Changelog	—
Whitepaper	—
Roadmap	https://docs.dolosdiary.com/dolos/roadmap-and-vision
Security advisories	—
Explorer	https://solscan.io/token/79yTpy8uwmAkrdgZdq6ZSBTvxKsgPrNqTLvYQBh1pump
App / Demo	https://t.me/dolosTheBully_portal
X	https://twitter.com/dolos_diary
Discord	—
Telegram	https://t.me/dolosTheBully_portal
Medium	—
Audit report(s)	—
Bug bounty	—
CoinGecko (profile, reference)	https://www.coingecko.com/en/coins/dolos-the-bully
CoinMarketCap (profile, reference)	https://coinmarketcap.com/currencies/dolos-the-bully/

General project overview

In the documentation, Dolos is described as an AI language model/persona fine‑tuned for a particular communication style, with integrations for X (auto‑posting/replies) and Telegram (participation in chats/groups). In this card we additionally record the existence of an SPL token on the Solana network, but the specific function of the token in the product is not confirmed by Tier‑1 sources.

Features/modules

LLM agent (per the documentation): the base model (Llama 3.1) and the approach to fine‑tuning/deployment are described.
Integrations (per the documentation): X (auto‑posting/replies), Telegram (chat interaction).

Typical scenarios

Scenario 1: a user writes in a Telegram chat/group → receives a reply from Dolos.
Scenario 2: a user reads/comments on posts on X → sees replies/posts on behalf of Dolos.

Getting started (wallet/network)

What you need: Telegram (portal/chat) and/or X.
Network/chain: Solana — only for the onchain token (per the explorer).
Fees: Solana fees arise only for operations with the token.

Architecture/tech (non‑AI)

Components: an offchain AI service/integrations with X and Telegram; onchain — the SPL token.
Where logic runs: interaction with the agent — offchain; the token — onchain (Solana).

Token/economics (expanded, no forecasts)

Token utility: not established per Tier‑1 sources.
Onchain fact: the SPL token is recorded per the Solana explorer.

Governance

Governance: —.

Security and incidents

Audits: —.
Bug bounty: —.
Incidents: —.

Project status and timeline

Current status: active (per the documentation updates).
Roadmap: the link is in links_*.

Ecosystem/integrations

Integrations: X and Telegram (per the documentation).

AI component of the project

What is real AI here? An LLM agent (persona) based on Llama 3.1 with fine‑tuning and deployment/integration mechanisms is described.
What is truly onchain? Only the fact of the SPL token on Solana (per the explorer); no useful protocol‑level onchain logic other than the token has been identified.
Why is a token needed? No Tier‑1 description of the necessity of the token was found.
Red flags (based on the information found): token‑washing — the token exists, but its role in the product is not confirmed by Tier‑1; what to double‑check — the official documentation/“token utility” page (if any) and the onchain mechanics related to access/payments/incentives.

DecAI Fit component summary

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

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

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 an already existing LLM agent, not only as “plans/intent”.
Evidence: Tier‑1 — https://docs.dolosdiary.com/dolos/advanced-ai-agent
Why sufficient / why not (one line): AI_0 is set when there are only intentions without a working component; here a working agent and its training are described.
Conflict note (if any): —

AI_1 — what the AI does (1/0)

AI_1 (decision): 1
Claim (one line): Dolos is an LLM agent/persona for generating posts/replies (X) and chatting on Telegram.
Evidence: Tier‑1 — https://docs.dolosdiary.com/dolos/advanced-ai-agent ; https://docs.dolosdiary.com/dolos/roadmap-and-vision
Why sufficient / why not (one line): Tier‑1 sources directly describe the integrations and the purpose of the agent.
Conflict note (if any): —

AI_2 — demos/examples (1/0)

AI_2 (decision): 1
Claim (one line): Real interaction channels are described (Telegram/X); the Telegram portal lets you “touch” the agent.
Evidence: Tier‑1 — https://docs.dolosdiary.com/dolos/advanced-ai-agent ; https://t.me/dolosTheBully_portal
Why sufficient / why not (one line): The existence of a public interaction channel and a described integration is sufficient as a demo/example.
Conflict note (if any): —

AI_3 — metrics/quality (1/0)

AI_3 (decision): 0
Metrics: —
Context (version/date/how measured): —
Evidence: Tier‑1 — https://docs.dolosdiary.com/dolos/advanced-ai-agent
Why sufficient / why not (one line): Per Tier‑1 sources, no reproducible set of quality metrics (benchmarks/model quality evaluation) was found.
Conflict note (if any): —

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

AI_4 (decision): 1
Claim (one line): The documentation describes the base model, the training data/methodology and the details of deployment/integrations.
Evidence: Tier‑1 — https://docs.dolosdiary.com/dolos/advanced-ai-agent
Why sufficient / why not (one line): There is technical information about the base (Llama 3.1) and the fine‑tuning/deployment process.
Conflict note (if any): —

Onchain necessity

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

OC_1 (decision): 1
Chain: Solana
Addresses/identifiers: SPL mint: 79yTpy8uwmAkrdgZdq6ZSBTvxKsgPrNqTLvYQBh1pump
Evidence: Tier‑1 — https://solscan.io/token/79yTpy8uwmAkrdgZdq6ZSBTvxKsgPrNqTLvYQBh1pump
Why sufficient / why not (one line): There is a verifiable onchain artifact in the explorer.
Conflict note (if any): —

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

OC_2 (decision): 0
What useful logic is onchain: per Tier‑1 sources, no description of onchain logic other than the issuance/accounting of the token was found.
Evidence: Tier‑1 — https://docs.dolosdiary.com/
Why sufficient / why not (one line): The official materials describe the AI agent and integrations, not the smart‑contract logic of the product.
Conflict note (if any): —

OC_3 — onchain is critical (1/0)

OC_3 (decision): 0
“Replace the blockchain” test: the core function (an AI agent on X/Telegram) looks like an offchain service; the criticality of onchain is not substantiated.
Evidence: Tier‑1 — https://docs.dolosdiary.com/dolos/advanced-ai-agent
Why sufficient / why not (one line): OC_3 requires a strict justification of “why a key property breaks down without the blockchain”; it was not found.
Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

TK_0 (decision): 0
Claim (one line): The project has a token (an SPL mint on Solana).
Evidence: Tier‑1 — https://solscan.io/token/79yTpy8uwmAkrdgZdq6ZSBTvxKsgPrNqTLvYQBh1pump
Why sufficient / why not (one line): The existence of the token is verifiable onchain.
Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

TK_1 (decision): 0
Claim (one line): Per Tier‑1 sources, no description of paying for services with the token was found.
Evidence: Tier‑1 — https://docs.dolosdiary.com/
Why sufficient / why not (one line): The documentation describes the agent and integrations, but does not record a payment role of the token.
Conflict note (if any): —

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

TK_2 (decision): 0
Claim (one line): Per Tier‑1 sources, no description of token‑based incentives/collateral/penalties was found.
Evidence: Tier‑1 — https://docs.dolosdiary.com/
Why sufficient / why not (one line): There is no description of a protocol‑level necessity of the token for incentives/security.
Conflict note (if any): —

TK_3 — governance (1/0)

TK_3 (decision): 0
Claim (one line): Per Tier‑1 sources, no description of governance mechanics with the token was found.
Evidence: Tier‑1 — https://docs.dolosdiary.com/dolos/roadmap-and-vision
Why sufficient / why not (one line): The roadmap describes the development of the agent and integrations, but not the governance mechanics of the token.
Conflict note (if any): —

TK_4 — token is replaceable (1/0)

TK_4 (decision): 0
Claim (one line): Per Tier‑1 sources, there are no grounds to conclude the replaceability/irreplaceability of the token.
Evidence: Tier‑1 — https://docs.dolosdiary.com/
Why sufficient / why not (one line): TK_4 requires an analysis of the token’s real protocol functions; they are not established.
Conflict note (if any): —

Evidence (table)

Tier	Source	What it proves
Tier‑1	https://docs.dolosdiary.com/dolos/advanced-ai-agent	Description of the LLM agent (Llama 3.1 base), the training approach and the integrations (X/Telegram).
Tier‑1	https://docs.dolosdiary.com/dolos/roadmap-and-vision	Positioning and plans for developing the AI agent and integrations.
Tier‑1	https://solscan.io/token/79yTpy8uwmAkrdgZdq6ZSBTvxKsgPrNqTLvYQBh1pump	Onchain artifact: the SPL token on Solana (mint).
Tier‑1	—	No Tier‑1 source for claim “why the token is needed in the product (payment/access/incentives/governance)” was found.
Tier‑2	https://www.coingecko.com/en/coins/dolos-the-bully	Reference metadata and links (context).
Tier‑2	https://coinmarketcap.com/currencies/dolos-the-bully/	Reference metadata and links (context).