SLOP

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

SLOP — a meme token on the Solana network. The onchain fact of the token is confirmed per Solscan; no Tier‑1 sources confirming AI functionality/a product were found.

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 meme token (Solana).
Who it’s for: members of the meme community/traders (in general terms).
Why onchain/token: the token exists onchain; no protocol utility requiring the token was found in Tier‑1.

How it works (very briefly)

The user does: performs operations with the SLOP token.
The system does: records the operations on the Solana network.
The user gets: ownership/transfer of the token.
Where the blockchain is: Solana (the token in the explorer).
Token role (if any): the asset itself; utility roles are not confirmed by Tier‑1.

Quick links: AI thesis fit

Project passport

Field	Value
Project name	SLOP
Also known as (aliases)	slop_bot
Logo (logo)	—
Token symbol (ticker)	SLOP
Category	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	FqvtZ2UFR9we82Ni4LeacC1zyTiQ77usDo31DUokpump
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)	—
Use‑case (use_case)	meme token
DecAI Fit — AI thesis fit	0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary	0 / 1 / 0 / 2
Last verified	2026-02-11

Links (links_*)

Type	Link
Website	https://pump.fun/FqvtZ2UFR9we82Ni4LeacC1zyTiQ77usDo31DUokpump
Docs	—
GitHub	—
Releases / Changelog	—
Whitepaper	—
Roadmap	—
Security advisories	—
Explorer	https://solscan.io/token/FqvtZ2UFR9we82Ni4LeacC1zyTiQ77usDo31DUokpump
X	https://twitter.com/slop_bot
Discord	—
Telegram	https://t.me/SLOPchannel
Medium	—
Audit report(s)	—
Bug bounty	—
CoinGecko (profile, reference)	https://www.coingecko.com/en/coins/slop
CoinMarketCap (profile, reference)	https://coinmarketcap.com/currencies/slop/

General project overview

SLOP is a meme token on the Solana network. The onchain artifact (mint) and basic links (explorer, social media) are confirmed. No Tier‑1 materials describing a product/protocol/AI part or “why the token is needed for a service” were found.

Features/modules

SPL token (mint) on Solana.
Trading/transfers of the token in the Solana ecosystem (as a consequence of the token’s existence).

Typical scenarios

Scenario 1: a user performs operations with SLOP on a DEX/via Solana tools → receives the token into a wallet.
Scenario 2: a user transfers SLOP to another address → transfers ownership of the token.

Getting started (wallet/network)

What you need: a Solana wallet and some SOL for fees.
Network/chain: Solana (mainnet).
Fees: Solana network fees for purchases/sales/transfers.

Architecture/tech (non‑AI)

Components: the SPL token mint + standard Solana tools (wallets/DEXs/indexers/explorers).
Participant roles: token holders, traders, liquidity providers (in general terms).
Where logic runs: onchain — operations with the SPL token; no separate protocol logic (other than the token) has been identified.
Dependencies: Solana infrastructure (RPC/validators), liquidity services (DEX) — without details in Tier‑1.

Token/economics (expanded, no forecasts)

Token utility: no Tier‑1 source describing the token’s utility (payment for a service/incentives/governance) was found.
Protocol necessity drivers: not established (a pure meme asset is possible).
Who pays fees: users for onchain operations (SOL gas).
Where fees go: to Solana validators/infrastructure (as part of network fees).
Issuance/burn / distribution: not established per Tier‑1 sources.

Governance

Who makes decisions: not established (no Tier‑1 data).
How protocol parameters change: not applicable/not established (at least, beyond the SPL token).

Security and incidents

Audits: — (no Tier‑1 confirmation found).
Bug bounty: — (no Tier‑1 confirmation found).
Incidents: — (no Tier‑1 confirmation found).
Threat model: risks of a meme token (concentration of ownership, liquidity, absence of utility) — requires separate verification based on onchain data.

Project status and timeline

Current status: active (the token exists onchain).
Roadmap: — (no Tier‑1 found).

Ecosystem/integrations

