-
Notifications
You must be signed in to change notification settings - Fork 2
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
Explain potential for abuse #28
base: main
Are you sure you want to change the base?
Conversation
Co-authored-by: Dave Thaler <[email protected]>
@@ -198,6 +198,17 @@ not limited to those discussed in this document, can affect fingerprinting. A | |||
deeper analysis of this topic has been deemed out of scope. | |||
|
|||
|
|||
While protocol features, extensions, and versions all have legitimate uses, they | |||
can become a burden when used to excess. For example, the ability to send | |||
protocol grease that a peer is required to ignore can be abused to cause it to |
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.
Maybe explain some examples of the abuse — not just the fact of ignoring one greased object, but having a flood of them that are all ignored, etc.
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.
Thought: There is a "cost" when the greasing creates state, even if only to ignore the greased value. (I can think of cases where seeing a new value needs the receiver to do work to ignore. )
We could also have some positive advice earlier to generators of great to say "don't grease too much" |
Discussion in the room was: split the text across the sections, which I'll do on this PR so its not ready to be merged yet |
Fixes #22