Understand market data, calculations and important limitations.
Where horakl gets the price data that drives performance calculations.
horakl computes portfolio performance from market price data. The current configuration sources market data from third-party providers.
The exact data provider, token universe and eligibility thresholds are configured on the backend and may change. Do not rely on a specific provider or threshold for decisions without confirming the current configuration.
How often prices are refreshed and how updates flow into metrics.
Prices and portfolio metrics are processed by scheduled backend pipelines. The displayed NAV, ROI and risk metrics reflect the latest processed snapshot rather than a live tick.
Refresh cadence is controlled by the backend pipeline. Confirm the current update frequency in the product before relying on exact timing.
How NAV and ROI are conceptually derived from allocations and prices.
Portfolio performance is derived from the recorded allocation and market prices. Each portfolio is normalized to an initial NAV of 100.
ROI = (Current NAV / Reference NAV − 1) × 100
The exact reference points, smoothing, weighting of intra-period rebalances and annualization of risk metrics are implemented in backend pipelines that are not documented here. The formula shown is a conceptual description, not the implemented specification.
How portfolio history is preserved across rebalances and changes.
horakl preserves portfolio history. When a manager rebalances or removes a holding, the previous state is retained so past performance and composition remain auditable.
Rebalance history records the date, the changes and the total absolute weight change for each adjustment.
Important limits of model portfolio performance and horakl metrics.
horakl metrics are useful for comparison and reputation, but they have important limits. Read these before interpreting any number.
Model portfolio performance is not the same as the realized return an investor would have achieved. Slippage, timing, fees and execution differences are not captured in a model.
Historical performance does not guarantee future performance. A high Score or strong ROI does not imply future outperformance.
Metrics depend on the availability and quality of market data. Missing or delayed prices can affect snapshots.
On-chain confirmation times and network fees vary by network and conditions. Payments and withdrawals can take time to confirm.
Comparisons versus Bitcoin depend on the implemented benchmark methodology and the period shown.
Metrics should be interpreted together rather than in isolation. ROI, risk and behavioral factors each describe a different dimension.
horakl research, the Score and rankings should not be treated as financial advice. This article is a methodology and product explanation; formal legal wording is subject to separate legal review.