RUG.TOOLS
rep logo
Base

rep$REP

Risk analysis for rep (REP) on Base — contract 0x3e7554f600d83ee0ef237ae6ccce63df0f59ec90. Covers liquidity, holder concentration, creator activity and available contract security signals, with unavailable checks shown as unavailable.

Rugged / Dead
Low ConfidenceRisk score 100
0x3e75…ec90 Explorer Risk report 1mo ago Market snapshot 1mo ago
Price
—
Market Cap
—
Liquidity
—
24h Volume
—
Holders
2
View risk analysis
Rug.Tools Risk Assessment
Rugged / Dead
Low confidenceScore 100
Canonical report 9953300c · v3
Scanned 2026-09-29 01:21 UTC
Red Flags · Ranked by Importance
  1. 1.CRITICAL RED FLAG · Contract Security

    Honeypot — buyers cannot sell.

    Why it matters: Restrictions on selling directly affect whether holders can exit; verify the exact tested route and observation time.

  2. 2.Historical launch exposure

    A sampled launch-window group of 482 tracked wallets reached up to 2.60% of supply.

    Why it matters: Historical exposure does not prove common wallet control, and it cannot be added to current holdings.

  3. 3.Creator wallet holdings

    The identified creator wallet has 0.00% of supply in the recorded balance observation.

    Why it matters: This measures the identified wallet only; it does not prove related-wallet holdings, creator intent, or future sales.

Reliability & unknowns

Low confidence describes evidence coverage, quality and freshness, not token safety. checks incomplete.

• Required verification checks are incomplete; category availability does not establish completed verification.

• The report evidence is stale or its observation time is invalid; confidence is limited.

• 0/482 launch-wallet balances measured; 482 remain unknown. Present group holdings are not fully measured.

LP protection: not verified. Wallet attribution and independent control require separate evidence.

Top 10 sampled holders · Not Identified
—
Creator holdings
0.00%
Liquidity
—
LP evidence
Unknown
View complete evidence Market data cannot change this canonical verdict.
Price
—
Market cap
—
Liquidity
—
24h volume
—
Holders
2
Primary pool age
—

Explore the evidence

Technical snapshot

Trading indicators and observed activity
Indexed intelligence

Technical snapshot

Market structure, order flow and published on-chain evidence from one chain-specific snapshot.

Stale · 45623m
Liquidity / market cap
Unavailable

Available depth relative to valuation

24h turnover
Unavailable

24h volume divided by liquidity

Buy flow · 24h
Unavailable

Transaction split unavailable

Momentum alignment
0/3 available

Across 1h, 6h and 24h returns

Return windowsPrice performance
1 hour
—
6 hours
—
24 hours
—
Evidence sets
5/5
Pool age
—
Top holder
—
Top 10
—
How to read these technicals

Turnover measures trading activity against available liquidity. High turnover can also mean volatility.

Momentum alignment compares overlapping return windows. It is context, not independent confirmation or a safety score.

Holder concentration uses the published report’s classified holder evidence when available.

Freshness is the age of Rug.Tools’ indexed market snapshot, separate from the report scan time.

Price chart

Price chart

Price chart

Open on DexScreener ↗

Load verified candle history to explore price and volume directly in this report.

What is rep?

What is rep?

rep ($REP) is a ERC-20 token on the Base blockchain. It currently has 2 on-chain holders. Rug.Tools' current assessment of rep is "Rugged / Dead", based on live on-chain signals including holder concentration, liquidity depth, creator wallet history and contract permissions.

Rug.Tools signals

Rug.Tools signals

Creator Trust
—
Solana only
Creator Holdings
0.00%
Of total supply
Contract
Unverified
Honeypot flag ⚠
Liquidity
—

Key statistics

Key statistics

Price
—
Market Cap
—
FDV
—
Liquidity
—
24h Volume
—
Holders
2
Primary pool age
—
Top Holder
—
Top 10 Holders
—
Total Supply
—
Primary DEX
—
Chain
Base

Launch activity

Native receipt, wallet and liquidity custody evidence

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.

base
Investigate creator trades & token transfers

