Repository navigation
Conversation
Tron is held back from the CVF 2.0.0 fleet rollout (EXSC-1174). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
lifi-action-bot
marked this pull request as draft
October 15, 2026 11:26
Contributor
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 32 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
2 of 8 tasks
This branch has not been deployed
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.
Which Linear task belongs to this PR?
Ref EXSC-1174
Why did I implement it this way?
EXSC-1174 rolls CalldataVerificationFacet 2.0.0 out to every production EVM network. Tron is left out because a Tron redeploy costs a lot and 2.0.0 changes little there: it removes the unreachable AcrossV3 branches and adds an offset check in
extractNonEVMAddress. Tron is pinned at its current 1.3.1 (perdeployments/tron.diamond.json) instead of left onlatest. Perdocs/TargetState.md, an exact-version pin is how a network is deliberately held back, and the deploy guard and sign-time gate then refuse any other version there. The doc's list of current pins now includes this one.Tests:
bun testontargetStatePinGuard,pinned-target-stateandhealthCheckInvariants(360 pass). Prettier is clean.Checklist before requesting a review
Checklist for reviewer (DO NOT DEPLOY and contracts BEFORE CHECKING THIS!!!)
🤖 Generated with Claude Code