LAYER 0 · PRE-TRADE RISK REPORTSETTLED 2026-04-18 21:57:11.948Z

UNSETTLED

50/100

GRADE D

River (RIVER) is a base token with $121.5M market cap, 15 days old. The Swarm found significant market cap ($121.5M). Key concerns: tokenomics concerns. Overall verdict: D — high risk — significant concerns identified.

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
$781.30

HARD BLOCKERS

  • 24h volume/liquidity ratio is 168.81:1 — elevated wash-trading/manipulation risk

HOLDER CLUSTERS

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

2 RETURNED CHECKS

CATEGORYCHECKFINDINGRESULT
securityCLOSED_SOURCEContract is not open sourcemedium
securityVOL_LIQ_RATIO24h volume/liquidity ratio is 168.81:1 — elevated wash-trading/manipulation riskcritical

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 5.0/10 while Safety scored 7.5/10. This 2.5-point gap suggests the token's strengths in Safety may not translate to Technical reliability.

[Technician]noted

This conflict matters because SafetyBot's positive assessment primarily covers contract security and market legitimacy, indicating a lower risk of direct technical exploits or scams. However, TechnicianBot's negative score highlights critical on-chain vulnerabilities like poor distribution and thin DEX liquidity, which can lead to price manipulation, poor trading experience, and an unstable ecosystem despite the token's apparent security and exchange listings.

