Add Slipstream V3 to dex_protocol enum#1
Merged
Conversation
Wires V3 rebalancer, compounder, and yield-claimer addresses into the AM address map and extends the DexProtocol type and template enum so the agent can configure V3 positions. Base-only (the position manager is only deployed on Base).
j-vp
approved these changes
Apr 18, 2026
j-vp
approved these changes
Apr 18, 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
2 participants
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.
Summary
Extends the plugin to support Slipstream V3 as a
dex_protocolvalue alongside V1 and V2. Wires the new V3 rebalancer, compounder, and yield-claimer addresses intoAM_ADDRESSES, extends theDexProtocolandAmProtocoltypes, and addsslipstream_v3/staked_slipstream_v3to the template prompt so the LLM can propose V3 automations.V3 is Base-only (position manager isn't deployed on Unichain/Optimism). Since this plugin is already Base-only today, no chain-routing changes are needed.
All 59 tests pass, typecheck clean. Optimism support is a larger refactor (per-chain POOLS/TOKENS maps) and is out of scope here.