docs: move deprecated contract addresses to legacy page - #29
Open
RhizoNymph wants to merge 1 commit into
Open
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
1 participant
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
Moves deprecated/legacy contract deployments out of the main Contract Addresses reference into a dedicated, lower-visibility Legacy Contract Addresses page, mirroring the
legacy/split landed indoppler(PR #525) anddoppler-sdk(PR #151).Why
PR #525 deprecated a set of contracts and relocated them to
legacy/in the protocol repo; the SDK followed in PR #151. The docs still listed those addresses inline in every network table on the main Contract Addresses page, presenting them as first-class options. This hides them while keeping the records reachable.Changes
reference/legacy-sdks-and-migration-guides/legacy-contract-addresses.mddoppler'slegacy/README.md).reference/contract-addresses.mdnow lists only active/canonical contracts, plus an info callout pointing to the legacy page.SUMMARY.mdadds the legacy page under the existing Legacy SDK migration guide section (relatively hidden, still navigable).Deprecated modules moved:
UniswapV3Initializer,UniswapV4MulticurveInitializer(+Hook),UniswapV4ScheduledMulticurveInitializer(+Hook),DecayMulticurveInitializer(+Hook),UniswapV4MigratorSplit(+Hook),UniswapV4MulticurveMigrator,ScheduledLaunchDopplerHook,StreamableFeesLocker(V1),CloneERC20(+Factory),CloneERC20Votes(+Factory),CloneDERC20VotesV2(+Factory),DERC20,DERC2080,TokenFactory,TokenFactory80.Retained as active (not moved):
LockableUniswapV3Initializer,UniswapV4Initializer,UniswapV2Migrator/MigratorSplit/Locker,StreamableFeesLockerV2,DopplerERC20V1(+Factory),DN404Factory,DopplerHookInitializer/Migrator,Rehype*, governance/no-op factories, quoters, deployers, etc.Out of scope / follow-ups
Two conceptual docs still mention legacy modules by name (not deployment records):
reference/overview.md(indexer event table) andcore-concepts/liquidity-migration-options.md(listsUniswapV4MulticurveInitializeras supported). Left unchanged to avoid altering technical descriptions — flag if you'd like them revised.