Option Position Lifecycle
Understand the CallPut position lifecycle from open request to execution, close request, expiry and settlement, including Pending, Executed and Cancelled request states.
Open request
An option trade begins as a request on the selected network. The request must progress through the protocol lifecycle before it should be treated as an executed position.
Track request state
Use the request key and protocol state. Pending means the request is not yet final, Executed means the protocol completed it, and Cancelled means the request did not become an active position.
Close before expiry
Closing is also request-based. Confirm the close request state and the resulting position balance rather than relying on the wallet transaction alone.
Post-expiry settlement
After expiry, settlement uses the protocol settlement path. The documented architecture separates active-position management from post-expiry settlement.
Frequently asked questions
What does the Option Position Lifecycle page cover?
It covers understand the CallPut position lifecycle from open request to execution, close request, expiry and settlement, including Pending, Executed and Cancelled request states.
Does a documentation example guarantee a live market or fill?
No. Market availability, expiries, strikes, liquidity, fees and contract state can change. Check the live application and selected network before acting.
Are CallPut stock and ETF options ownership of the referenced security?
No. The documented stock and ETF options are synthetic onchain instruments and do not grant shares, fund units, dividends, voting rights or physical delivery.