Security
State verification, contract security, resolution security and administrative permissions.
Do not trust the interface. Verify the state.
State Verification
Published transaction data lets anyone replay F over the same inputs and reproduce the state independently. If a reconstructed state differs from the reported one, the reported one is wrong.
Smart Contract Security
- Market, vault and settlement logic lives in contracts with explicit, minimal external interfaces.
- Accounting changes are state transitions, not backend records.
- Contracts are reviewed before they hold user capital; audit reports are published when complete.
Oracle / Resolution Security
Resolution is where prediction markets fail most often. The direction is multi-signature submission plus a challenge window before finalisation, so a single reporter cannot decide an outcome alone.
Submit Result→
Challenge Window→
Finalize
Administrative Permissions
- Privileged functions are enumerated, scoped and intended to shrink over time.
- Emergency controls exist to pause, not to move user funds arbitrarily.
- Upgrade paths and their controllers are disclosed as the contracts are deployed.
COMING SOONPublished audit reports and a bug bounty programme.