Add Pendle V2 swap context to upgrade explanations - #413
Merged
Merged
Conversation
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.
Pendle V2 PendleSwap upgrade alerts on Ethereum and Arbitrum now include the proxy's live owner, complete contract-scoped swap/approval/authorization source from the current and proposed implementations, and a pinned reference for the standard Pendle router integration. The context appears in both the LLM prompt and the full report, explaining the optional aggregator leg and exposing payload/enum changes even when the external ABI is unchanged.
The summary critique also checks that removing a scaling branch is not described as disabling every unscaled route, and that unknown storage compatibility is not presented as evidence of increased collision likelihood. The adapter covers direct upgrades and Safe multisend members; nested governance wrappers remain outside its scope.
Validation:
prek run --all-filespasses: Ruff lint/format andty.LLM output remains advisory: the live replay correctly described ODOS scaling removal, but refinement accepted an unsupported “v2” implementation-version label in one output, and risk tags varied between MEDIUM and HIGH. This change does not enforce a fixed risk rating or alter provider timeouts.