Verdict on 0x97a5…05af ethereum

CredScore sees a 5.2-year-old wallet with at least 501 transfers. Circular funding pattern and History capped by fetch limit are severe enough to require escalation before any further interaction.

Transfers observed: 501

Wallet age: 5.2 years (1893 days)

Last activity: 0 days ago

Unique counterparties: 80

Sanctions exposure count: 0

Mixer-like interactions: 0

Bridge-like interactions: 0

1. Circular funding patternhighWhy this driver?
   • Circular loop count: 5
   • Source return count: 9
   • Linked recirculating counterparties: 5
   • Bidirectional cluster count: 2

   Funds appear to move out and then return through a narrow set of counterparties within bounded windows. This can be consistent with circular funding, staged routing, or internal treasury cycling and should be reviewed directly.

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

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

3. Source return flow detectedmediumWhy this driver?
   • Circular loop count: 5
   • Source return count: 9
   • Linked recirculating counterparties: 5
   • Bidirectional cluster count: 2

   Observed sources later reappear as return destinations, which reduces legibility and suggests recirculating flow rather than clean one-direction settlement.

• Established history. Wallet age: 5.2y (observed)Why?
• Moderately distributed counterparties. Unique counterparties observed: 80Why?
• Recognizable exchange or protocol context. Observed label: CoW Protocol Settlement; Observed label: uniswap; Observed label: Uniswap V3 RouterWhy?

• 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.
• Off-chain context would be particularly valuable here, the detected structural patterns raise interpretive ambiguity that on-chain data alone cannot resolve.