Increase strike safety factor when scanning chains #416
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When no strike limit was specified, we would previously scan above/below the current underlying price, plus/minus 2%, when looking for contracts to either roll to or write. The reason for this is that sometimes a 50 delta contract is ITM, so we might miss out on some juice.
This just increases that safety factor from 2% (relative to the underlying price) to 5%. The only downside of this is that if we're trying to write contracts really far OTM (such as 0.1 delta, for example) we might need to increase the number of strikes to load from the chain.