Documentation

Everything Ballast does, what its cover actually pays, what that costs, and what it does not do — sourced from the contracts and from the run the engine recorded on chain.

Ballast buys downside cover for a position you already hold, automatically, in the same block the window opens. dreamDEX Event Contracts settle a fixed payout on a yes/no question about a price at a moment. They expire and are replaced constantly — as often as every sixty seconds — so cover bought against one window is worthless a minute later. In practice nobody sits up all night re-buying it. Ballast does, with no keeper in the money path: Somnia’s reactivity precompile invokes the handler as a synthetic transaction inside the block that triggered it.

What that buys is parametric cover, not a hedge, and these pages are careful about the difference. The payout is fixed, so it is exact at one depth of fall and wrong on both sides of it. That gap is basis risk, it cannot be engineered away on this instrument, and the pages below give it more room than the marketing would. The engine has stopped before, for days at a time; each stop has a measured reason, and they are written up rather than hidden.

Understanding

UnderstandingWhat it isThe product in plain language, the three steps, and one worked example end to end.UnderstandingWhat it paysParametric cover, the fixed payout, the three regions of the payoff, and basis risk.UnderstandingEconomicsWhere the cover costs money: the spread, the roll frequency, and why 4h and 24h.

Under the hood

Under the hoodHow it worksThree contracts, the reactive subscription, and the same-block path from trigger to cover.Under the hoodCustodyWhose money it is, what consent means, and how revocation works.Under the hoodRefusalsEvery reason Ballast declines to buy, and why declining is the product working.

Honest

HonestFindingsWhat we measured about Somnia and dreamDEX that is not in anyone's documentation.HonestLimitationsWhat is untested, what cannot be covered, and what the record does not prove.

Reference

ReferenceReferenceAddresses, chain details, the engine set, links to every source document, and a glossary.

The source

These pages are a presentation of documents that already live in the repository, and those documents remain the source of truth. Every figure quoted here is read from the same place the dashboard reads it — the chain, or the 80,658-event record the engine wrote over 1–11 September 2026 — so a number cannot say one thing here and another on the dashboard.

The repository — contracts, tests, scripts and every document below.
Raw markdown, if you would rather read the source than the presentation.
The run record — every event the engine emitted, as captured JSON.