← All articles

quant

17 articles on quant.

backtestingbasis tradingcryptodata engineeringdata qualitydeveloper experienceeducationemerging managersexchangesexecutionfeesfund managementfund operationsfunding ratesinfrastructurelive tradingnon custodialperpetualsquantrisk managementsecurity

funding-rates · basis-trading · perpetuals

Anatomy of a Funding-Rate Trade: One Cycle Inside a Carry Book

Everyone quotes funding-arb returns; almost nobody walks through a single trade end to end. Here's one full cycle of a delta-neutral carry position — the sizing, the two entries, what every settlement actually pays, the mid-life basis wobble that scares people out, and the exit arithmetic.

The Fluxy Team ·

live-trading · backtesting · execution

When Live Doesn't Match the Backtest: A Diagnosis Checklist

Every systematic trader eventually stares at the same chart: the live equity curve sagging under the backtest that justified it. Sometimes the strategy is broken. More often something specific and findable is leaking — and the causes have an order you should check them in.

The Fluxy Team ·

data-quality · backtesting · data-engineering

Reading a Data-Quality Report: The Numbers Behind the Numbers

Every backtest report we produce ships with a second report almost nobody reads: the data-quality section. It's the one that tells you whether the first report means anything. Here's how to read it, and the thresholds where a beautiful equity curve should go in the bin.

The Fluxy Team ·

funding-rates · perpetuals · data-study

The Funding Rate Almanac: What Five Years of Perp Carry Actually Paid

We took every settlement-level funding print in our market database — 80,000 of them across Binance, Hyperliquid, and KuCoin since 2019 — and measured what collecting perp funding actually paid. The answer: a real but violently regime-dependent yield, and a persistent cross-venue gap that most carry traders are leaving on the table.

The Fluxy Team ·

risk-management · volatility-targeting · position-sizing

Volatility Targeting in Crypto: Position Sizing That Respects the Regime

A fixed 1-BTC position is not one risk — it's five different risks depending on the month. Volatility targeting inverts the question: decide how much risk you want, then let position size float to deliver it. In a market where vol swings 5x, it's less an optimization than a survival trait.

The Fluxy Team ·

backtesting · survivorship-bias · delistings

Survivorship Bias in Crypto Backtests: The Coins That Aren't There Anymore

Build your universe from today's listings and you've quietly deleted every coin that died — which means your backtest only ever trades the winners. In crypto, where delisting is routine and drawdowns end at zero, survivorship bias isn't a footnote. It's often the whole edge.

The Fluxy Team ·

backtesting · walk-forward · out-of-sample

Walk-Forward Analysis in Crypto: Making Out-of-Sample Mean Something

Every parameter sweep produces one combination that looks brilliant — and most of them are brilliant only at describing the past. Walk-forward analysis is the discipline that separates a strategy from a coincidence: tune on one window, judge on the next, and only ever trust the windows the strategy never saw.

The Fluxy Team ·

research · productivity · quant

Speed Is Alpha: Why Research Velocity Quietly Compounds Into an Edge

Two quants with equal talent, equal data, and equal ideas can end up worlds apart for one unglamorous reason: how fast they can test an idea and move to the next one. Research velocity isn't a convenience. It's a compounding advantage that, over months, separates the funds that find robust edges from the ones still waiting on yesterday's backtest. Here's why speed is its own kind of alpha.

The Fluxy Team ·

onboarding · templates · developer-experience

Start From Working Code: Templates That Solve the Blank-Editor Problem

The hardest moment in any strategy platform is the empty editor and a blinking cursor. We seed it with real, runnable templates — EMA trend, Bollinger mean-reversion, momentum — each a complete Strategy you can backtest in one click and then make your own. Here's why starting from working code beats starting from a blank page, every time.

The Fluxy Team ·

backtesting · metrics · sharpe

Reading a Backtest Honestly: Metrics That Don't Flatter

It's easy to compute a Sharpe ratio. It's harder to compute one that won't embarrass you in front of an allocator. Our metrics derive elapsed time from the calendar span (not the bar count), use textbook downside deviation, and ship a data-quality report alongside every result — because a number you can't defend is worse than no number.

The Fluxy Team ·

data-engineering · data-catalog · architecture

Logical Datasets, Not Raw Tables: The Catalog That Decouples Strategies From Storage

Crypto data is a mess of inconsistent column names, symbol formats, and venue quirks. The dataset catalog maps a clean logical name — 'ohlcv', 'funding' — to a physical table plus a column map and point-in-time semantics, so a strategy says what it needs and never touches a raw table. Add a data source by adding a catalog row, not changing engine code.

The Fluxy Team ·

ai · llm · code-generation

From Prompt to Validated Strategy: AI That's Grounded in Your Real Data

An LLM that writes trading code from a one-line description is a parlor trick — unless it's grounded in the exact authoring API, the live dataset catalog, and real sample rows, and its output is validated against the same sandbox the engine uses, with an automatic repair round. Here's how we make AI-generated strategies that actually run.

The Fluxy Team ·

developer-experience · editor · monaco

An Editor That Writes Itself: Autocomplete Derived Straight From the Engine

A strategy editor whose autocomplete drifts from the engine is worse than no autocomplete — it confidently suggests methods that don't exist. Ours introspects the real source at startup, so the surface you're offered is exactly the surface that runs — every deploy refreshes the editor automatically. Add a method with one decorator and it appears in the editor; no frontend change.

The Fluxy Team ·

backtesting · optimization · parameter-sweep

3,125 Backtests Before Lunch: Parameter Sweeps with Parquet Caching

Research velocity is a competitive edge. A grid of five parameters across five values is 3,125 backtests — and on our engine the data for all of them is pulled once, cached as parquet, and reused. Here's how the sweep harness and the cache turn a coffee-break into a sensitivity study.

The Fluxy Team ·

backtesting · live-trading · execution

Same Code, Everywhere: From on_bar() Backtest to Live Cron in One Engine

The deadliest gap in systematic trading is between the code you backtested and the code that trades live. We close it by running the exact same engine in both — preflight in milliseconds, backtest in minutes, then schedule the identical strategy as a live signal runner with mandate execution and a dry-run safety net.

The Fluxy Team ·

backtesting · funding · perpetuals

Funding Carry Is a First-Class Citizen: Backtesting Perp Basis Without Hacks

If your backtester ignores funding, every carry, basis, and delta-neutral strategy you test is a fiction. Our engine charges funding at each venue's real settlement times, on live mark notional — so a Binance 8h feed and a Hyperliquid 1h feed are both charged correctly in the same study.

The Fluxy Team ·

backtesting · quant · data-engineering

No Look-Ahead by Construction: Killing the #1 Backtest Lie

Most backtests quietly leak the future into the past. Here's how our engine makes look-ahead bias structurally impossible — as-of joins on the bar clock, per-instrument freshness TTLs, and a leak-check attestation on every preview.

The Fluxy Team ·

© 2026 Fluxy, Inc. All rights reserved.