Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Increase strike safety factor when scanning chains #416

Merged
merged 1 commit into from
May 10, 2024

Conversation

brndnmtthws
Copy link
Owner

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.

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.
@brndnmtthws brndnmtthws merged commit 415a10a into main May 10, 2024
8 checks passed
@brndnmtthws brndnmtthws deleted the strike-safety-factor branch May 10, 2024 11:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant