-
Notifications
You must be signed in to change notification settings - Fork 86
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
chore: Delete bad token detection #2319
Comments
This issue has been marked as stale because it has been inactive a while. Please update this issue or it will be automatically closed. |
Not stale, just taking a bit longer than expected. |
This issue has been marked as stale because it has been inactive a while. Please update this issue or it will be automatically closed. |
This issue has been marked as stale because it has been inactive a while. Please update this issue or it will be automatically closed. |
This issue has been marked as stale because it has been inactive a while. Please update this issue or it will be automatically closed. |
This issue has been marked as stale because it has been inactive a while. Please update this issue or it will be automatically closed. |
Background
Bad token detection is a crutch needed when we are not able to verify quotes. Once we are confident in the quote verification logic we should delete it. Since this is also the only code we use
trace_callMany
we can also delete support for that.One thing to look out for is that we'll probably experience higher load because we will be serving more tokens than before.
The text was updated successfully, but these errors were encountered: