CredScore Defensible Verdict Report
Verdict on 0xc260…7d83 ethereum
0xc2608b0136c84c12005a3394d7f3ac8176407d83
Verdict
Score
80/100
0 = maximum risk · 100 = clean
Tier
Low
Decision posture
Review
Confidence
58%
Moderate — treat as directional
Review before proceeding
Executive summary
CredScore sees a 6.4-year-old wallet with at least 501 transfers. History capped by fetch limit and Balance unavailable warrant manual review before this case is treated as routine. Observed entity context: USDT Token, tether.
Wallet snapshot at analysis time
Transfers observed: 501
Wallet age: 6.4 years (2324 days)
Last activity: 224 days ago
Unique counterparties: 134
Sanctions exposure count: 0
Mixer-like interactions: 0
Bridge-like interactions: 0
Primary risk drivers
- History capped by fetch limitmedium
- 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.
- Balance unavailablemedium
- Native balance: Unknown
Missing core metrics reduce confidence and increase the chance of misclassification.
- High transfer activitymedium
- Transfers observed: At least 501
- History cap: observed count may be a lower bound (cap 500)
Higher activity increases interpretive complexity, but should not be treated as adverse on its own unless paired with suspicious concentration, rapid routing, or sensitive exposure.
Offsetting factors considered
- Established history. Wallet age: 6.4y (observed)
- Material attribution coverage. Attributed interaction share: 100% (24% high-confidence)
- High-confidence label coverage. High-confidence attributed share: 24%
Sensitivity — what would change this verdict
- Improved transaction coverage could materially change activity-based interpretation and increase confidence.
- Fresh activity could change this classification because the current signal is not recent.
- Improved data coverage for missing core metrics would likely improve confidence and may affect the trust score.
- The dormancy-reactivation pattern warrants direct inquiry, understanding what triggered resumed activity would substantially clarify the current behavioral picture.
Observed entity / protocol context
USDT Tokentether
Analyst notes
Loading…
Analyst notes
[no analyst notes added]