Salience Theory and Cryptocurrency Returns
Log in to collectAcademic paper
Salience Theory and Cryptocurrency Returns
Charlie X. Cai; Ran Zhao
University of Liverpool- University of Liverpool Management School
Claremont Graduate University- Claremont Graduate University, Drucker School of Management
Strategy in a nutshell
The strategy invests in cryptocurrencies with a market capitalization above $1 million, using data from coinmarketcap.com. It calculates a Salience Measure (ST) for each crypto, which quantifies how much a crypto’s daily return deviates from the market average, adjusted by salience weights. Cryptos are then ranked based on ST values and sorted into quintiles. The strategy goes long on the lowest ST quintile (least salient) and short on the highest ST quintile (most salient). Portfolios are value-weighted and rebalanced regularly to capture the expected price reversals driven by salience effects.
Economic rationale
Cryptocurrency markets are dominated by retail investors who are highly susceptible to behavioral biases, particularly salience and attention-driven trading. Cryptos with unusually high salience often experience overreactions, while low-salience cryptos are underappreciated. As market prices revert to fundamental equilibrium, this creates predictable profit opportunities. The strategy leverages these behavioral patterns, exploiting the temporary mispricing caused by trend amplification, hype, or community-driven sentiment in the crypto market.
Entry & exit
Entry
Compute a 20-day z-score on each name in BTC-USD, ETH-USD. Enter when z ≤ -1 (stretched to the downside).
Exit
Exit when the z-score mean-reverts back to ≥ 0. Positions are not held through a full trend — only the snap-back.
Market data required
Needs at least 25 adjusted daily closes on BTC-USD, ETH-USD before the first signal is ready. Crypto columns include weekend rows. The lab loads Yahoo Finance via backtest.data.load_daily_prices.
Symbols
BTC-USD, ETH-USD
Frequency
Monthly · Daily adjusted close; signals rebalance on the month change (last available session)
History needed
≥ 25 trading days per symbol (about 2 months), plus a few extra bars so the first signal can fire.
Fields
- Adjusted close (Yahoo auto_adjust)
- Session date index
Credentials
- None for paper and the onsite lab
- Broker or exchange API keys only for live orders
APIs & providers
Quant Buffet Data API
The lab calls load_daily_prices for the ASSETS panel of adjusted closes, then caches CSV so backtests replay the same series.
- Provider
- backtest.data.load_daily_prices
- Auth
- None for paper / sandbox backtests
- Endpoints
- load_daily_prices(ASSETS, start="2000-01-01")
Yahoo Finance via yfinance
ETFs and crypto proxies such as BTC-USD / ETH-USD share Yahoo daily bars (auto_adjust=True).
- Provider
- yfinance → Yahoo Finance
- Auth
- None for public history
- Endpoints
- Ticker.history / yf.download(auto_adjust=True)
Onsite backtest IDE
Quant Buffet native backtest IDEEdit and run Quant Buffet Python for Salience Theory and Cryptocurrency Returns in the browser. Results update live with equity, drawdown, and metrics charts. Allowed: backtest.data, backtest.engine, backtest.metrics, numpy, pandas. Define ASSETS and make_on_day(prices). Shortcut: Ctrl+Enter. API docs →
Quant Buffet syntax cheat sheet (copy / insert)
Paste these fragments into the editor. The sandbox rejects QuantConnect, os, and network libraries.
from __future__ import annotations
import numpy as np
import pandas as pd
from backtest.data import load_daily_prices
from backtest.engine import EngineConfig, PortfolioEngine
from backtest.metrics import compute_metricsASSETS = ["SPY", "QQQ", "TLT", "GLD", "BIL"]def make_on_day(prices: pd.DataFrame):
cols = [c for c in ASSETS if c in prices.columns]
sma = prices[cols].rolling(200, min_periods=200).mean()
state = {"last": None}
def on_day(engine: PortfolioEngine, dt: pd.Timestamp) -> None:
if sma.loc[dt].isna().all():
return
key = (dt.year, dt.month)
if state["last"] == key:
return
state["last"] = key
long = [
s for s in cols
if pd.notna(prices.at[dt, s]) and pd.notna(sma.at[dt, s])
and prices.at[dt, s] > sma.at[dt, s]
]
weights = {} if not long else {s: 1.0 / len(long) for s in long}
engine.set_target_weights(dt, weights)
ready = sma.dropna(how="all").index.min() if sma.notna().any().any() else None
return on_day, readyengine.set_target_weights(dt, {"SPY": 0.60, "BIL": 0.40})Live backtest performance
Order records
Export to your platform
Transform Quant Buffet lab code (ASSETS + make_on_day / PortfolioEngine) into native classes for a third-party IDE — then copy and paste.
# Generated from Quant Buffet → QuantConnect LEAN
# Strategy: Salience Theory and Cryptocurrency Returns
# Detected pattern: Mean reversion
# Source uses Quant Buffet lab APIs (ASSETS + make_on_day / PortfolioEngine).
# Review fees, data, and risk before live trading — educational export only.
from AlgorithmImports import *
class QuantBuffetExport(QCAlgorithm):
def Initialize(self):
self.SetStartDate(2010, 1, 1)
self.SetCash(100000)
tickers = ["BTC-USD", "ETH-USD"]
self.symbols = []
for t in tickers:
if "-" in t: # crypto proxy e.g. BTC-USD
self.symbols.append(self.AddCrypto(t.replace("-USD", ""), Resolution.Daily).Symbol)
else:
self.symbols.append(self.AddEquity(t, Resolution.Daily).Symbol)
self.Schedule.On(
self.DateRules.MonthStart(self.symbols[0]),
self.TimeRules.AfterMarketOpen(self.symbols[0], 30),
self.Rebalance,
)
# Logic: Buy when return z-score < -1 over 20 days.
def Rebalance(self):
import numpy as np
picks = []
for symbol in self.symbols:
hist = self.History(symbol, 20 + 5, Resolution.Daily)
if hist.empty: continue
close = hist["close"]
if hasattr(close, "unstack"):
close = close.unstack(level=0).iloc[:, 0]
rets = close.pct_change().dropna()
if len(rets) < 20: continue
window = rets.iloc[-20:]
z = (window.iloc[-1] - window.mean()) / (window.std() or 1e-9)
if z < -1:
picks.append(symbol)
w = 1.0 / len(picks) if picks else 0.0
for symbol in self.symbols:
self.SetHoldings(symbol, w if symbol in picks else 0.0)
Exported code uses the platform’s native classes and libraries. Install dependencies in your third-party IDE, then run. Validate before live trading.