-
Notifications
You must be signed in to change notification settings - Fork 80
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: remove support of v1 proofs in Miner actor #1391
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #1391 +/- ##
==========================================
+ Coverage 91.00% 91.04% +0.03%
==========================================
Files 145 145
Lines 27529 27485 -44
==========================================
- Hits 25053 25023 -30
+ Misses 2476 2462 -14
|
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.
Generally looks good to me!
Q: Do we need to remove v1 variants in
RegisteredPoStProof
altogether?
Yes, I think we'll want to do so in the FVM when releasing FVM4.
@@ -358,30 +358,24 @@ impl ProofSet { | |||
/// Create a `ProofSet` for enabled `RegisteredPoStProof`s | |||
pub fn default_post_proofs() -> Self { | |||
let mut proofs = vec![false; REGISTERED_POST_PROOF_VARIANTS]; |
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.
We should be able to drop the size of this REGISTERED_POST_PROOF_VARIANTS
field now.
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.
What do you mean exactly by dropping the size of REGISTERED_POST_PROOF_VARIANTS
?
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 number can change from 15 to 10?
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.
You mean from 15 to 5, no? Let me know if I am mistaken, I might not have all the context here.
I have also created counterpart PR in the FVM repo: filecoin-project/ref-fvm#1896
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.
Oh, nvm, I was wrong -- we can't reduce this number at all, because it needs to be indexed up to StackedDRGWindow64GiBV1P1
, which is 15.
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.
Yes but once the builtin-actors
repo is making use of FVM4 this should be possible (the V1P1
proofs are indexed from 0 to 4 there).
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.
Unfortunately, these numbers are consensus-critical, so we can't change them (easily).
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.
Got it!
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.
LGTM, thank you!
We were supporting partially v1 PoSt proof types in v11, now we don't support them anymore in v12.
Q: Do we need to remove v1 variants in
RegisteredPoStProof
altogether?Closes #1260