Forensic intelligence / Activity

What did the developer actually do?

Separate current holdings, historical launch exposure, verified sales and token transfers. Follow the receipts before drawing conclusions.

Trade history unavailable
Creator holdings
0.00%

Saved balance measurement; separate from sale history

Historical launch exposure
2.60%

Observed launch-group share of total token supply; not every graph node, developer sales or present insider ownership

Developer sales: Insufficient Evidence · Trading integrity: Not Scored. A creator holding 0% does not establish whether tokens were sold or transferred.

Launch evidence

60 stored cohort rows

Partial evidence

Receipt-level replay was not stored for this snapshot.

Current cohort balances

Unknown

0/482 wallets measured · 482 unknown

Custody coverage

0 custody accounts / markets

0 without verified protection

Token custody and LP withdrawal protection are separate checks.

Creator provenance

0xe8ff…0f76 · 0.00% current measured holdings

Attribution: alchemy-transfer. Identified wallet only; this does not establish total team ownership.

Deployment receipt: 0x26c1…94c2

Launch timeline & receipt references
First 10 recipients: 517 blocks
First 20 recipients: 872 blocks
First 10 elapsed: Unknown

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

No position-level custody evidence is stored. This does not establish that liquidity is absent or protected.

Measured wallet balances & transfer evidence

A measured zero balance does not prove a sale. Unknown balances are not zero. Only 40 stored sample rows are listed; aggregate coverage includes missing rows.

RecipientCurrent balanceFirst positionReceipt references
0x3de5…0f78Unknown#51,511,210Not stored
0x527e…f8ecUnknown#51,513,161Not stored
0xe720…a50aUnknown#51,513,121Not stored
0x490d…a3faUnknown#51,513,150Not stored
0x59cf…76ffUnknown#51,511,280Not stored
0x5d35…ef4bUnknown#51,513,161Not stored
0xdea4…ca1eUnknown#51,513,175Not stored
0xe09b…92d9Unknown#51,513,106Not stored
0x869f…ec60Unknown#51,513,132Not stored
0xe7e2…58e6Unknown#51,513,168Not stored
0xcfd4…e1deUnknown#51,513,161Not stored
0xdf9a…1ed2Unknown#51,513,065Not stored
0xc43a…eef8Unknown#51,512,580Not stored
0x906d…c73fUnknown#51,512,777Not stored
0xe4c0…2198Unknown#51,512,017Not stored
0x8e41…3944Unknown#51,512,427Not stored
0x58c2…1ccaUnknown#51,511,540Not stored
0x14f2…f4e3Unknown#51,511,576Not stored
0x800e…bfa9Unknown#51,512,534Not stored
0x3c62…9076Unknown#51,512,502Not stored
0x8387…f466Unknown#51,511,493Not stored
0xa8db…3616Unknown#51,513,129Not stored
0xc1ef…238aUnknown#51,512,280Not stored
0xb0c0…978bUnknown#51,511,980Not stored
0x31a2…f66fUnknown#51,512,159Not stored
0x9587…fa03Unknown#51,512,462Not stored
0x56c3…e80aUnknown#51,512,654Not stored
0x77af…028eUnknown#51,512,676Not stored
0x860f…1170Unknown#51,511,748Not stored
0x8a06…1cadUnknown#51,511,582Not stored
0xf2fc…15ddUnknown#51,513,033Not stored
0x8393…4062Unknown#51,513,095Not stored
0xb1f8…e1c7Unknown#51,511,970Not stored
0xe873…d968Unknown#51,512,082Not stored
0xa8a4…5ce5Unknown#51,512,808Not stored
0xd9db…bdf0Unknown#51,512,598Not stored
0x12ba…ae19Unknown#51,512,521Not stored
0x1a1c…cd41Unknown#51,512,990Not stored
0x1305…767bUnknown#51,511,772Not stored
0x1121…1630Unknown#51,512,089Not stored

Source snapshot: . This evidence explorer does not independently change the Rug.Tools verdict. Existing risk findings, verification gates and source timestamps remain authoritative.

