B
Bitcoin Tax Rehearsal Service
4.00
Derivation Chain
Step 1
Bitcoin crash and geopolitical risks
→
Step 2
Tax postponement confusion among cryptocurrency holders in their 50s
→
Step 3
After-tax profit simulation by selling timing + health insurance premium linkage
Problem
Many office workers in their 50s purchased Bitcoin in 2020-2021, and Korea's cryptocurrency taxation has been postponed multiple times, now scheduled for implementation in 2027. Depending on whether they sell their current holdings before or after the tax takes effect, the tax difference can reach several million KRW, but few people accurately understand the cost basis calculation methods (FIFO vs. moving average) and how the basic deduction of 2.5 million KRW (approx. $1,875) applies. Since each exchange has a different format for downloading transaction history, manual calculation is very cumbersome.
Solution
Upload CSV transaction histories from major domestic exchanges (Upbit, Bithumb, Coinone) to automatically calculate cost basis under FIFO/moving average methods, compare after-tax net proceeds from selling now vs. after the tax takes effect, optimize taxes across partial sale scenarios, and display impacts on comprehensive financial income taxation and health insurance premiums.
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 (68%)
Data Availability
18.3/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 (64/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]
Data Pipeline [low]