LAYER 0 · PRE-TRADE RISK REPORTSETTLED 2026-04-17 00:55:01.222Z

UNSETTLED

36/100

GRADE F

REPPO ON BASE (REPPO) is a base token with $2.3M market cap, 131 days old. The Swarm found deep liquidity ($1.9M). Key concerns: tokenomics concerns, weak technical fundamentals. Overall verdict: F — critical risk — not recommended.

NO ACTION RETURNEDREPLAY THE INTERROGATION

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
$10,000.00

HARD BLOCKERS

  • Top 10 holders concentration is very high
  • high_holder_concentration

HOLDER CLUSTERS

Top 10 holder share
100%
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

CATEGORYCHECKFINDINGRESULT
securityTOP10_CONCENTRATIONTop 10 holders concentration is very highhigh

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.

[Technician]challenge

Cross-category conflict: Technical scored 3.0/10 while Safety scored 8.5/10. This 5.5-point gap suggests the token's strengths in Safety may not translate to Technical reliability.

[Technician]noted

This conflict indicates that while the token's smart contract is secure and immutable (SafetyBot 8.5/10), its market health and liquidity are severely compromised (TechnicianBot 3.0/10). Investors face a 'rug pull' risk not from code exploits, but from the inability to sell due to poor liquidity, high concentration, and lack of demand, despite the contract being technically sound.

