RUG.TOOLS
Edge (EDGE)
0xed6e000def95780fb89734c07ee2ce9f6dcaf110Showing the saved report. Select Analyze Again for a new scan.
6 of 8 analysis modules returned usable evidence on Base. Some checks remain incomplete, so Rug.Tools cannot issue a complete safety-clear verdict for this token. Confirmed risk findings below still apply. Missing data is not counted as a new risk signal — and it is not evidence the token is safe either.
Required native contract evidence could not be fully verified
LP lock status could not be determined from available data
Verified below: market observation (Market provider not recorded).
Elevated Risk
Checks IncompleteThe token is actively trading, but one holder account holds 37.8% of supply, and sampled holder accounts hold 81.7% of supply, and new tokens can be minted.
Ruggy commentary
Report explanation
“The risk factors are piling on. Not a comfortable one.”
- •one holder account holds 37.8% of supply.
- •sampled holder accounts hold 81.7% — high concentration.
- •Owner can mint new supply.
Coverage note: Liquidity protection is unverified. No verified locked or burned LP position was established.
The main evidence in this report
Important signals
Controls, wallet exposure and liquiditySampled holder accounts: 81.7% · lower bound after infrastructure exclusions
No protective claim without on-chain proof
Risk findings remain visible even when other modules lack evidence. Open the full report for wallet, contract, creator and liquidity sources.
Detailed reportCheck Full DetailsWallet links, holder distribution, liquidity protection, creator activity, contract controls and source evidence.Check Full Details ↓Hide Full Details ↑
Supplemental intelligence
Provider and wallet context
GMGN intelligence
Independent token signals. The Rug.Tools verdict stays based on its own analysis.
GMGN has not returned data for this token. Your scan and verdict remain available.
Wallet Trade Context
Loading trade context separately from your scan…
Risk Snapshot
Report overviewRisk Snapshot
The most important report signals in one place. Detailed evidence stays below; this presentation does not recompute or alter the canonical Rug.Tools verdict.
Buy/sell simulation passed at the tested block, however single holder holds 37.8% of supply. Currently sits at $717.8K in liquidity, $157.0K traded in the last 24h, 20.2K holders. The largest wallet controls 37.8% of supply. The identified creator wallet holds less than 1% of supply, but total team or connected-wallet ownership is not established.
Why this verdict?▾
- + ConcernLargest Holder Accountone holder account holds 37.8% of supply.
- + ConcernSampled Holder Accountssampled holder accounts hold 81.7% — high concentration.
- + ConcernContract SecurityOwner can mint new supply.
- NeutralLiquidityLiquidity depth looks reasonable ($717,787).
- NeutralProject LifecycleProject is actively trading on-chain.
Key Findings
🟠 Elevated RiskLive Market Context
Market & trading
Live Market Context
Price, liquidity, volume, venue and trading-tax context are grouped here instead of being repeated across the report.
Market Snapshot
Market activity
Recent trades and participating wallets · Birdeye
Loaded only when requested. No background refresh.
Holders & connected wallets
Wallet intelligenceWallet & Distribution Intelligence
Current holder concentration, connected-wallet evidence and launch-window coordination are kept together so current ownership is not confused with historical launch exposure.
High Concentration. Adjusted concentration excludes identified pools and burn sinks; other custody is retained when independent control is unverified.
Connected Wallet Intelligence
Reading cached wallet relationships…
Native evidence explorer
Launch, wallet flows & liquidity custody
Inspect what was observed, which balances were measured, and what remains unverified. Timing and transfers alone do not establish common ownership or a sale.
Launch evidence
0 stored cohort rows
Receipt-level replay was not stored for this snapshot.
Current cohort balances
Unknown
Recipient cohort not recorded
Custody coverage
1 custody accounts / markets
1 without verified protection
Token custody and LP withdrawal protection are separate checks.
Creator provenance
0x11ed…392d · 0.00% current measured holdings
Attribution: rpc-creation-trace. Identified wallet only; this does not establish total team ownership.
Deployment receipt: 0xc1c9…828a
Launch timeline & receipt references
This older snapshot contains a recipient cohort, not the full receipt timeline. Counts and timing describe only the stored sample. Exact interval supply figures and transaction references remain unknown until a bounded native replay records them.
Pool-by-pool custody & protection
Pool allocation not established · reported role / market
Market selection alone does not verify LP ownership, locks or the controller of this pool.
Measured wallet balances & transfer evidence
A measured zero balance does not prove a sale. Unknown balances are not zero. Only 0 stored sample rows are listed; aggregate coverage includes missing rows.
| Recipient | Current balance | First position | Receipt references |
|---|
Source snapshot: . This evidence explorer does not independently change the Rug.Tools verdict. Existing risk findings, verification gates and source timestamps remain authoritative.
Launch activity
Launch exposure, linked wallets and current holdingsNo Coordinated Launch Signal Observed
Module severity describes launch-pattern evidence and does not replace the overall Rug.Tools verdict.
Reconstructed from ERC-20 Transfer logs in the first 5,000 blocks after deployment. Initial distribution includes pools, lockers and other protocol contracts and is not evidence of insider control. Wallet exposure counts only non-contract recipients, and wallets are reported as coordinated only when they acquired supply in the same block.
Creator intelligence
Developer intelligenceDeveloper / Creator Intelligence
Creator attribution, current holdings, external creator facts and wallet-link evidence are correlated here without changing the canonical Rug.Tools verdict.
GMGN supplemental intelligence unavailable for this token right now
Developer network could not be fully verified
Wallet-link evidence is incomplete. Missing evidence is not treated as safe.
Incomplete wallet evidence does not lower the overall risk verdict.
Why RugGraph reached this conclusion▾
- • Verified creator wallet currently holds 0.00%
0x11ed…34392d · verified attributionCoverage note: connected-wallet relationships are still loading.
Wallet relationships are one risk category. The overall Rug.Tools verdict can still be High Risk because of contract controls, trading restrictions, liquidity, holder concentration, or other evidence. A dominant holder is a concentration risk; one large wallet alone is not proof that several wallets are connected.
Presentation-only · does not independently change the Rug.Tools verdict
Liquidity & LP Protection
LiquidityLiquidity & LP Protection
Trading depth and LP ownership/lock evidence are grouped together. Liquidity depth describes trading conditions; LP protection describes whether liquidity ownership can be verified.
No LP holder or lock data was returned for this token, so liquidity protection is Unknown rather than estimated. Unverified LP is a potential signal only and is not counted as evidence of a rug on its own.
Source: On-chain LP holders
Contract & trading controls
ContractContract Controls
Direct contract and security-provider evidence. Unknown capabilities stay unknown and are never silently treated as safe.
Historical Pattern Review
Historical intelligence
Historical Pattern Review
Optional read-only comparison against archived launches and developer patterns. It never changes the Rug.Tools verdict or risk score.
Challenge this report with historical patterns
Runs only when you ask. It compares stored launch and developer patterns and may add an AI adversarial review. It never changes the Rug.Tools verdict or risk score.
Sources & coverage
Evidence quality
Analysis Coverage
Core report evidence and extended intelligence are separated so a complete core report cannot be confused with an unavailable optional launch-history module.
Core evidence coverage measures whether required report checks resolved. It is not a safety score.