B
My Cryptocurrency Inheritance Scenario Planner
3.25
Derivation Chain
Step 1
Clarity Act — acceleration of crypto asset institutionalization
→
Step 2
Tax uncertainty for inheritance and gifting among crypto asset holders in their 50s
→
Step 3
Integrated scenario design for wallet access + taxes + reporting procedures during inheritance
Problem
When a crypto asset holder in their 50s wants to transfer assets to a spouse or children in preparation for sudden accidents or illness, there is no single source of information covering wallet passwords, seed phrase transfer methods, valuation for inheritance tax as of the assessment date, and inheritance application procedures that differ by exchange. It is even unclear how to report crypto assets on the National Tax Service inheritance tax return, so hiring a tax accountant costs 1-3 million KRW (approx. $750-$2,250) per case, and finding a tax accountant specializing in crypto assets is difficult.
Solution
On the web, users select their exchanges, wallet types, and asset types, and the service provides step-by-step: (1) inheritance application procedures and required document checklists by exchange, (2) inheritance tax base amount simulation (automatic calculation of valuation as of inheritance date), and (3) secure seed phrase and password transfer guides (including legally valid will templates). It compares tax scenarios based on the 2026 crypto asset taxation implementation standards.
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. |
N=.15 U=.20 M=.15 R=.30 V=.20
Feasibility (61%)
Data Availability
17.1/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 (56/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
Frontend [medium]
Backend [medium]