Security & risks
Smart contracts, public networks, oracle systems, and wallets can fail. This page summarizes the main boundaries; it is not financial, legal, or security advice.
Contract and upgrade risk
A deployed contract can contain bugs or use permissions that differ from a user's expectations. Read the verified source, deployment metadata, and current role configuration before treating a market as trust-minimized.
Oracle and automation risk
A proof source can be delayed, unavailable, disputed, or misconfigured. Automation improves liveness but does not make a centralized reporter trustworthy by itself. The contract's stale-data, timeout, cancellation, and refund behavior matters more than a status badge.
Wallet and network risk
- Transactions can fail, be delayed, or be irreversible after signing.
- RPC responses and indexer records can be stale or unavailable.
- Only connect a wallet you control and verify the destination, chain, amount, and contract before signing.
- Testnet assets have no promised real-world value.