-
Notifications
You must be signed in to change notification settings - Fork 27
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
Don't apply subjective billing to read-only transactions #114
Don't apply subjective billing to read-only transactions #114
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently read-only transactions are signaled in controller as accepted_transaction
and as applied_transaction
. I think we should avoid signaling read-only transactions. Also read-only transaction traces are logged in deep-mind logger as applied. I think we should not deep-mind log them either.
This PR turns off subjective billing for read-only transactions.
*** Warning ***
An effect of this change is that compute_transaction becomes a potential DOS attack vector for any node that has enabled the compute_transaction end point. Any exposed node should implement some form of throttling to prevent this sort of attack.