lowerBoundTimestamp
and upperBoundTimestamp
. These parameters let you defer execution or enforce expiration on quotes, enabling powerful UX like scheduled actions, delayed bridging, market timing, and more.
Why Use Time Bounds?
- Scheduled execution (e.g. trigger after a certain amount of time)
- Custom expiry (e.g. keep trying to execute for five minutes, if simulation is error still - then discard)
- Sequential execution (e.g. execute a transaction every five minutes)
Setup
Instant Execution (Default Expiry)
Executes immediately and simulates until it passes or hits a 2-minute timeout.Instant Execution with Custom Expiry
Runs immediately but expires 1 minute after quote creation if it still errors.Scheduled Execution
Quote won’t be eligible to run until 5 minutes from now.Bounded Window Execution
Will only attempt execution between 2 and 5 minutes from quote creation.Developer Tips
- Timestamps are expected in seconds, not milliseconds.
- Quotes simulate continuously within the window. If execution fails for the full duration, they will revert.
- If both
lowerBoundTimestamp
andupperBoundTimestamp
are omitted, quotes execute immediately with a 2-minute fallback. - Use in combination with cleanup for robust, failure-tolerant flows.