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.
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
Draft of Phasing Out Fil+ and Restoring Deal Quality Multiplier to 1x #788
Draft of Phasing Out Fil+ and Restoring Deal Quality Multiplier to 1x #788
Changes from 29 commits
45ea13b
5ecbbde
7a96cbb
1553ffa
aafbb9c
af7bf20
f34f4e5
c69a078
205f243
e9b8cf1
9c34ab0
b2238b7
ddf07b5
aad40f6
b9e27af
35bc71c
b15740a
caac144
312cba2
cdaa688
e8e4f26
c84945c
e8aea2e
e64d75e
237885e
a38eeb8
1a7546b
92e04c6
fbdddb7
be9381b
fc63f2b
3a22f1d
b11d6b7
94946a3
7075a6c
a3b5966
ee50ff3
437305a
4923d0e
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
The fact that pledge collateral requirements fall due to baseline crossing just make the problem even worse. It's not a mitigation.
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.
I think the argument being made is that by reducing non-hardware costs, more hardware will be onboarded to secure the network -- that seems reasonably intuitive in any scenario of finite SP financial capacity. It doesn't follow that this results in "increasing the cost to attack" as a very significant increase in storage capacity (certainly more than the 2x comparison between current and peak RBP) would be required to match the same level of resources at stake. This is not a deal breaker -- it's a choice -- but also not something that can be swept under the rug.
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.
Resolved.
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.
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.
My bad. Resolved.