Price markets depend on configured price feeds. A feed can be stale, unavailable, delayed, or rejected by validation rules. Some Pyth actions also require fresh update data and an ETH fee.Different markets can use different adapters, such as Pyth, Chainlink, or TWAP-style sources. Do not assume two markets use the same price source or freshness rules.
Event markets depend on resolution modules and resolvers. A dispute path can take time, require bonds, and depend on a resolver decision.Permissionless creation increases market choice, but it also increases the need to read the question, rules, resolver, evidence standard, and invalid conditions before trading.
Some deployments include roles for pausing, risk parameters, oracle changes, treasury settings, market creation, or settlement configuration. These controls can protect users, but they also introduce governance and operational risk.
Frontends, indexers, metadata services, and wallet providers can fail or show incomplete data. A successful contract transaction may differ from what an offchain UI last displayed.When app data and contract state differ, the transaction follows the contract state. Refresh the page, check the connected network, and review wallet simulation details when available.