[Devil's Advocate]challenge

⚔️ SecurityBot's optimism ignores the critical centralization risk of 'owner's control over cross-chain' LayerZero configuration, especially for a mere 15-day-old omnichain token. This significant trust assumption, explicitly stated, is glossed over despite the potential for bridge exploits or re-routing that could devastate token integrity.

[Security]defend

The Devil's Advocate correctly identifies LayerZero configuration control as a centralization risk. However, the 7.5 score is justified because the owner *cannot* mint new tokens, pause transfers, or implement fees, safeguarding the token's supply and core utility. The owner's control is limited to cross-chain routing, a necessary function for an OFT, and while a trust assumption, it doesn't compromise the token's fundamental integrity or supply on its native chain.

[Devil's Advocate]escalate

⚔️ While the owner cannot mint or pause, their 'limited control over cross-chain routing' is precisely the attack vector for an OFT, enabling rerouting to malicious contracts or arbitrary message execution that devastates token integrity, regardless of supply immutability. This fundamental trust assumption, especially for a nascent 15-day-old token, presents a disproportionately high risk that a 7.5 security score fails to adequately reflect.

[Security]compromise

The Devil's Advocate correctly identified that the owner's 'limited control over cross-chain routing' in an OFT creates a critical attack vector for rerouting tokens to malicious contracts or arbitrary message execution, fundamentally compromising token integrity despite supply immutability.

[swarm]resolution

Consensus after 1 round(s), σ=0.99

[swarm]resolution

DEBATE DEFENSES AND CHALLENGES: [TokenomicsBot] Defense: The token exhibits a healthy distribution with the top 10 holders controlling only 1.0% of the supply, indicating decentralization and reduced manipul → Challenges MacroBot: MacroBot's score is too low; the token's excellent distribution metrics and reasonable FDV/MCAP rati [SocialBot] Defense: Despite recent price volatility and liquidation events, River Protocol maintains a moderate social health, evidenced by its established and verified T → Challenges MacroBot: MacroBot's score is significantly too low, as my analysis shows a well-established social presence a [TechnicianBot] Defense: While River Protocol exhibits a strong exchange presence and a verified contract, the lack of reliable on-chain holder data and thin DEX liquidity are → Challenges SecurityBot: SecurityBot's score is too high because despite a verified contract, the absence of transparent on-c [SecurityBot] Defense: River Protocol, despite it

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-18 21:57:11.948Z
Model set
Not returned for this report.
RECEIPT LINK UNAVAILABLEOPEN PUBLIC LEDGER →

RAW REPORT PAYLOAD

{
  "address": "0xda7ad9dea9397cffddae2f8a052b82f1484252b3",
  "chain": "base",
  "depth": "full",
  "tier": "FREE",
  "score": 49.6,
  "grade": "D",
  "risk_level": "HIGH",
  "flags": [],
  "free_tier_result": {
    "verdict": "UNHEALTHY",
    "reason": "This token exhibits an extremely unhealthy liquidity profile, with a $121.5M market cap supported by only $104K in liquidity, indicating a high risk of price manipulation and inability to sell.",
    "label": "AI Verdict",
    "checks": {
      "contract_verified": true,
      "token_age_days": 15,
      "liquidity_usd": 104173.9,
      "holder_count": 39,
      "has_liquidity_pool": true,
      "chain": "base"
    },
    "risk_level": "critical",
    "key_findings": [
      "Market Cap ($121.5M) is disproportionately high compared to Liquidity ($104K), resulting in a liquidity-to-market-cap ratio of 0.000085%, which is extremely unhealthy and indicates severe illiquidity.",
      "Total Holders (39) is extremely low for a token with a $121.5M market cap, suggesting a highly concentrated ownership despite the reported 'Top 10 Concentration' of 1.0% (this discrepancy needs further investigation, but the low holder count itself is a major red flag).",
      "Token Age (15 days) is very young, and combined with the other factors, points to a potentially manipulated or illiquid asset.",
      "Lack of social presence and clear identity for a token with a significant market cap is concerning.",
      "Mint and Freeze authorities are revoked, which is positive, but overshadowed by liquidity and holder issues."
    ],
    "confidence": 0.95
  },
  "goplus": {
    "source": "goplus",
    "api_available": true,
    "goplus_available": true,
    "goplus_status_message": null,
    "is_mintable": null,
    "is_honeypot": null,
    "holder_count": 39,
    "lp_holder_count": 1,
    "top_10_holder_rate": 0.01,
    "top10_holders_pct": 1,
    "is_open_source": false,
    "is_proxy": null,
    "lp_burned_or_locked": null,
    "security_findings": [
      {
        "source": "goplus",
        "code": "CLOSED_SOURCE",
        "severity": "medium",
        "message": "Contract is not open source",
        "value": false
      }
    ]
  },
  "security_findings": [
    {
      "source": "goplus",
      "code": "CLOSED_SOURCE",
      "severity": "medium",
      "message": "Contract is not open source",
      "value": false
    },
    {
      "source": "verdictswarm",
      "code": "VOL_LIQ_RATIO",
      "severity": "critical",
      "message": "24h volume/liquidity ratio is 168.81:1 — elevated wash-trading/manipulation risk",
      "value": 168.81,
      "metric": {
        "name": "vol_liq_ratio",
        "display_name": "Volume/Liquidity Ratio",
        "value": 168.81,
        "unit": "x",
        "volume_24h": 17586062,
        "liquidity_usd": 104173.9,
        "threshold_high": 10,
        "threshold_critical": 20
      }
    }
  ],
  "scanned_at": "2026-04-18T21:57:11.948678Z",
  "cached": false,
  "cached_at": null,
  "liquidity_exposure_cap_usd": 781.3,
  "summary": "River (RIVER) is a base token with $121.5M market cap, 15 days old. The Swarm found significant market cap ($121.5M).  Key concerns: tokenomics concerns. Overall verdict: D — high risk — significant concerns identified.",
  "token": {
    "vol_liq_ratio": 168.81,
    "name": "River",
    "symbol": "RIVER",
    "chain": "base",
    "price_usd": 6.2,
    "mcap": 121460412,
    "market_cap": 121460412,
    "volume_24h": 17586062,
    "liquidity_usd": 104173.9,
    "contract_age_days": 15,
    "contract_verified": true,
    "holder_count": 39,
    "top10_holders_pct": 1,
    "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": "unlocked",
    "lp_locked_pct": 0,
    "lp_burned_pct": 0,
    "lp_unlocked_pct": 100,
    "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": 5,
      "sentiment": "neutral",
      "category": "Technical",
      "reasoning": {
        "summary": "AI on-chain (GPT-4o Mini); River Protocol shows signs of a young token with significant exchange presence but lacks reliable on-chain holder data, which raises concerns about distribution quality. The trading activity is relatively active, but the liquidity on DEXs is thin, indicating potential fragility in execution quality.",
        "positives": [
          "Verified contract enhances trustworthiness",
          "Strong exchange presence with 26 listings, indicating good market access",
          "Decent transaction count (481 in 24h) suggests active trading"
        ],
        "concerns": [
          "Holder count of 39 is likely incomplete, suggesting a lack of distribution data",
          "Top 10 holders concentration is unknown, raising concerns about centralization",
          "Thin DEX liquidity ($27,622.90) compared to total volume indicates fragility",
          "confidence 0.50"
        ],
        "flags": []
      },
      "confidence": 0.5
    },
    "DevilsAdvocate": {
      "score": 6.5,
      "sentiment": "bullish",
      "category": "Contrarian",
      "reasoning": {
        "summary": "AI contrarian (Gemini 2.5 Flash) [NEUTRAL contrarian]; Despite API limitations skewing on-chain metrics, River Protocol demonstrates strong market traction for a young token, evidenced by its listing on numerous major exchanges and substantial daily trading volume. The 'established project' status and verified contract provide a baseline of legitimacy. While the 'unknown' mint authority is a lingering risk, the overall market activity suggests a project with significant early adoption and potential, warranting a more bullish outlook than the current neutral consensus.; risks: Mint authority status is 'unknown', posing a potential risk of unlimited token creation if not renounced., True on-chain holder distribution and concentration are unknown due to API limitations, obscuring potential centralization., Reliance on CEX liquidity means on-chain liquidity ($104k) is very low, making it vulnerable to large sells if CEX liquidity dries up or is not deep., Project's long-term viability and ability to deliver on 'chain abstraction' utility are unproven at 15 days old., Risk-off market conditions could disproportionately impact newer, utility-focused tokens if broader sentiment remains negative.; open questions: Actual holder count and distribution beyond the API-limited on-chain data., Whether the mint authority has been renounced or is still active., The depth and stability of liquidity on the 26 listed centralized exchanges.; confidence 0.85",
        "positives": [],
        "concerns": [],
        "flags": []
      },
      "confidence": 0.85
    },
    "MacroBot": {
      "score": 3.8,
      "sentiment": "bearish",
      "category": "Macro",
      "reasoning": {
        "summary": "AI macro (Grok); River (RIVER) is highly fragile in the current risk-off regime, with razor-thin DEX liquidity ($104K) versus $121M MCAP exposing it to outsized drawdowns despite decent CEX volume ($17.5M, 14% vol/mcap). Chain abstraction on Base has narrative appeal and rapid listings (26 exchanges incl. Kraken/Bitget), but -19% 24h/-33% 7d lags BTC/ETH (-2/-3%) and signals high beta vulnerability without offsetting catalysts. Young age limits track record, but liquidity mismatch screams illiquidity risk over any sector resilience.; drivers: Rapid CEX listings (26 incl. majors) provide some volume access for young token, Chain abstraction narrative ties to Base ecosystem growth potential, Vol/mcap ~0.14x validates real trading interest despite risk-off; risks: Extreme liquidity vulnerability ($104K pool on $121M MCAP) in risk-off fear (FGI 26), High BTC/ETH beta evident in -19% 24h vs BTC -2%, prone to amplified downside, Tiny FDV ($423K) implies massive dilution risk if unlocks hit; confidence 0.55",
        "positives": [],
        "concerns": [],
        "flags": []
      },
      "confidence": 0.55
    },
    "SecurityBot": {
      "score": 6.5,
      "sentiment": "bullish",
      "category": "Safety",
      "reasoning": {
        "summary": "AI security (Claude Sonnet 4.5); River Protocol is a 15-day-old LayerZero OFT (Omnichain Fungible Token) with verified source code, $121M market cap, and listings on 26 exchanges including Kraken and Bitget. The contract implements a one-time initialization pattern that mints the entire 100M supply to specified recipients, after which no further minting is possible. The owner retains LayerZero configuration privileges (endpoint delegation, peer management) but cannot mint additional tokens, pause transfers, or implement fees. The primary trust assumption is the owner's control over cross-chain routing configuration. Liquidity is concerningly low ($104K) relative to market cap, and 100% is unlocked, creating material exit risk. The token's rapid exchange adoption and high reported volume ($17.6M/24h) against minimal on-chain liquidity suggests most trading occurs on centralized venues. For a 15-day-old token, the security posture is above average due to fixed supply and verified code, but the liquidity structure and owner privileges prevent a higher score.; risks: Owner retains LayerZero endpoint configuration control: can modify cross-chain peers, delegates, and messaging parameters, creating potential for cross-chain routing manipulation or fund diversion on non-native chains, Extreme liquidity risk: only $104K liquidity against $121M market cap (0.09% ratio) with 100% unlocked LP creates severe exit vulnerability and price manipulation exposure, Centralized exchange dependency: $17.6M reported daily volume with minimal on-chain liquidity indicates trading is concentrated on CEX venues, exposing holders to exchange counterparty risk and potential delisting impact, Young contract age (15 days) with no operating history: insufficient time to validate owner behavior, cross-chain bridge stability, or response to market stress events; confidence 0.72",
        "positives": [],
        "concerns": [],
        "flags": []
      },
      "confidence": 0.72
    },
    "TokenomicsBot": {
      "score": 4,
      "sentiment": "bullish",
      "category": "Tokenomics",
      "reasoning": {
        "summary": "Tokenomics checks; healthy distribution (top10 1.0%); FDV/MCAP reasonable (0.00x); AI unavailable (AIProviderCallError)",
        "positives": [],
        "concerns": [],
        "flags": []
      },
      "confidence": 0.4
    },
    "SocialBot": {
      "score": 5.5,
      "sentiment": "neutral",
      "category": "Social",
      "reasoning": {
        "summary": "X/Twitter sentiment (Grok); sub-scores: OE=5.0, IQ=4.0, CG=7.0, BSD=6.0; ⚠️ BREAKING: 5% bearish plunge and volume spike on $RIVER; $139k long liquidation on Bybit; Aggressive buying at $7.3-$7.5 support on Hyperliquid amid S4 campaigns; River Protocol ($RIVER) shows moderate social health for a young token with an established official Twitter (@RiverdotInc, 199k followers, verified) and strong Telegram presence (44k users per CoinGecko). Recent X discussions focus on price dumps, accumulation at supports, and ongoing trading competitions/points farming on Hyperliquid. Positive CoinGecko sentiment (93.75%) contrasts short-term bearish trading chatter amid risk-off market. Fake support accounts indicate impersonation risk, but no heavy bot spam. Sparse live data limits depth.; narratives: Post-dump accumulation and stabilization, Chain abstraction for liquidity unification, Trading competitions and points farming for multipliers; fake/coordination risk: 4/100; confidence 0.65",
        "positives": [],
        "concerns": [],
        "flags": []
      },
      "confidence": 0.65
    }
  },
  "consensus_narrative": "The swarm agreed River is a young token with strong exchange presence and a verified contract, yet its D grade reflects significant fragility. TechnicianBot and MacroBot highlighted critical issues like razor-thin DEX liquidity ($104K vs $121M MCAP) and poor on-chain distribution, exposing it to high volatility despite SecurityBot's positive assessment of contract safety. The final grade signifies a project with early market traction but substantial structural risks. Exercise extreme caution due to liquidity and distribution concerns.",
  "debates": [
    {
      "topic": "Safety vs Technical",
      "resolution": "This conflict matters because SafetyBot's positive assessment primarily covers contract security and market legitimacy, indicating a lower risk of direct technical exploits or scams. However, TechnicianBot's negative score highlights critical on-chain vulnerabilities like poor distribution and thin DEX liquidity, which can lead to price manipulation, poor trading experience, and an unstable ecosystem despite the token's apparent security and exchange listings.",
      "outcome": "noted",
      "rounds": [
        {
          "phase": "challenge",
          "agent": "TechnicianBot",
          "agentName": "Technician",
          "target": "SecurityBot",
          "targetName": "Security",
          "content": "Cross-category conflict: Technical scored 5.0/10 while Safety scored 7.5/10. This 2.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 matters because SafetyBot's positive assessment primarily covers contract security and market legitimacy, indicating a lower risk of direct technical exploits or scams. However, TechnicianBot's negative score highlights critical on-chain vulnerabilities like poor distribution and thin DEX liquidity, which can lead to price manipulation, poor trading experience, and an unstable ecosystem despite the token's apparent security and exchange listings.",
          "round": 2,
          "stance": "noted"
        }
      ]
    },
    {
      "topic": "Devil's Advocate vs SecurityBot",
      "resolution": "Compromise: 7.5 → 7.0",
      "outcome": "compromise",
      "rounds": [
        {
          "phase": "challenge",
          "agent": "DevilsAdvocate",
          "agentName": "Devil's Advocate",
          "target": "SecurityBot",
          "targetName": "Security",
          "content": "⚔️ SecurityBot's optimism ignores the critical centralization risk of 'owner's control over cross-chain' LayerZero configuration, especially for a mere 15-day-old omnichain token. This significant trust assumption, explicitly stated, is glossed over despite the potential for bridge exploits or re-routing that could devastate token integrity.",
          "round": 1,
          "stance": "challenge"
        },
        {
          "phase": "defense",
          "agent": "SecurityBot",
          "agentName": "Security",
          "target": "DevilsAdvocate",
          "targetName": "Devil's Advocate",
          "content": "The Devil's Advocate correctly identifies LayerZero configuration control as a centralization risk. However, the 7.5 score is justified because the owner *cannot* mint new tokens, pause transfers, or implement fees, safeguarding the token's supply and core utility. The owner's control is limited to cross-chain routing, a necessary function for an OFT, and while a trust assumption, it doesn't compromise the token's fundamental integrity or supply on its native chain.",
          "round": 2,
          "stance": "defend"
        },
        {
          "phase": "rebuttal",
          "agent": "DevilsAdvocate",
          "agentName": "Devil's Advocate",
          "target": "SecurityBot",
          "targetName": "Security",
          "content": "⚔️ While the owner cannot mint or pause, their 'limited control over cross-chain routing' is precisely the attack vector for an OFT, enabling rerouting to malicious contracts or arbitrary message execution that devastates token integrity, regardless of supply immutability. This fundamental trust assumption, especially for a nascent 15-day-old token, presents a disproportionately high risk that a 7.5 security score fails to adequately reflect.",
          "round": 3,
          "stance": "escalate"
        },
        {
          "phase": "resolution",
          "agent": "SecurityBot",
          "agentName": "Security",
          "content": "The Devil's Advocate correctly identified that the owner's 'limited control over cross-chain routing' in an OFT creates a critical attack vector for rerouting tokens to malicious contracts or arbitrary message execution, fundamentally compromising token integrity despite supply immutability.",
          "round": 4,
          "stance": "compromise"
        }
      ]
    },
    {
      "topic": "Score Calibration",
      "resolution": "Consensus after 1 round(s), σ=0.99",
      "outcome": "consensus"
    },
    {
      "topic": "Peer Review",
      "resolution": "DEBATE DEFENSES AND CHALLENGES:\n  [TokenomicsBot] Defense: The token exhibits a healthy distribution with the top 10 holders controlling only 1.0% of the supply, indicating decentralization and reduced manipul\n    → Challenges MacroBot: MacroBot's score is too low; the token's excellent distribution metrics and reasonable FDV/MCAP rati\n  [SocialBot] Defense: Despite recent price volatility and liquidation events, River Protocol maintains a moderate social health, evidenced by its established and verified T\n    → Challenges MacroBot: MacroBot's score is significantly too low, as my analysis shows a well-established social presence a\n  [TechnicianBot] Defense: While River Protocol exhibits a strong exchange presence and a verified contract, the lack of reliable on-chain holder data and thin DEX liquidity are\n    → Challenges SecurityBot: SecurityBot's score is too high because despite a verified contract, the absence of transparent on-c\n  [SecurityBot] Defense: River Protocol, despite it"
    }
  ],
  "upgrade_cta": false,
  "warnings": [
    {
      "severity": "critical",
      "code": "VOL_LIQ_RATIO",
      "message": "24h volume/liquidity ratio is 168.81:1 — elevated wash-trading/manipulation risk"
    },
    {
      "severity": "medium",
      "code": "CLOSED_SOURCE",
      "message": "Contract is not open source"
    }
  ],
  "scan_tier": "PRO_PLUS",
  "success": true,
  "og": {
    "title": "VerdictSwarm: RIVER — Score 50/100",
    "description": "The swarm agreed River is a young token with strong exchange presence and a verified contract, yet its D grade reflects significant fragility. TechnicianBot and MacroBot highlighted critical issues li",
    "url": "https://www.vswarm.io/report/0xda7ad9dea9397cffddae2f8a052b82f1484252b3"
  }
}

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.