Engine
The reactive contract that does the buying. 0xFE7250509634ABb94b3cDbd72eb122feCcaC157c — subscribed to dreamDEX’s window events, woken by Somnia’s reactivity precompile inside the block that triggered it, with no keeper in the money path. A separate watcher reads the chain for notifications and balance alerts.
Subscribed, but not being woken
The engine still holds subscription 22,911,033, but no callback has arrived since 2026-09-26 07:30:00 UTC. Until one does, nothing here is covering anything. This is the contract’s own stale flag, read when this page was requested — not an inference.
What this deployment did
Live counters on the engine contract — permanent, and unaffected by the subscription closing. It opened cover on 3,836 of the 19,501 windows it saw. The gap is not a miss rate: most windows carry no exposure to cover, or no book to price it against, and refusing those is the behaviour, not a failure of it. Every refusal, with its reason.
These do not match the recorded history, and a reader who notices that deserves the reason rather than the benefit of the doubt. Covers opened reads 3,836 here against 258 in the record, because the record is one account’s history across every engine Ballast has deployed, and this page counts only this contract. Wakes billed counts every event the subscription matched; Somnia charged each one at the gas it actually used, and most of them only registered a window.
Parameters
Every one of these is a subscription or constructor parameter, readable on chain. None of them requires a new contract to change.
Enrolment and queue
- Enrolled accounts
- 2accounts the engine will act for
- Windows pending
- 3,087seen, not yet resolved either way
Retry ladder
- Max attempts
- 3tries before a window is given up as unpriceable
- Initial delay
- 15swait before the first attempt, so the book can form
Cost and runway
- Callbacks per window
- 1.87measured, not configured — how many wakes each window costs
- Windows remaining
- 0a floor: this contract's worst-case estimate, not what Somnia charges
- Health reading
- Stalethe engine has not been woken recently
The recorded history
6 engine deployments over one vault wrote 80,658 events to the chain over 1–11 September 2026, across blocks 476,937,616–485,350,332. That history is on chain and independently checkable; the capture committed to the repository is a convenience, not the source of truth. Read it on Activity, or verify each engine on the explorer: 0xB095Aacf…, 0x9cf2fBC0…, 0x8ff05870…, 0x9026b93d…, 0x234520a8…, 0xFE725050….