The chart above plots the **Price of 1 Ounce Of Gold** and the **Inflation-Adjusted 10-year Treasury Yield**. The real interest rate is defined as the difference between the nominal interest rate and the (expected or actual) inflation rate.
The real yield in the chart above is calculated by subtracting the 10-Year *(expected)* Inflation Rate from the 10-Year Treasury Constant Maturity Rate.

According to Erb and Harvey the correlation between real interest rates and the price of gold is -0.82. In other words, when real yields go down gold goes up. This correlation explains why inflation is gold's best friend while rate hikes are its worst enemy.

Here is a possible explanation for this relationship. Rising interest rates also mean rising opportunity costs of holding gold. Gold neither pays dividends nor interest. Thus, it is relatively expensive to hold it in the portfolio when real interest rates are high. On the other hand, when real yields are negative, holders of cash and bonds are losing wealth. In such a scenario, they are more prone to buy gold.

- Federal Reserve Bank of St. Louis: 10-Year Treasury Inflation-Indexed Security, Constant Maturity
- OnlyGold: Historic Gold prices
- Quandl: Recent Gold prices

- SSRN: The Golden Dilemma
- Sunshine Profits: Real Interest Rates and Gold
- Investopedia: What is a Real Interest Rate?
- Poket Casts: Adam Robinson on the Angelo Robles Podcast (at 53:26)

The real yields in this chart are calculated by subtracting the *actual* inflation rate from the nominal interest rates (rather than by subtracting the *expected* inflation rate). The methodology is described here in more detail.

- Stooq: 10-Year Treasury Constant Maturity Rate
- 1-Year Treasury Constant Maturity Rate
- Robert Shiller Online Data: Data until 1929
- Capital Markets Data: Data from 1929 until 1990 (orginally from here and here)
- Quandl: Data since 1990
- Inflation
- Robert Shiller Online Data: CPI from 1871 until 1913
- Federal Reserve Bank of St. Louis: CPI since 1913

An error appeared while loading the data. Maybe there is a technical problem with the data source. Please let me know if this happens regularly @silvan_frank.