1Choose a wallet
2Inspect its transactions
3Trace its funding
Historical launch-group exposure
2.60% historical
Wallet coverage
458 outside this sample
Creator history
0 balance snapshots
Evidence status
Partial launch history

01 / Launch activity

Select a wallet to see its activity near token launch. Early receipt of tokens alone does not prove a sniper purchase.

LAUNCHreceipt sampleCREATOR0xe8f…0f76EARLY0x3de…0f78EARLY0x527…f8ecEARLY0xe72…a50aEARLY0x490…a3faEARLY0x59c…76ffEARLY0x5d3…ef4bEARLY0xdea…ca1eEARLY0xe09…92d9EARLY0x869…ec60EARLY0xe7e…58e6EARLY0xcfd…e1de

Cyan: tokens received · Amber: tokens moved out · Dashed: deployment. Lines connect wallets to the launch sample; they do not identify who sent the tokens. The first 12 wallets are plotted; every listed wallet can be inspected below.

Selected wallet

0xe8ffec1927ffeee0a780b5a2395d9eefbbb00f76

Creator attribution

Balance at last observation

Unknown

Time unavailable · observation, not a live balance

Supporting transactions (1)

02 / Funding connections

Where did the funding come from?

Follow verified transfers back up to three wallets. Select any connected wallet to explore its evidence.

Evidence first. Ownership stays unproven.

A transfer proves funds moved between addresses. It does not prove they belong to the same person. Known exchange, bridge and pool accounts are marked as infrastructure.

How to read this evidence

Arrows show receipt references associated with the launch sample. They do not identify transfer counterparties or establish common ownership.

An early recipient is not necessarily a buyer or sniper. Outflows may be transfers; these summaries do not establish realized sales.

Balance measurements retain their original timestamps. Historical launch exposure is separate from present holdings.

Funding paths, verified swap activity and volume manipulation require additional transaction evidence. Missing history is unknown.

Source snapshot: 2026-09-29 01:21:35 UTC · Funding research runs only when requested.

Rug.Tools analysis

Rug.Tools analysis

Ruggy verdict
Rugged / Dead
Low confidence

The contract behaves like a honeypot — buyers cannot exit. Do not trade.

Verdict from canonical snapshot 9953300c · v3 · scanned 2026-09-29 01:21 UTC · page content updated 2026-09-29 01:21 UTC

Holder distribution

Holder distribution

Total holders
2
Everyone else
100.00%

Creator profile

Creator profile

Creator wallet
0xe8ffec1927ffeee0a780b5a2395d9eefbbb00f76
View wallet
Trust Score
—
Holdings
0.00%
Projects
—
Active
—
Inactive
—
High Risk
—

Full creator history is currently Solana-only. Multi-chain creator profiles are coming soon.

Token activity

Token activity

  1. 2026-09-29 01:21 UTC
    Rug.Tools analyzed this token
    Fresh on-chain snapshot captured.

Similar tokens

Similar tokens

Compared using stored market cap, launch age and trading venue. Similarity is not a safety rating.

Finding comparable tokens…

Learn more

Frequently asked questions

Frequently asked questions

What is rep?⌄

rep is a Base token analyzed by Rug.Tools using public on-chain data — holders, liquidity, creator wallet activity and contract security signals. This page shows the latest cached analysis and refreshes automatically.

Is rep safe?⌄

Current Rug.Tools verdict: Rugged / Dead. The contract behaves like a honeypot — buyers cannot exit. Do not trade. No token can be guaranteed safe: verdicts summarize on-chain risk signals only and cannot detect off-chain intent. Always do your own research.

How many holders does rep have?⌄

Rug.Tools currently sees 2 holders. The largest holder account holds — of supply; the top 10 holder accounts together hold —. These balances alone do not establish individual ownership or independent control.

Where is rep traded?⌄

Rug.Tools has not yet detected an active trading pair for this token on Base. Liquidity may be very low or the pool may have moved.

How often does this page update?⌄

This page renders from cached data in our database. It refreshes when a new scan runs — either on a scheduled background sync or when a user clicks Refresh above. Opening this page does not trigger a new scan.

Optional Forensic Review

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.