The topic of quantum computing has been gaining popularity recently, and both the scientific community and investors seem to have high hopes for its future. It seems that this brand-new technology could revolutionize various aspects of computing as we currently know them. Great contributions could be made in the fields of medicine and healthcare, security, and computability [1], as well as in the field of finances, which interests us here at Quantpedia the most. Quantum computers are especially great in optimization tasks, so optimizing a portfolio could be one of the key contributions in our interest. [2] In this article, we would like to introduce the concept of quantum computers, their current state, their potential use in finance, and more.

Finding high-quality data with a long history can be challenging. We have already examined How To Extend Historical Daily Bond Data To 100 years, How To Extend Daily Commodities Data To 100 years, and How To Build a Multi-Asset Trend-Following Strategy With a 100-year Daily History. Following the theme of our previous articles, we decided to extend historical data of a new factor, the Dollar Factor. This article explains how to combine multiple data sources to create a 100-year daily data history for the Dollar Factor (the value of the United States Dollar relative to its most important trading partners’ currencies), introduces data sources, and explains the methodology.

The growth of passive investing and ETFs is indisputable. Consequently, this boom also affects financial markets (e.g., market elasticity or by creating predictable buys and sells) and assets that ETFs track. Even though all passive ETFs aim to replicate some benchmark index, there are two distinct approaches to doing so. The first approach is directly replicating the benchmark (by buying underlying assets) either by full direct replication or sampling. The second approach consists of synthetic replication using derivatives – most commonly by total return swaps (or futures). How do replication methods influence tracking error?