Verdict on 0x2767…f482 ethereum

CredScore sees a 2-month-old wallet with at least 61 transfers. History capped by fetch limit and Repeated amount-band recirculation warrant manual review before this case is treated as routine. Observed entity context: USDT Token, 1inch Router.

Transfers observed: 61

Wallet age: 0.2 years (63 days)

Last activity: 17 days ago

Unique counterparties: 39

Sanctions exposure count: 0

Mixer-like interactions: 0

Bridge-like interactions: 0

1. History capped by fetch limitmediumWhy this driver?
   • Transfers observed: At least 61
   • History cap: observed count may be a lower bound (cap 500)

   Incomplete transfer coverage reduces confidence because observed totals may be lower bounds.

2. Repeated amount-band recirculationmediumWhy this driver?
   • Source return count: 1
   • Repeated amount-band recirculation: 2
   • Funding dependency concentration: 28%
   • Multi-hop pressure: 6/100

   Repeated reuse of the same transfer size bands across a narrow routing set can indicate mechanical flow or recirculation rather than broad organic usage.

3. Balance unavailablemediumWhy this driver?
   • Native balance: Unknown

   Missing core metrics reduce confidence and increase the chance of misclassification.

• Moderately distributed counterparties. Unique counterparties observed: 39Why?
• Material attribution coverage. Attributed interaction share: 100% (13% high-confidence)Why?
• Recognizable exchange or protocol context. Observed label: USDT Token; Observed label: 1inch Router; Observed label: 1inchWhy?

• Improved transaction coverage could materially change activity-based interpretation and increase confidence.
• Improved data coverage for missing core metrics would likely improve confidence and may affect the trust score.