Policy
A policy is consent with limits: how deep a fall you want made whole, the most you will pay per window, and when it expires. Without one the engine can do nothing — consent is a contract state, not a setting in our database. Priced against the live BTC · 5m window.
For reference, the demonstration account 0x7caEb6fc… runs 2.50% made whole, at most 3.00% per window, until 2026-10-14 18:30:00 UTC. That is not your policy — yours is below.
Make-whole point
How deep a fall you want covered in full.
The book is unpriceable right now
The current window’s Down side is one-sided, so there is no price to size against. Rather than show a made-up number, this waits — which is exactly what the engine does with a book it cannot price. The policy can still be set.
Limits
Both are per window, and both are checked on every purchase.
What would change
Connect a wallet to compare against your own policy; the current column is the demonstration account’s.
| Now | Proposed | |
|---|---|---|
| Make whole a fall of | 2.50% | 2.50% |
| Premium ceiling | 300 bps | 300 bps |
| Notional cap | 2,000.00 tUSDC | 2,000.00 tUSDC |
| Expires | 2026-10-14 | 2026-10-14 |
Revoke
One action, immediate, and no operator can block or delay it. Revoking stops new cover from being bought at the next window. Cover already open is untouched: it runs to settlement and pays out to you as normal, and your collateral stays withdrawable throughout. This is not a withdrawal and it does not close positions.
It also does not remove you from the cursor set. revoke() clears the policy, which is what stops the buying — the engine finds no consent and skips. Leaving the set is a second transaction, withdrawEnrolment(), and it is below. Neither is a prerequisite for the other and neither can be blocked.