[Devil's Advocate]challenge

⚔️ SecurityBot's 8.5/10 is absurdly optimistic; how can a token with 'extremely low 24h volume ($0)' and 'data gaps around LP lock status' be considered operationally stable or safe? The $1.9M liquidity is meaningless if the token is effectively untradeable, making any CEX listing rumor irrelevant to its current, critical illiquidity.

[Security]defend

The 8.5/10 score reflects the token's exceptional smart contract security: it's a fixed-supply, non-upgradable ERC-20 with no admin controls, minting, or transfer restrictions, eliminating common attack vectors. While zero volume and LP lock data gaps are valid market viability and rug-pull concerns, they do not compromise the inherent security of the contract's architecture itself, which is the primary focus of this safety score. The contract's immutability and lack of privileged functions make it robust against malicious code execution or manipulation.

[Devil's Advocate]escalate

⚔️ While the smart contract's immutability and lack of admin controls indeed bolster its architectural integrity, this inherent security is rendered practically moot by zero trading volume ($0) and undisclosed LP lock status. The absence of market activity and transparent liquidity protection means users cannot exit positions safely, making the token's 'security' an academic point for an illiquid, potentially un-ruggable asset.

[Security]defend

While the zero trading volume and undisclosed LP lock are valid concerns for market viability and investor protection, they do not directly impact the smart contract's inherent security against exploits or unauthorized modifications. My 8.5/10 score specifically reflects the robust architectural integrity, immutability, and absence of critical vulnerabilities within the contract code itself, which remains secure regardless of market dynamics.

[swarm]resolution

Consensus after 2 round(s), σ=0.77

[swarm]resolution

DEBATE DEFENSES AND CHALLENGES: [TechnicianBot] Defense: The token's extremely low trading volume relative to its market cap, coupled with an anomalous top holder concentration, indicates severe structural f → Challenges SocialBot: SocialBot's higher score overestimates the token's health, as social metrics cannot compensate for t → Challenges SecurityBot: SecurityBot's score is excessively high because while contract security is important, it does not mi [MacroBot] Defense: My score reflects the extreme liquidity vulnerability indicated by near-zero 24h volume ($0.02) against a $2.3M market cap, which makes REPPO highly f → Challenges SocialBot: SocialBot's 5.8 score is too high because strong social sentiment or narrative tailwinds cannot over → Challenges SecurityBot: SecurityBot's 8.5 score is excessively high as even perfect security cannot compensate for a token's [TokenomicsBot] Defense: The complete absence of reported trading volume ($0) for a token with

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-17 00:55:01.222Z
Model set
Not returned for this report.
RECEIPT LINK UNAVAILABLEOPEN PUBLIC LEDGER →

RAW REPORT PAYLOAD

{
  "address": "0x8b978ae767588afde3ac54df778d6b01e1bc01bf",
  "chain": "base",
  "depth": "full",
  "tier": "FREE",
  "score": 36.4,
  "grade": "F",
  "risk_level": "CRITICAL",
  "flags": [
    "high_holder_concentration"
  ],
  "free_tier_result": {
    "verdict": "UNHEALTHY",
    "reason": "This token exhibits contradictory financial data, with a reported $2.3M market cap and $1.9M liquidity but a $0.00 price and negligible trading volume, indicating a potential data error, a dead token, or a severe market anomaly.",
    "label": "AI Verdict",
    "checks": {
      "contract_verified": true,
      "token_age_days": 131,
      "liquidity_usd": 1877377.23,
      "holder_count": 36304,
      "has_liquidity_pool": true,
      "chain": "base"
    },
    "risk_level": "critical",
    "key_findings": [
      "Reported price is $0.00 despite a $2.3M market cap and $1.9M liquidity, which is a critical inconsistency.",
      "24h trading volume is $0.02, indicating no active trading for a token with significant reported liquidity.",
      "Top 10 holders control 100.0% of the supply, with 0.0% attributed to protocol-controlled wallets, suggesting extreme centralization in individual hands.",
      "Lack of social presence and unknown mutable metadata status adds to the risk profile.",
      "Mint and Freeze authorities are revoked, which is a positive security measure, but overshadowed by other critical issues."
    ],
    "confidence": 1
  },
  "goplus": {
    "source": "goplus",
    "api_available": true,
    "goplus_available": true,
    "goplus_status_message": null,
    "is_mintable": false,
    "is_honeypot": false,
    "holder_count": 36304,
    "lp_holder_count": null,
    "top_10_holder_rate": 1,
    "top10_holders_pct": 100,
    "is_open_source": true,
    "is_proxy": false,
    "lp_burned_or_locked": null,
    "security_findings": [
      {
        "source": "goplus",
        "code": "TOP10_CONCENTRATION",
        "severity": "high",
        "message": "Top 10 holders concentration is very high",
        "value": 100
      }
    ]
  },
  "security_findings": [
    {
      "source": "goplus",
      "code": "TOP10_CONCENTRATION",
      "severity": "high",
      "message": "Top 10 holders concentration is very high",
      "value": 100
    }
  ],
  "scanned_at": "2026-04-17T00:55:01.222126Z",
  "cached": false,
  "cached_at": null,
  "liquidity_exposure_cap_usd": 10000,
  "summary": "REPPO ON BASE (REPPO) is a base token with $2.3M market cap, 131 days old. The Swarm found deep liquidity ($1.9M).  Key concerns: tokenomics concerns, weak technical fundamentals. Overall verdict: F — critical risk — not recommended.",
  "token": {
    "vol_liq_ratio": 0,
    "name": "REPPO ON BASE",
    "symbol": "REPPO",
    "chain": "base",
    "price_usd": 2.346e-9,
    "mcap": 2346721,
    "market_cap": 2346721,
    "volume_24h": 0.02,
    "liquidity_usd": 1877377.23,
    "contract_age_days": 131,
    "contract_verified": true,
    "holder_count": 36304,
    "top10_holders_pct": 100,
    "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": false
  },
  "bots": {
    "SocialBot": {
      "score": 3,
      "sentiment": "neutral",
      "category": "Social",
      "reasoning": {
        "summary": "X/Twitter sentiment (Grok); sub-scores: OE=4.5, IQ=6.5, CG=5.0, BSD=8.0; ⚠️ BREAKING: $REPPO rumored to list on Kraken soon; REPPO on Base is currently driven by a strong narrative around an unconfirmed Kraken CEX listing and reported smart money accumulation on the Base chain. While sentiment is predominantly bullish, the project lacks official social channels and verifiable community metrics, leading to low confidence in its organic health.; narratives: Anticipation around Kraken CEX listing, Smart money rotation into Base memecoins/lowcaps like $REPPO; fake/coordination risk: 20/100; confidence 0.40",
        "positives": [],
        "concerns": [],
        "flags": []
      },
      "confidence": 0.4
    },
    "TechnicianBot": {
      "score": 3,
      "sentiment": "bearish",
      "category": "Technical",
      "reasoning": {
        "summary": "AI on-chain (GPT-4o Mini); REPPO ON BASE exhibits significant structural fragility, characterized by extremely low trading volume relative to its market cap and an anomalous top holder concentration. While the holder count appears robust, the lack of trading activity and liquidity depth raises concerns about the token's tradability and overall health.",
        "positives": [
          "Verified contract provides some assurance of legitimacy",
          "Total holder count of 36,304 suggests a potentially engaged community",
          "Market cap of $2.3M indicates some level of interest"
        ],
        "concerns": [
          "24-hour trading volume is only $0.02, indicating negligible activity",
          "Top 10 holders percentage reported as 100.0% suggests data error or extreme concentration",
          "Liquidity of $1.88M is not being utilized effectively given the low transaction count"
        ],
        "flags": [
          "Top 10 holders percentage at 100.0% is highly improbable and suggests incomplete data",
          "confidence 0.70"
        ]
      },
      "confidence": 0.7
    },
    "DevilsAdvocate": {
      "score": 2,
      "sentiment": "bearish",
      "category": "Contrarian",
      "reasoning": {
        "summary": "AI contrarian (Gemini 2.5 Flash) [NEUTRAL contrarian]; Despite a neutral consensus, the token exhibits critical red flags: negligible trading volume rendering its market cap illusory, unverified LP lock status, and unknown mint authority. These combined factors point to a highly illiquid and potentially insecure asset, making it a high-risk investment even for a meme token.; risks: Extreme illiquidity: $0.02 24h volume for a $2.3M market cap means the token is effectively untradeable at its stated value., Potential rug pull risk: Unknown LP lock status means liquidity could be withdrawn by the deployer at any time., Centralization risk: The '100% top 10 holders' data, even if an error, highlights a critical data gap regarding actual token distribution and potential insider control., Dilution risk: Unknown mint authority means new tokens could be created, devaluing existing holdings., Market cap illusion: The reported market cap is not supported by any real trading activity, making it highly susceptible to sudden and severe price collapse if any selling pressure emerges.; open questions: Actual token distribution beyond the top 10 holders., Status of LP lock/burn., Status of mint authority renouncement.; confidence 0.90",
        "positives": [],
        "concerns": [],
        "flags": []
      },
      "confidence": 0.9
    },
    "TokenomicsBot": {
      "score": 4,
      "sentiment": "bearish",
      "category": "Tokenomics",
      "reasoning": {
        "summary": "AI tokenomics (Gemini 2.5 Flash); The token presents a contradictory and high-risk profile. While it boasts a large holder base (36,304) and an excellent MCap/FDV ratio of 1.0, the complete absence of trading volume ($0 reported) at a $2.3M market cap is a critical red flag. The extremely high liquidity-to-market cap ratio (0.8) is rendered meaningless by the lack of trading activity, suggesting the liquidity may be artificial or the token is effectively abandoned.; unlock risk 0/100; + The MCap/FDV ratio is 1.0, indicating no future dilution risk from unissued tokens., The reported holder count of 36,304 is very high for its market cap, suggesting a potentially wide initial distribution., The contract is verified on the Base blockchain.; risks: The 24-hour trading volume is $0, indicating a complete lack of market activity and making the $2.3M valuation highly questionable and impossible to realize., Extreme illiquidity risk despite a high on-paper liquidity value; it is impossible to sell any significant position without causing a total price collapse., The token appears to be abandoned or frozen, with no active trading interest from the community or market makers., The top 10 holder data is erroneous (100%), hiding the true concentration risk which could be severe.; confidence 0.60",
        "positives": [],
        "concerns": [],
        "flags": []
      },
      "confidence": 0.6
    },
    "MacroBot": {
      "score": 3.2,
      "sentiment": "bearish",
      "category": "Macro",
      "reasoning": {
        "summary": "AI macro (Grok); REPPO, a Base meme token, faces high fragility in the current risk-off regime marked by extreme fear (23/100) and BTC/ETH mixed performance, exacerbated by near-zero 24h volume ($0.02) relative to $2.3M mcap, signaling acute liquidity vulnerability. Unverified Kraken listing rumors and smart money rotation into Base lowcaps provide narrative tailwinds, but these are outweighed by meme sector weakness and lack of confirmed catalysts. Likely to underperform peers with better liquidity, amplifying downside in any further drawdown.; drivers: Smart money accumulation on Base (ranked #1 by @with_luma, @PoodleFi_), Kraken listing rumors driving community excitement, Decent holder count (36k) for size, suggesting some base retention; risks: Extreme illiquidity (0.0x volume/mcap ratio, $0.02 24h vol), Meme sector exposure in risk-off (Extreme Fear, BTC dom 56.9%), Unverified catalysts prone to fizzle or cause sell pressure; confidence 0.62",
        "positives": [],
        "concerns": [],
        "flags": []
      },
      "confidence": 0.62
    },
    "SecurityBot": {
      "score": 5,
      "sentiment": "bullish",
      "category": "Safety",
      "reasoning": {
        "summary": "AI security (Claude Sonnet 4.5); REPPO ON BASE is a clean, minimalist ERC-20 implementation with no admin privileges, no upgradeability, no mint function, and no transfer restrictions. The verified source code shows a standard token contract with fixed supply minted at deployment. At 131 days old with $2.3M mcap and $1.9M liquidity, the token has demonstrated operational stability. The contract architecture eliminates common attack vectors (no owner, no pause, no blacklist, no fees). Primary concerns are data gaps around LP lock status and holder distribution, plus extremely low 24h volume ($0.02) that suggests either stale data or temporary liquidity issues. The contract itself presents minimal structural risk to holders.; risks: LP lock/burn status unknown — without confirmed LP lock or burn, liquidity could theoretically be withdrawn by LP providers, though 131-day operating history reduces immediate concern, Holder distribution data unavailable — cannot verify concentration risk or insider control, though 36,304 holders suggests reasonable distribution, Extremely low 24h volume ($0.02 vs $2.3M mcap) — likely stale API data, but if accurate indicates severe liquidity crisis or market dysfunction, No formal audit — while contract is simple and verifiable, lack of third-party security review means potential edge cases unexamined; confidence 0.78",
        "positives": [],
        "concerns": [],
        "flags": []
      },
      "confidence": 0.78
    }
  },
  "consensus_narrative": "The swarm agreed REPPO ON BASE is an extremely high-risk asset, primarily due to its severe illiquidity, evidenced by $0.02 24h volume against a $2.3M market cap, making it effectively untradeable (TechnicianBot, TokenomicsBot, MacroBot). Key disagreement centered on SecurityBot's high score for contract safety versus other agents arguing contract security doesn't negate market health issues. Despite 36,304 holders and unconfirmed Kraken rumors (SocialBot), the F grade signifies critical market fragilities and high risk. Investors should exercise extreme caution and recognize the token's untradeable nature.",
  "debates": [
    {
      "topic": "Safety vs Technical",
      "resolution": "This conflict indicates that while the token's smart contract is secure and immutable (SafetyBot 8.5/10), its market health and liquidity are severely compromised (TechnicianBot 3.0/10). Investors face a 'rug pull' risk not from code exploits, but from the inability to sell due to poor liquidity, high concentration, and lack of demand, despite the contract being technically sound.",
      "outcome": "noted",
      "rounds": [
        {
          "phase": "challenge",
          "agent": "TechnicianBot",
          "agentName": "Technician",
          "target": "SecurityBot",
          "targetName": "Security",
          "content": "Cross-category conflict: Technical scored 3.0/10 while Safety scored 8.5/10. This 5.5-point gap suggests the token's strengths in Safety may not translate to Technical reliability.",
          "round": 1,
          "stance": "challenge"
        },
        {
          "phase": "resolution",
          "agent": "TechnicianBot",
          "agentName": "Technician",
          "content": "This conflict indicates that while the token's smart contract is secure and immutable (SafetyBot 8.5/10), its market health and liquidity are severely compromised (TechnicianBot 3.0/10). Investors face a 'rug pull' risk not from code exploits, but from the inability to sell due to poor liquidity, high concentration, and lack of demand, despite the contract being technically sound.",
          "round": 2,
          "stance": "noted"
        }
      ]
    },
    {
      "topic": "Devil's Advocate vs SecurityBot",
      "resolution": "Split verdict: SecurityBot maintains 8.5, Devil's Advocate maintains 2.0. Both positions presented.",
      "outcome": "split",
      "rounds": [
        {
          "phase": "challenge",
          "agent": "DevilsAdvocate",
          "agentName": "Devil's Advocate",
          "target": "SecurityBot",
          "targetName": "Security",
          "content": "⚔️ SecurityBot's 8.5/10 is absurdly optimistic; how can a token with 'extremely low 24h volume ($0)' and 'data gaps around LP lock status' be considered operationally stable or safe? The $1.9M liquidity is meaningless if the token is effectively untradeable, making any CEX listing rumor irrelevant to its current, critical illiquidity.",
          "round": 1,
          "stance": "challenge"
        },
        {
          "phase": "defense",
          "agent": "SecurityBot",
          "agentName": "Security",
          "target": "DevilsAdvocate",
          "targetName": "Devil's Advocate",
          "content": "The 8.5/10 score reflects the token's exceptional smart contract security: it's a fixed-supply, non-upgradable ERC-20 with no admin controls, minting, or transfer restrictions, eliminating common attack vectors. While zero volume and LP lock data gaps are valid market viability and rug-pull concerns, they do not compromise the inherent security of the contract's architecture itself, which is the primary focus of this safety score. The contract's immutability and lack of privileged functions make it robust against malicious code execution or manipulation.",
          "round": 2,
          "stance": "defend"
        },
        {
          "phase": "rebuttal",
          "agent": "DevilsAdvocate",
          "agentName": "Devil's Advocate",
          "target": "SecurityBot",
          "targetName": "Security",
          "content": "⚔️ While the smart contract's immutability and lack of admin controls indeed bolster its architectural integrity, this inherent security is rendered practically moot by zero trading volume ($0) and undisclosed LP lock status. The absence of market activity and transparent liquidity protection means users cannot exit positions safely, making the token's 'security' an academic point for an illiquid, potentially un-ruggable asset.",
          "round": 3,
          "stance": "escalate"
        },
        {
          "phase": "resolution",
          "agent": "SecurityBot",
          "agentName": "Security",
          "content": "While the zero trading volume and undisclosed LP lock are valid concerns for market viability and investor protection, they do not directly impact the smart contract's inherent security against exploits or unauthorized modifications. My 8.5/10 score specifically reflects the robust architectural integrity, immutability, and absence of critical vulnerabilities within the contract code itself, which remains secure regardless of market dynamics.",
          "round": 4,
          "stance": "defend"
        }
      ]
    },
    {
      "topic": "Score Calibration",
      "resolution": "Consensus after 2 round(s), σ=0.77",
      "outcome": "consensus"
    },
    {
      "topic": "Peer Review",
      "resolution": "DEBATE DEFENSES AND CHALLENGES:\n  [TechnicianBot] Defense: The token's extremely low trading volume relative to its market cap, coupled with an anomalous top holder concentration, indicates severe structural f\n    → Challenges SocialBot: SocialBot's higher score overestimates the token's health, as social metrics cannot compensate for t\n    → Challenges SecurityBot: SecurityBot's score is excessively high because while contract security is important, it does not mi\n  [MacroBot] Defense: My score reflects the extreme liquidity vulnerability indicated by near-zero 24h volume ($0.02) against a $2.3M market cap, which makes REPPO highly f\n    → Challenges SocialBot: SocialBot's 5.8 score is too high because strong social sentiment or narrative tailwinds cannot over\n    → Challenges SecurityBot: SecurityBot's 8.5 score is excessively high as even perfect security cannot compensate for a token's\n  [TokenomicsBot] Defense: The complete absence of reported trading volume ($0) for a token with "
    }
  ],
  "upgrade_cta": false,
  "warnings": [
    {
      "severity": "high",
      "code": "TOP10_CONCENTRATION",
      "message": "Top 10 holders concentration is very high"
    },
    {
      "severity": "medium",
      "code": "high_holder_concentration",
      "message": "high_holder_concentration"
    }
  ],
  "scan_tier": "PRO_PLUS",
  "success": true,
  "og": {
    "title": "VerdictSwarm: REPPO — Score 36/100",
    "description": "The swarm agreed REPPO ON BASE is an extremely high-risk asset, primarily due to its severe illiquidity, evidenced by $0.02 24h volume against a $2.3M market cap, making it effectively untradeable (Te",
    "url": "https://www.vswarm.io/report/0x8b978ae767588afde3ac54df778d6b01e1bc01bf"
  }
}

OPINION ONLY — NOT FINANCIAL ADVICE. This report is an automated risk assessment based on returned public data. An AVOID verdict does not accuse anyone of crimes. A CLEAR verdict does not guarantee safety. Conduct your own research.