-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
[consensus observer] add new BlockTransactionPayload variants to prepare for block gas limit override on blocks #15848
Conversation
…are for block gas limit override on blocks
⏱️ 37m total CI duration on this PR
🚨 1 job on the last run was significantly faster/slower than expected
|
transaction_limit: Option<u64>, | ||
gas_limit: Option<u64>, |
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.
should we make this an enum, so we just need to extend this in future if necessary?
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 was thinking this, but thought we probably don't need to extend it. Probably what we thought before too :P
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.
@ibalajiarun changed to an enum. There's a lot of "similar-looking and sounding" structs in here now, that we'll need to clean up later
OptQuorumStoreV2( | ||
PayloadWithProofAndLimits, | ||
/* OptQS and Inline Batches */ Vec<BatchInfo>, | ||
), |
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.
On second thought, we don't need a V2 for opt quorum store because we haven't turned it on yet?
QuorumStoreInlineHybrid(PayloadWithProofAndLimit, Vec<BatchInfo>), | ||
OptQuorumStore( | ||
PayloadWithProofAndLimit, | ||
TransactionsWithProof, |
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're okay breaking the existing serialization for the OptQuorumStore
?
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.
^ yeah, this is from @ibalajiarun
On second thought, we don't need a V2 for opt quorum store because we haven't turned it on yet?
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.
Awesome, thanks!
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! Thanks @bchocho 😄
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
✅ Forge suite
|
✅ Forge suite
|
✅ Forge suite
|
Description
These are the consensus observer message-side changes needed to support blocks having a block gas limit override. Once these messages are deployed, they can be used.
How Has This Been Tested?
Existing unit tests.
Key Areas to Review
Serde compatibility. Any structs that are currently used in messages should not be changed in place.
Type of Change
Which Components or Systems Does This Change Impact?
Checklist