Repository navigation
Return block timestamp in EVM WriteReportReply - #916
Draft
Krish-vemula wants to merge 2 commits into
Draft
Krish-vemula wants to merge 2 commits into
Krish-vemula wants to merge 2 commits into
Conversation
This was referenced Nov 17, 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
EVM
WriteReportnow fills inWriteReportReply.block_timestamp(microseconds), matching Aptos and Stellar, for SLO tx-latency tracking.How
replyFromReceipt, so the change is made once there.HeaderByNumber(receipt.BlockNumber)(withWithQuickRetry) and returnheader.Timestamp * 1_000_000.FeatureEVMWriteReportBlockTimestampActivePeriod, checked against the execution timestamp. This is the same pattern as the L1 fee flag and the Aptos block timestamp flag.Behaviour
Testing
TestReplyFromReceiptBlockTimestamp(table-driven) covers: flag on/off, success and revert, header error, empty header, zero timestamp, missing block number, hash mismatch.TestReplyFromReceiptBlockTimestamp_NilLimiterOmitsTimestampTestWriteReportBlockTimestamp_FeatureFlagWiringruns the fullEVM.WriteReportflow with the limiter built from cresettings defaults.go test ./... -racepasses andgolangci-lintreports 0 issues (run against local chainlink-common).Dependencies
chain_capabilities/evm/go.modonce it merges.Rollout
Set
FeatureEVMWriteReportBlockTimestampActivePeriodin CRE settings for each environment to enable.