Integrations: standard tools of the Solana ecosystem (wallets/DEXs/explorers).
Partners: — (no Tier‑1 found).
Where it’s actually used: trading/transfers of the token; no other use‑cases established.

AI component of the project

What is real AI here? not established (there are no Tier‑1 sources about an AI component/feature).
What is truly onchain? The SPL token on the Solana network.
Why is a token needed? not established (Tier‑1 utility/incentives/governance are not confirmed).
Red flags (based on the information found): token‑washing — if there are attempts to present a meme asset as an infrastructure token; AI‑washing — if AI is claimed without Tier‑1 artifacts; what to double‑check — the existence of a real product/docs/repo.

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	0
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 declaration of AI intent was found.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): without a Tier‑1 roadmap/official update we do not set AI_0.
Conflict note (if any): —

AI_1 — what the AI does (1/0)

AI_1 (decision): 0
Claim (one line): An AI feature/component is not established per Tier‑1.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): there is no Tier‑1 description of “what exactly the AI does”.
Conflict note (if any): —

AI_2 — demos/examples (1/0)

AI_2 (decision): 0
Claim (one line): no Tier‑1 demo/guide of the AI part was found.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): there is no Tier‑1 “what you can touch” artifact about AI.
Conflict note (if any): —

AI_3 — metrics/quality (1/0)

AI_3 (decision): 0
Metrics: —
Context (version/date/how measured): —
Evidence: Tier‑1 — —
Why sufficient / why not (one line): AI metrics/benchmarks are absent in Tier‑1 sources.
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 part is absent in Tier‑1 sources.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): there is no Tier‑1 document with the architecture/model versions.
Conflict note (if any): —

Onchain necessity

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

OC_1 (decision): 1
Chain: Solana
Addresses/identifiers: token mint: FqvtZ2UFR9we82Ni4LeacC1zyTiQ77usDo31DUokpump
Evidence: Tier‑1 — https://solscan.io/token/FqvtZ2UFR9we82Ni4LeacC1zyTiQ77usDo31DUokpump
Why sufficient / why not (one line): the onchain fact of the token and the network is verifiable via the explorer.
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) per Tier‑1 sources.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): there is no Tier‑1 description of protocol onchain logic other than the SPL token.
Conflict note (if any): —

OC_3 — onchain is critical (1/0)

OC_3 (decision): 0
“Replace the blockchain” test: not applicable/not proven (no protocol other than the token has been identified).
Evidence: Tier‑1 — —
Why sufficient / why not (one line): there is no Tier‑1 argument for the criticality of onchain logic (other than the existence of the token).
Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

TK_0 (decision): 0
Claim (one line): the project has a token, SLOP.
Evidence: Tier‑1 — https://solscan.io/token/FqvtZ2UFR9we82Ni4LeacC1zyTiQ77usDo31DUokpump
Why sufficient / why not (one line): the token is confirmed by the explorer.
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): payment for a service with the token is not established per Tier‑1.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): there is no Tier‑1 document/product docs with a payment utility.
Conflict note (if any): —

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

TK_2 (decision): 0
Claim (one line): incentive/staking mechanics are not established per Tier‑1.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): there is no Tier‑1 description of incentives/collateral/penalties.
Conflict note (if any): —

TK_3 — governance (1/0)

TK_3 (decision): 0
Claim (one line): the governance role of the token is not established per Tier‑1.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): there is no Tier‑1 description of voting/a DAO.
Conflict note (if any): —

TK_4 — token is replaceable (1/0)

TK_4 (decision): 0
Claim (one line): no conclusion about the replaceability of the token has been drawn.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): there is no Tier‑1 wording/comparison “with the token/without the token”.
Conflict note (if any): —

Evidence (table)

Tier	Source	What it proves
Tier‑1	https://solscan.io/token/FqvtZ2UFR9we82Ni4LeacC1zyTiQ77usDo31DUokpump	onchain fact of the SLOP token (Solana)
Tier‑1	—	No Tier‑1 source for claim “the project has an AI component / a product with an AI feature” was found.