Gaia — the BTC accumulation basket
Gaia is a non-custodial, advisory BTC accumulation program. It is not a trade feed and it never touches your keys or your custody. Instead it publishes a basket — a set of statistically sized buy deployments — designed to do one thing: drive your lifetime cost basis below a naive dollar-cost-average (DCA) of the same capital.
Where the live signal feed is active — discrete entries and exits a subscriber must execute — Gaia is passive. You contribute capital on your own cadence; the program tells you how much of your equity to deploy into BTC each time the market reaches a statistically cheap level. You hold what you accumulate. There is no exit, no stop, no churn.
The product alias is
gaia. Throughout these docs that is the only product identifier you key off — exactly as the signal feed keys off its ownalias.
What it does
Gaia watches BTC on 4H bars and deploys into dips: when price is statistically depressed
relative to the deployment window, the program fires a buy and reports a deploy_pct — the fraction
of your equity to put to work at that moment. Over a full window the accumulated buys land, on
average, well below both VWAP and a calendar DCA of the same total capital. Every sales-page
number quantifying that advantage is reproducible from the keyless preview endpoint — see
Benchmark methodology.
Tiers, aliased by horizon
The basket is split across three tiers, aliased by horizon — you never see the underlying mechanism, only the horizon label and a depth band:
| Tier | Horizon | Static weight |
|---|---|---|
| core | longest | 60% |
| cyclical | medium | 20% |
| tactical | shortest | 20% |
Each tier fires at one of two depth bands, d1 (shallower dip) or d2 (deeper dip).
A deployment is fully described by its tier (core / cyclical / tactical) and its depth
(d1 / d2) — nothing more. See Data model.
Verification status
:::note Gaia is backtested and engine-verified — but it is not one of the dual-verified signal strategies
Gaia is backtested and engine-verified: the production engine is bit-exact against a
canonical reference port, so the numbers the program publishes are exactly the numbers the
methodology computes. Its allocation logic is independently verified against a hand-authored
TradingView indicator — 94% of deploys land on the same bar at the same price. Its tv_status
remains provisional: it has not completed independent forward verification, and the
published avg cost and DCA-savings figures are engine-backtested, not independently
TradingView-verified. It is not part of the dual-verified live signal set. Treat Gaia as
an advisory accumulation aid, not a verified live-trading strategy.
:::
What you build
- Data model — the basket object,
deploy_pct, tiers, anddeployment_state. - Endpoints — the gated program API and the keyless marketing preview.
- Benchmark methodology — exactly how every published number is computed, with a worked example you can recompute yourself.