Security and audits
The whole pitch is that you do not have to trust us. Here is what backs that up, and the risks named outright.
Funds cannot be trapped
A corridor that reaches its end settles with no oracle report, so an outage cannot freeze your position.
Only your position is at stake
The rest of your balance stays yours. No operator can seize it or your winnings.
Admin powers, disclosed
Admin can tune fees, caps and curves within hard-coded bounds and rotate the keeper. Admin cannot touch the price, pick a winner, or seize your balance.
Public maths
The payout maths, the caps and the settlement rules sit in a contract anyone can read, and every result is recomputable from public data.
Residual risks, stated plainly
- ·Prompt liquidation depends on the operator publishing touch proof in its next batch. If the operator goes dark, your fallback is reclaiming your deposit after a bounded settlement window.
- ·The backstop is a loss-bearing counterparty. Caps mean no single win can sink it, but it can draw down.
- ·Span is an operator-maintained input. It is bounded and sizing-only, but it is the one input the venue maintains.
Publishing here
The independent audit report, its scope and fixes, the auditor and date, and a responsible-disclosure contact publish here. Until then, treat the properties above as claims you can verify against the code rather than a third-party attestation.