Lighter Explained: ZK Perpetual Trading, Order Books and Risk
A validity proof can verify state transitions; it does not protect traders from leverage or market manipulation.
Order-book performance depends on sequencer availability, market makers and reliable price feeds.
Key takeaways
Orders are matched off the base chain. The rollup commits state and proof data.
Margin is shared across positions. One losing trade can threaten the account.
Funding aligns perpetual prices. It can become a large recurring cost.
Liquidations are mechanical. Oracle and mark-price design determine timing.
The full trade path
A trader deposits through the supported bridge, submits signed orders, receives sequencer execution and later relies on proof verification and withdrawal. Each stage has different finality.
Risk beyond proofs
Inspect upgrade keys, emergency controls, oracle sources, insurance fund, auto-deleveraging and what users can do during sequencer downtime.
Trading discipline
Use isolated size, set slippage and reduce-only controls, monitor funding and test withdrawal before using leverage.
Decision checklist
Verify current official documentation, contracts or legal entities, administrator permissions, fees, liquidity and the full exit path. Test the smallest practical transaction and record what happens when an interface, oracle, bridge, operator or counterparty fails.
Keep a dated baseline of addresses, reserves or collateral, governance roles and normal withdrawal results. Recheck it after upgrades or incidents. An audit, license application, partnership or TVL number answers only one part of the risk.
Before increasing exposure, define an observable stop condition: a collateral deviation, missed withdrawal, governance change, loss of market depth or unsupported software version. Decide the response in advance and retain enough native gas and independent wallet access to execute it without relying on customer support.