← Back to project list
Research Prototype · Data Pipeline
PrototypeKimchi Premium Threshold Strategy Validation Pipeline
I explored buy and sell thresholds using hourly price data, compared performance metrics, and extended the work into a pipeline that updates data hourly.
- Company
- Algorith Capital
- Service
- Kimchi Premium Research
- Period
- 2024.08–2024.11 · 4 months
- Role
- Backend / Data Prototype
- Responsibility
- Research · Backtest · Data Pipeline
- Team
- Solo
- Python
- pandas
- Jupyter
- Excel
- Google Drive API
- Bithumb · Yahoo Finance
Ownership
My direct responsibilities
- Documented the threshold-strategy hypothesis and experimental procedure based on fluctuations in the kimchi premium
- Cleaned hourly exchange-rate, BTC, and USDT price data for 2021–2024 and verified the kimchi premium (KPR) formula
- Calculated profit and loss for buy/sell threshold combinations, generated heatmaps, and compared risk-adjusted returns, gain-to-loss ratios, and buy-and-hold performance
- Automated hourly price updates using Yahoo Finance and Bithumb data, with uploads to Google Drive
- Implemented an Excel-based trading log structure separating funds, wallets, orders, and executions by strategy
Constraints
Constraints to address first
- Even for the same strategy, favorable thresholds varied by validation period, so a single result could not be generalized.
- I needed to align time zones and missing intervals in the price data and compare the results of the existing kimchi premium formula with a simplified formula.
- Backtest returns could differ from actual execution results because of fees, slippage, liquidity, and partial fills.
- The project was halted before live order automation was complete, so research and prototype work had to be distinguished from operational outcomes.
Implementation Timeline
I extended hypothesis testing into repeatable data updates
These stages were not independent tasks. The buy/sell thresholds from Phase 01 and the current kimchi premium from Phase 02 feed into Phase 03, where they come together in trading signals and per-strategy state records. Select a phase to see the problem identified at that stage and how it led to the architecture and verification criteria.
Phase 01 · Threshold Backtesting
Threshold Backtesting
Outcome
Verifiable outcomes
- Implemented a backtest calculating profit and loss and comparison metrics for threshold combinations using hourly price data
- Created result reports with return heatmaps and buy-and-hold comparisons to review strategy conditions
- Automated hourly price collection, merging with existing data, and loading to local storage and Google Drive
- Implemented per-strategy wallet, fund, order, and execution log schemas and exchange-response mapping
Limitations
Limitations and unimplemented scope
- This was not independent validation with fully separate backtest and strategy-condition selection periods.
- Some threshold values differ between the documentation and experiment artifacts, so I do not present an exact optimum as a headline outcome.
- Live order automation and recovery from partial fills and exchange failures remained incomplete because the project was halted.
- Update status was checked every hour, but gaps in exchange-rate data availability were not automatically filled.
- Backtest returns should not be interpreted as actual investment performance or risk-free arbitrage results.
Further reading
Explore the design decisions
Public reflections covering alternatives, trade-offs, and current judgments omitted from the summary.

