Bump chainlink-protos/svr to v1.3.0 and emit per-OFA gas limit#503
Merged
Conversation
product-security-plaid-production
Bot
requested review from
DylanTinianov,
RensR,
jmank88 and
silaslenihan
July 15, 2026 14:11
Contributor
|
jmank88
previously approved these changes
Jul 15, 2026
dimriou
reviewed
Jul 15, 2026
dimriou
reviewed
Jul 15, 2026
dimriou
reviewed
Jul 15, 2026
mostlyconsistent
force-pushed
the
oev-1356-gas-limit-plumbing
branch
from
July 16, 2026 12:54
42c9d6d to
e6a9074
Compare
dimriou
approved these changes
Jul 16, 2026
dimriou
enabled auto-merge (squash)
July 16, 2026 14:55
jmank88
approved these changes
Jul 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What
github.com/smartcontractkit/chainlink-protos/svrfromv1.2.0→v1.3.0, which adds the optionalgas_limitfield (9) to theTxMessageproto.TxMessage.GasLimit.Why
The OFA gas tier reserves the last two digits of the gas limit per OFA backend so an on-chain transaction can be attributed to a specific OFA (e.g. Titan / MEV-Share) for auction and performance comparison. Until now that tiered limit was computed at broadcast time but never made it into the beholder
TxMessage, so downstream consumers couldn't attribute transactions.Builds on top of #462