B
Crypto Sanctions Screener
3.15
Derivation Chain
Step 1
Binance Iran sanctions violation firing incident
→
Step 2
Growing sanctions compliance demand at crypto exchanges
→
Step 3
Sanctions screening automation SaaS for small-to-mid-size exchanges/fintechs
Problem
Korean Virtual Asset Service Providers (VASPs), required by the Special Financial Transactions Act to perform sanctions screening, must manually cross-reference OFAC/UN/EU sanctions lists. Global sanctions lists are updated 2-3 times per week, and mid-size exchanges processing 10,000+ transactions per month need 1-2 dedicated staff. Non-compliance risks business suspension and penalties.
Solution
When cryptocurrency wallet addresses and transaction records are connected via API, the system: (1) performs real-time matching against OFAC/UN/EU/Korea Financial Services Commission sanctions lists, (2) detects indirectly connected (2-hop) risky addresses through blockchain on-chain analysis, (3) auto-generates STR (Suspicious Transaction Report) drafts compliant with the Special Financial Transactions Act. Auto-rescans and alerts when sanctions lists are updated.
NUMR-V Scores
NUMR-V Scoring System
| N Novelty | 1-5 | How uncommon the service is in market context. |
| U Urgency | 1-5 | How urgently users need this problem solved now. |
| M Market | 1-5 | Market size and growth potential from proxy indicators. |
| R Realizability | 1-5 | Buildability for a small team with realistic constraints. |
| V Validation | 1-5 | Validation signal quality from competition and demand data. |
SaaS N=.15 U=.20 M=.15 R=.30 V=.20
Senior N=.25 U=.25 M=.05 R=.30 V=.15
Feasibility (64%)
Data Availability
15.0/25
Feasibility Breakdown
| Tech Complexity | / 40 | Difficulty of core implementation stack. |
| Data Availability | / 25 | Practical availability and cost of required data. |
| MVP Timeline | / 20 | Expected time to ship a usable MVP. |
| API Bonus | / 15 | Bonus for viable public API leverage. |
Market Validation (58/100)
Validation Breakdown
| Competition | / 20 | Signal quality from competitor landscape. |
| Market Demand | / 20 | Demand proxies from search and mention patterns. |
| Timing | / 20 | Fit with current shifts in tech, behavior, and regulation. |
| Revenue Signals | / 15 | Reference evidence for monetization viability. |
| Pick-Axe Fit | / 15 | How well the concept serves participants in a trend. |
| Solo Buildability | / 10 | Practicality for lean-team implementation. |
Technical Requirements
Data Pipeline [medium]
Backend [medium]
Frontend [low]