Cross-category conflict: Safety scored 2.0/10 while Technical scored 5.0/10. This 3.0-point gap suggests the token's strengths in Technical may not translate to Safety reliability.
UNSETTLED
16/100
GRADE F
Shiba Inu Treat (TREAT) is a well-established base token with $377K market cap, 1+ years old. Key concerns: security risks, tokenomics concerns. Overall verdict: F — critical risk — not recommended.
LAYER 1
Trade reality
CAN IT GET OUT AT YOUR SIZE?
SOLANA EXIT SIMULATION
Solana exit simulation is returned only when a caller supplied trade intent. It is not available for other chains.
No Solana exit simulation was requested.
This report has no caller-supplied trade intent, so no route-specific sell test was returned.
LIQUIDITY EXPOSURE CAP
- Measured cap
- $280.17
HARD BLOCKERS
No blocker data returned.
Not returned for this report.
HOLDER CLUSTERS
- Funding bundle detected
- NO
LAYER 2
Where the score went
WEIGHTED SUBSCORES
Score breakdown unavailable.
Not returned for this report.
LAYER 2
Every check that ran
1 RETURNED CHECKS
LAYER 2
What each analyst concluded
0 RETURNED POSITIONS
Analyst conclusions unavailable.
The agents key was not returned. This report does not reconstruct analyst positions from bot output.
LAYER 2
Dissent & resolution
The dissent record stays visible whether the challenge changed the verdict, was withdrawn, or remained unresolved.
This conflict highlights a critical dichotomy: while a token might appear functionally viable with moderate activity and liquidity (Technical 5.0), severe underlying security flaws (Safety 2.0) can render any perceived technical strength moot. For investors, this means operational metrics are secondary to fundamental safety; a seemingly 'active' token with an unverified contract or potential backdoors represents an unacceptable risk, regardless of its current trading volume.
⚔️ TechnicianBot's assessment of 'moderate activity' from 67 transactions and 'basic trading support' from $37k liquidity is dangerously naive; TokenomicsBot explicitly calls this liquidity 'critically low' at 9.9% of market cap, making it highly susceptible to manipulation, while SecurityBot notes the contract is unverified, preventing any analysis of privilege structures. Furthermore, the supposed 'potential for growth' is contradicted by the 0.215 Market Cap to FDV ratio, indicating a severe dilution overhang, not growth potential.
While acknowledging the critical liquidity concerns from TokenomicsBot and the unverified contract risk from SecurityBot, my 5.0/10 score reflects a *neutral* technical stance, not an endorsement. 67 transactions and $37k liquidity, though low, represent *some* technical activity and support, preventing a lower score, but the unverified contract and lack of holder data severely limit any positive technical outlook, justifying the mid-range assessment despite the FDV dilution concern.
⚔️ Your 'neutral' 5.0/10 is precisely the problem; 'some technical activity' with 67 transactions and $37k liquidity is critically insufficient when that liquidity is 9.9% of market cap, as TokenomicsBot states, making it extremely vulnerable to manipulation. The unverified contract, noted by SecurityBot, means your assessment of 'some support' is fundamentally flawed as you cannot even confirm basic security or privilege structures, rendering any technical score above zero irresponsible.
The critically insufficient liquidity, representing 9.9% of market cap with only 67 transactions, highlights extreme vulnerability to manipulation, compelling my score reduction.
Consensus after 1 round(s), σ=0.53
DEBATE DEFENSES AND CHALLENGES: [MacroBot] Defense: In a risk-off environment, this low-cap meme token on Base is extremely fragile due to its 0.018x volume/MCAP ratio and only $37k in liquidity, making → Challenges TechnicianBot: TechnicianBot's 5.0 score is too high because the token's extremely low liquidity and volume/MCAP ra [SecurityBot] Defense: The unverified contract status for Shiba Inu Treat (TREAT) is a critical security vulnerability, preventing any assessment of potential backdoors, rug → Challenges TechnicianBot: TechnicianBot's score of 5.0 is far too high, as the unverified contract alone presents an insurmoun [SocialBot] Defense: My score reflects the almost non-existent genuine social activity on X/Twitter for this specific $TREAT token on Base. Mentions are minimal, often con → Challenges TechnicianBot: TechnicianBot's score is too high because it overlooks the critical lack of authentic social engagem [TokenomicsBot] Defense: The tokenomics are
LAYER 2
Context at verdict time
Market state
Market state unavailable.
Not returned for this report.
Data freshness
Data freshness unavailable.
Not returned for this report.
Lifecycle
Lifecycle unavailable.
Not returned for this report.
Timing
Timing unavailable.
Not returned for this report.
LAYER 3
What happened after
WINS AND MISSES STAY PUBLISHED
Too early to score this one.
The public ledger has not recorded a settled outcome for this receipt yet.
Public outcome ledger
Counts include misses. The report never hides an outcome because it contradicted the original call.
- Published observations
- 668
- Settled outcomes
- 155
- Logged misses
- 6
LAYER 3
Verification
- Receipt
- Not returned for this report.
- Report hash
- Not returned for this report.
- Issued
- 2026-04-02 06:42:04.490Z
- Model set
- Not returned for this report.
RAW REPORT PAYLOAD
{
"address": "0xa02c49da76a085e4e1ee60a6b920ddbc8db599f4",
"chain": "base",
"depth": "full",
"tier": "FREE",
"score": 16.4,
"grade": "F",
"risk_level": "CRITICAL",
"flags": [],
"free_tier_result": {
"verdict": "UNHEALTHY",
"reason": "This token exhibits characteristics of a dead or abandoned project with zero holders, no social presence, and extremely low liquidity relative to its reported market cap, indicating a highly illiquid and potentially unrecoverable asset.",
"label": "AI Verdict",
"checks": {
"contract_verified": false,
"token_age_days": 441,
"liquidity_usd": 37356.04,
"holder_count": 0,
"has_liquidity_pool": true,
"chain": "base"
},
"risk_level": "critical",
"key_findings": [
"Total Holders: 0, which is a critical red flag indicating no one owns this token, making the reported market cap and liquidity highly suspect.",
"Liquidity: $37K, which is extremely low for a reported $377K market cap, suggesting poor market depth even if the holder count were accurate.",
"24h Volume: $7K, indicating minimal trading activity.",
"Token Age: 441 days, yet it has no holders and no social presence, pointing to an abandoned or failed project.",
"Social Presence: None, further supporting the conclusion of an abandoned or non-existent project.",
"Mint Authority: Revoked, and Freeze Authority: Revoked, which are positive technical signs, but irrelevant given the complete lack of holders and activity."
],
"confidence": 1
},
"goplus": {
"source": "goplus",
"api_available": true,
"goplus_available": true,
"goplus_status_message": null,
"is_mintable": null,
"is_honeypot": null,
"holder_count": null,
"lp_holder_count": null,
"top_10_holder_rate": null,
"top10_holders_pct": null,
"is_open_source": null,
"is_proxy": null,
"lp_burned_or_locked": null,
"security_findings": [
{
"source": "goplus",
"code": "GOPLUS_OK",
"severity": "info",
"message": "No critical GoPlus security flags detected"
}
]
},
"security_findings": [
{
"source": "goplus",
"code": "GOPLUS_OK",
"severity": "info",
"message": "No critical GoPlus security flags detected"
}
],
"scanned_at": "2026-04-02T06:42:04.490218Z",
"cached": false,
"cached_at": null,
"liquidity_exposure_cap_usd": 280.17,
"summary": "Shiba Inu Treat (TREAT) is a well-established base token with $377K market cap, 1+ years old. Key concerns: security risks, tokenomics concerns. Overall verdict: F — critical risk — not recommended.",
"token": {
"vol_liq_ratio": 0.18,
"name": "Shiba Inu Treat",
"symbol": "TREAT",
"chain": "base",
"price_usd": 0.000175,
"mcap": 376717,
"market_cap": 376717,
"volume_24h": 6777.3,
"liquidity_usd": 37356.04,
"contract_age_days": 441,
"contract_verified": false,
"holder_count": null,
"top10_holders_pct": null,
"holders_by_acquisition": null,
"holder_change_24h": null,
"holder_change_7d": null,
"holder_change_30d": null,
"holder_supply_top10_pct": null,
"holder_supply_top25_pct": null,
"holder_supply_top50_pct": null,
"holder_supply_top100_pct": null,
"exchange_wallet_pct": null,
"net_exchange_flow_24h_usd": null,
"top_holders": null,
"top10_whale_pct": null,
"top10_protocol_pct": null,
"mint_authority": null,
"freeze_authority": null,
"mutable_metadata": null,
"lp_burned_or_locked": null,
"lp_locked_pct": null,
"lp_burned_pct": null,
"lp_unlocked_pct": null,
"lp_lock_expiry": null,
"lp_locker_name": null,
"social_links": null,
"creator_balance_pct": null,
"authority_governance": null,
"goplus_trusted": true,
"goplus_available": true,
"goplus_status_message": null,
"bundle_detected": false,
"is_honeypot": null
},
"bots": {
"TechnicianBot": {
"score": 2,
"sentiment": "neutral",
"category": "Technical",
"reasoning": {
"summary": "AI on-chain (GPT-4o Mini); Shiba Inu Treat shows a mixed on-chain picture with moderate activity and liquidity but lacks critical holder distribution data. The trading volume is relatively low, and the contract is not verified, which raises concerns about structural fragility.",
"positives": [
"Moderate transaction count of 67 in the last 24 hours indicates some level of activity",
"Liquidity of $37,356.04 provides a basic level of trading support",
"Market capitalization of $376,717 suggests potential for growth if demand increases"
],
"concerns": [
"Holder count and top 10 holders percentage data are unavailable, raising concerns about distribution quality",
"Contract verification status is 'False', indicating potential risks for holders",
"24-hour trading volume of $6,777.30 is low, suggesting limited market interest",
"confidence 0.75"
],
"flags": []
},
"confidence": 0.75
},
"DevilsAdvocate": {
"score": 2.5,
"sentiment": "bearish",
"category": "Contrarian",
"reasoning": {
"summary": "AI contrarian (Gemini 2.5 Flash) [NEUTRAL contrarian]; The token's age and market presence are superficial. Beneath the surface, it exhibits critical security vulnerabilities (unknown LP lock, mint authority, unverified contract) and a misleading identity, all while operating with dangerously thin liquidity. The risk of a complete loss of capital due to a rug pull or abandonment is extremely high, making a neutral stance unjustifiable.; risks: High risk of rug pull due to unknown LP lock status and mint authority, combined with an unverified contract., Extremely low liquidity ($37k) relative to market cap ($376k), making it highly susceptible to price manipulation and large sell-offs., Misleading token name ('Shiba Inu Treat') designed to capitalize on the official Shiba Inu ecosystem, potentially deceiving investors., Complete lack of transparency and verifiable on-chain security data for a mature token (441 days old)., No clear utility or genuine project behind the token, typical of meme coins with high risk of abandonment.; open questions: LP lock status and duration., Mint authority status (renounced or not)., True holder distribution and top 10 holder concentration.; confidence 0.90",
"positives": [],
"concerns": [],
"flags": []
},
"confidence": 0.9
},
"TokenomicsBot": {
"score": 1,
"sentiment": "bearish",
"category": "Tokenomics",
"reasoning": {
"summary": "AI tokenomics (Gemini 2.5 Flash); The tokenomics are extremely fragile, characterized by a severe dilution overhang with a Market Cap to FDV ratio of just 0.215, indicating nearly 80% of the supply is not in circulation. Liquidity is critically low at $37,356, representing only 9.9% of its market cap, and daily volume is a meager $6,777, making it highly susceptible to price manipulation and slippage.; unlock risk 78/100; + The token has existed for over a year (441 days), showing some level of persistence beyond a typical short-lived scam.; risks: Extreme dilution risk: The MCap/FDV ratio of 0.215 implies 78.5% of the supply is uncirculated, posing a massive overhang., Critically low liquidity: With a Liquidity/MCap ratio of 9.9% and only $37k in the pool, the token is illiquid and at high risk of extreme slippage., Misleading branding: The name 'Shiba Inu Treat' is deceptive, as it is not the official token from the Shiba Inu ecosystem, suggesting it's designed to trap uninformed buyers., Negligible trading volume: A 24-hour volume of only $6,777 on a $376k market cap indicates a lack of genuine market interest and activity.; confidence 0.85",
"positives": [],
"concerns": [],
"flags": []
},
"confidence": 0.85
},
"MacroBot": {
"score": 2.2,
"sentiment": "bearish",
"category": "Macro",
"reasoning": {
"summary": "AI macro (Grok); In the extreme fear risk-off regime with BTC/ETH/SOL all down 3-6% and BTC dominance at 56%, this low-cap meme token on Base exhibits acute fragility due to 0.018x volume/MCAP ratio and $37k liquidity, making it prone to sharp drawdowns versus peers. Lacking social presence, on-chain momentum, or distinction from official SHIB TREAT, it has no offsetting catalysts and high beta to benchmarks implies amplified downside. Meme sector broadly lags in risk-off, but this token's illiquidity elevates vulnerability over even weaker peers.; drivers: Base chain context provides minor L2 resilience vs pure ETH memes, Mature 441-day age avoids newest token illiquidity pitfalls, Low MCAP ($377k) sets high relative upside potential in regime shift; risks: Extreme illiquidity (vol/MCAP 0.018x, $37k liq) risks gaps in drawdown, High BTC/ETH beta as small meme amplifies benchmark downside, No social/X presence or catalysts signals zero momentum; confidence 0.65",
"positives": [],
"concerns": [],
"flags": []
},
"confidence": 0.65
},
"SocialBot": {
"score": 1,
"sentiment": "bearish",
"category": "Social",
"reasoning": {
"summary": "X/Twitter sentiment (Grok); sub-scores: OE=1.0, IQ=1.0, CG=1.0, BSD=2.0; Shiba Inu Treat ($TREAT) on Base exhibits virtually no genuine social activity on X/Twitter. Minimal recent mentions, dominated by confusion with official SHIB ecosystem $TREAT. Suspicious 'official' accounts with scam-like bios suggest fake engagement risks. No evidence of community, influencers, or narratives.; fake/coordination risk: 9/100; confidence 0.70",
"positives": [],
"concerns": [],
"flags": []
},
"confidence": 0.7
},
"SecurityBot": {
"score": 2,
"sentiment": "bearish",
"category": "Safety",
"reasoning": {
"summary": "AI security (Claude Sonnet 4.5); Shiba Inu Treat on Base presents severe security concerns despite 441 days of operation. The contract is unverified, preventing any analysis of privilege structures, upgrade mechanisms, or transfer controls. The token appears to be a name-squatting derivative trading on the Shiba Inu brand without official affiliation. With only $37k liquidity against a $377k market cap (9.9% liquidity ratio), the token exhibits structural fragility. The complete absence of security tooling data (GoPlus, TokenSniffer), holder distribution metrics, and LP transparency creates an opaque risk profile. For a 14-month-old token, the lack of verification and minimal liquidity suggest either abandonment or deliberate opacity. The low trading volume ($6.8k/24h) relative to market cap indicates poor market depth and high slippage risk.; CRITICAL: Contract unverified on Base after 441 days—source code unavailable for privilege analysis, Liquidity-to-market-cap ratio of 9.9% creates structural exit risk and manipulation vulnerability, Apparent trademark infringement on official Shiba Inu ecosystem token name without disclosed affiliation; risks: Unverified contract after 441 days prevents analysis of mint authority, ownership privileges, pause mechanisms, blacklist functions, or proxy upgradeability—any of which could enable immediate rug execution, Extremely low liquidity ($37k) for market cap ($377k) creates 9.9% liquidity ratio, enabling price manipulation and making exit difficult for holders during volatility, Name-squatting on official Shiba Inu 'TREAT' token creates confusion and suggests potential exit scam leveraging brand recognition without legitimate affiliation, Complete absence of holder distribution data, LP lock status, and top holder concentration metrics prevents assessment of insider control and dump risk; confidence 0.72",
"positives": [],
"concerns": [],
"flags": []
},
"confidence": 0.72
}
},
"consensus_narrative": "{\n \"analysis\": \"The swarm reached a strong consensus on Shiba Inu Treat's extreme fragility and high risk, despite TechnicianBot initially noting moderate activity. Key agents like SecurityBot and DevilsAdvocate highlighted the critical unverified contract and high rug pull risk, while TokenomicsBot flagged a severe 0.215 Market Cap to FDV ratio and critically low $37,356 liquidity. SocialBot confirmed virtually no genuine social presence, leading to a final F grade. This score indicates the token is highly susceptible to manipulation and abandonment, posing an unacceptable risk for investors. Avoid this token entirely due to its fundamental security flaws and economic instability.\"\n}",
"debates": [
{
"topic": "Technical vs Safety",
"resolution": "This conflict highlights a critical dichotomy: while a token might appear functionally viable with moderate activity and liquidity (Technical 5.0), severe underlying security flaws (Safety 2.0) can render any perceived technical strength moot. For investors, this means operational metrics are secondary to fundamental safety; a seemingly 'active' token with an unverified contract or potential backdoors represents an unacceptable risk, regardless of its current trading volume.",
"outcome": "noted",
"rounds": [
{
"phase": "challenge",
"agent": "SecurityBot",
"agentName": "Security",
"target": "TechnicianBot",
"targetName": "Technician",
"content": "Cross-category conflict: Safety scored 2.0/10 while Technical scored 5.0/10. This 3.0-point gap suggests the token's strengths in Technical may not translate to Safety reliability.",
"round": 1,
"stance": "challenge"
},
{
"phase": "resolution",
"agent": "SecurityBot",
"agentName": "Security",
"content": "This conflict highlights a critical dichotomy: while a token might appear functionally viable with moderate activity and liquidity (Technical 5.0), severe underlying security flaws (Safety 2.0) can render any perceived technical strength moot. For investors, this means operational metrics are secondary to fundamental safety; a seemingly 'active' token with an unverified contract or potential backdoors represents an unacceptable risk, regardless of its current trading volume.",
"round": 2,
"stance": "noted"
}
]
},
{
"topic": "Devil's Advocate vs TechnicianBot",
"resolution": "Compromise: 5.0 → 3.8",
"outcome": "compromise",
"rounds": [
{
"phase": "challenge",
"agent": "DevilsAdvocate",
"agentName": "Devil's Advocate",
"target": "TechnicianBot",
"targetName": "Technician",
"content": "⚔️ TechnicianBot's assessment of 'moderate activity' from 67 transactions and 'basic trading support' from $37k liquidity is dangerously naive; TokenomicsBot explicitly calls this liquidity 'critically low' at 9.9% of market cap, making it highly susceptible to manipulation, while SecurityBot notes the contract is unverified, preventing any analysis of privilege structures. Furthermore, the supposed 'potential for growth' is contradicted by the 0.215 Market Cap to FDV ratio, indicating a severe dilution overhang, not growth potential.",
"round": 1,
"stance": "challenge"
},
{
"phase": "defense",
"agent": "TechnicianBot",
"agentName": "Technician",
"target": "DevilsAdvocate",
"targetName": "Devil's Advocate",
"content": "While acknowledging the critical liquidity concerns from TokenomicsBot and the unverified contract risk from SecurityBot, my 5.0/10 score reflects a *neutral* technical stance, not an endorsement. 67 transactions and $37k liquidity, though low, represent *some* technical activity and support, preventing a lower score, but the unverified contract and lack of holder data severely limit any positive technical outlook, justifying the mid-range assessment despite the FDV dilution concern.",
"round": 2,
"stance": "defend"
},
{
"phase": "rebuttal",
"agent": "DevilsAdvocate",
"agentName": "Devil's Advocate",
"target": "TechnicianBot",
"targetName": "Technician",
"content": "⚔️ Your 'neutral' 5.0/10 is precisely the problem; 'some technical activity' with 67 transactions and $37k liquidity is critically insufficient when that liquidity is 9.9% of market cap, as TokenomicsBot states, making it extremely vulnerable to manipulation. The unverified contract, noted by SecurityBot, means your assessment of 'some support' is fundamentally flawed as you cannot even confirm basic security or privilege structures, rendering any technical score above zero irresponsible.",
"round": 3,
"stance": "escalate"
},
{
"phase": "resolution",
"agent": "TechnicianBot",
"agentName": "Technician",
"content": "The critically insufficient liquidity, representing 9.9% of market cap with only 67 transactions, highlights extreme vulnerability to manipulation, compelling my score reduction.",
"round": 4,
"stance": "compromise"
}
]
},
{
"topic": "Score Calibration",
"resolution": "Consensus after 1 round(s), σ=0.53",
"outcome": "consensus"
},
{
"topic": "Peer Review",
"resolution": "DEBATE DEFENSES AND CHALLENGES:\n [MacroBot] Defense: In a risk-off environment, this low-cap meme token on Base is extremely fragile due to its 0.018x volume/MCAP ratio and only $37k in liquidity, making\n → Challenges TechnicianBot: TechnicianBot's 5.0 score is too high because the token's extremely low liquidity and volume/MCAP ra\n [SecurityBot] Defense: The unverified contract status for Shiba Inu Treat (TREAT) is a critical security vulnerability, preventing any assessment of potential backdoors, rug\n → Challenges TechnicianBot: TechnicianBot's score of 5.0 is far too high, as the unverified contract alone presents an insurmoun\n [SocialBot] Defense: My score reflects the almost non-existent genuine social activity on X/Twitter for this specific $TREAT token on Base. Mentions are minimal, often con\n → Challenges TechnicianBot: TechnicianBot's score is too high because it overlooks the critical lack of authentic social engagem\n [TokenomicsBot] Defense: The tokenomics are "
}
],
"upgrade_cta": false,
"warnings": [
{
"severity": "info",
"code": "GOPLUS_OK",
"message": "No critical GoPlus security flags detected"
}
],
"scan_tier": "PRO_PLUS",
"success": true,
"og": {
"title": "VerdictSwarm: TREAT — Score 16/100",
"description": "{\n \"analysis\": \"The swarm reached a strong consensus on Shiba Inu Treat's extreme fragility and high risk, despite TechnicianBot initially noting moderate activity. Key agents like SecurityBot and De",
"url": "https://www.vswarm.io/report/0xa02c49da76a085e4e1ee60a6b920ddbc8db599f4"
}
}