Risk scores
Ospree’s Blockchain Analytics provides powerful tools to assess and manage compliance risks by analyzing wallet addresses and transactions. Risk scores are central to this process, helping you identify and mitigate potential threats efficiently.
How risk scores are calculated
Ospree’s risk scoring algorithm evaluates several key factors:
Transaction Patterns: Analyzes the frequency, volume, and destination of transactions. Unusual patterns can indicate illicit activity.
Counterparty Risk: Assesses the risk level of counterparties involved in transactions, including connections to sanctioned or high-risk entities.
Wallet Reputation: Evaluates the history of the wallet address, including past associations with darknet markets, scams, or fraud.
Geolocation Data: Considers jurisdictional risks based on the origin and destination countries of transactions.
Behavioral Analysis: Looks at behavioral anomalies, such as sudden spikes in transaction volume or activity.
Ospree uses advanced algorithms and blockchain intelligence to aggregate these factors into a comprehensive risk score.
Understanding risk score levels
Ospree categorizes risk scores into three levels, providing a clear overview of compliance risk:

Low Risk (Green): Safe transaction patterns and trustworthy counterparties. No further action required.
Medium Risk (Yellow/Orange): Potentially risky behavior or associations. Further review is recommended.
High Risk (Red): High likelihood of suspicious activity or compliance violations. Immediate action is required.
The risk level is displayed using color-coded bars on the dashboard, enabling quick visual identification.
Using risk scores in Ospree
Screening Wallet Addresses: Enter wallet addresses in the Blockchain Analytics search bar to receive a risk score and detailed analysis.
Monitoring Transactions: Continuously monitor transactions in real-time, receiving alerts when risk levels change.
Decision-Making: Use risk scores to determine the need for enhanced due diligence, reporting, or transaction blocking.
Last updated