B
Ethereum Tax Rehearsal
3.70
Derivation Chain
Step 1
Ethereum surge and increased cryptocurrency trading
→
Step 2
Implementation of cryptocurrency taxation
→
Step 3
Simulation of sell/hold strategies before taxation
Problem
For office workers in their 30s-40s investing in cryptocurrency, it is difficult to accurately calculate after-tax returns based on selling timing during Ethereum surges under the virtual asset taxation implemented in 2026 (22% tax rate on profits exceeding 2.5 million KRW, approx. $1,875). Manually calculating the average purchase price across multiple exchanges like Upbit and Bithumb takes over 30 minutes per transaction, and incorrect calculations can lead to tax filing errors and penalty surcharges.
Solution
A service that automatically syncs transaction histories from Upbit, Bithumb, and Binance to calculate real-time after-tax returns and provides a 'how much tax if I sell now' simulation. It includes annual profit-loss netting strategy recommendations and automatic generation of tax filing PDFs for the National Tax Service.
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 (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 (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
Backend [medium]
Frontend [low]
Data Pipeline [medium]