MétaCan
Menu
Back to cohort
Record W4294839466 · doi:10.3390/math10173190

Forecasting the Volatility of Cryptocurrencies in the Presence of COVID-19 with the State Space Model and Kalman Filter

2022· article· en· W4294839466 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueMathematics · 2022
Typearticle
Languageen
FieldComputer Science
TopicBlockchain Technology Applications and Security
Canadian institutionsUniversity of Manitoba
FundersUniversiti Malaya
KeywordsCryptocurrencyAutoregressive conditional heteroskedasticityEconometricsStochastic volatilityVolatility (finance)State-space representationAutoregressive modelKalman filterForward volatilityMathematicsStatisticsEconomicsComputer scienceAlgorithm

Abstract

fetched live from OpenAlex

During the COVID-19 pandemic, cryptocurrency prices showed abnormal volatility that attracted the participation of many investors. Studying the behaviour of volatility for the prices of cryptocurrency is an interesting problem to be investigated. This research implements the state space model framework for volatility incorporating the Kalman filter. This method directly forecasts the conditional volatility of five cryptocurrency prices (Bitcoin (BTC), Ethereum (ETH), Ripple (XRP), Litecoin (LTC) and Bitcoin Cash (BCH)) for 10,000 consecutive hours, i.e., approximately 417 days during the COVID-19 pandemic from 26 February 2020, 00:00 h until 18 April 2021, 00:00 h. The performance of this model is compared to the GARCH (1,1) model and the neural network autoregressive (NNAR) based on root mean square error (RMSE), mean absolute error (MAE) and the volatility plot. The autocorrelation function plot, histogram and the residuals plot are used to examine the model adequacy. Among the three models, the state space model gives the best fit. The state space model gives the narrowest confidence interval of volatility and value-at-risk forecasts among the three models.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.768
Threshold uncertainty score0.189

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.042
GPT teacher head0.261
Teacher spread0.219 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it