-
Notifications
You must be signed in to change notification settings - Fork 159
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
Update Runtime to Support V5 Actors #1173
Conversation
This still has todos and failing tests and linter. Is this RFR? |
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, left a few comments
@ec2 It looks good in my localhost. I merge this branch to my dev branch and now It can sync the whole latest actorv5 interopnet network:) |
let step = self | ||
.verify_aggregate_seal_steps | ||
.get(&proof_type) | ||
.expect("There is an implementation error where proof type does not exist in table"); |
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.
Same suggestion here as before. A HashMap
is lacking the knowledge that there is a price for each variant of proof type.
&seeds, | ||
inp, | ||
)? { | ||
Err("Invalid Aggregate Seal proof".into()) |
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.
Upsetting that this doesn't use a custom error type. Would it be worth it to create a ticket to define the error types here? Do you anticipate any complications will come up?
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.
This trait is fairly small.
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 dont see why its useful or important here. These methods are generally used in actors. And the way the error is handled is irrespective of what error happens here anyways. I think a refactor of error handling in this might mess up with error propagation in actors.
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. I left a few questions and suggestions that I'd like to talk through before approving.
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.
Thanks Eric
Summary of changes
Changes introduced in this pull request:
verify_aggregate_seals
andbase_fee
.TODO:
networks
crate to set Hyperdrive height (currently using placeholderReference issue to close (if applicable)
Closes
Other information and links