Fix 404: Redirect legacy contract-addresses URLs to v2 page and add to navigation

[Copilot]

/references/contract-addresses and /v1/references/contract-addresses were returning 404 or serving stale v1 content. After investigating the v2 documentation structure, the existing v2/resources/references/contract-addresses.mdx page (which contains current Arbitrum Mainnet and historical contract addresses) was found to not be wired into the v2 navigation. Both legacy URLs now redirect to the v2 page, and the page has been added to the v2 navigation.

Description

• Investigated v2 documentation structure and confirmed v2/resources/references/contract-addresses.mdx exists with comprehensive current contract addresses (Governor, Controller, LivepeerToken, BondingManager, TicketBroker, ServiceRegistry, AIServiceRegistry, etc.) plus historical entries — but was not in the navigation.
• Added redirects in docs.json so both the unversioned legacy URL and the v1 URL point to the v2 canonical page.
• Added v2/resources/references/contract-addresses to the Protocol References navigation group in all 4 language tabs (English, Spanish, French, Chinese).

Note: The existing v2/about/resources/blockchain-contracts page (already in the nav) covers the conceptual/architectural overview of the contract system; the newly surfaced reference page provides the actual deployed addresses.

Scope

• docs.json — redirects array and navigation groups (Protocol References in all 4 language tabs)

Validation

• Verified redirect from /references/contract-addresses → /v2/resources/references/contract-addresses
• Verified redirect from /v1/references/contract-addresses → /v2/resources/references/contract-addresses
• Verified all 4 Protocol References navigation groups now include v2/resources/references/contract-addresses
• Confirmed docs.json remains valid JSON post-edit

Follow-up Tasks

None

Type of Change

• Bug fix (fixes an issue)
• New content (adds new documentation)
• Content update (improves existing content)
• Style/formatting fix
• Information architecture change
• Other (please describe)

Related Issues

Related to #

Changes Made

• Added redirect: /references/contract-addresses → /v2/resources/references/contract-addresses
• Added redirect: /v1/references/contract-addresses → /v2/resources/references/contract-addresses
• Added v2/resources/references/contract-addresses to Protocol References navigation group in all 4 language tabs (en, es, fr, cn) in docs.json

Testing

• Tested locally with npm run dev
• Verified all links work
• Checked formatting and style
• Reviewed against style guides
• Screenshots (if UI changes)

Screenshots (if applicable)

N/A

Checklist

• My changes follow the style guides
• I've reviewed the Component Library for available components
• I've updated related pages if needed
• I've checked for broken links
• My changes are clear and easy to understand
• I've tested locally
• I've added/updated keywords and metadata if needed

Additional Notes

The v2/resources/references/contract-addresses.mdx page already contained up-to-date contract addresses for both Arbitrum Mainnet (current Delta protocol) and Ethereum Mainnet, as well as historical deprecated addresses. It simply needed to be surfaced in the navigation and pointed to by both redirect entries. The v1 docs themselves remain frozen/immutable — only redirect entries in docs.json were added.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>404 Error: "Old Contracts" page failing to redirect to new documentation</issue_title>
<issue_description>### Description

When accessing the legacy "Old Contracts" documentation page via search engine results (Google), the page fails to redirect to the updated documentation and instead returns a 404 Not Found error.

Steps to Reproduce

1. Search Google for "Livepeer Contracts" or use the direct legacy URL (if known).
2. Click on the link pointing to the old documentation path.
3. Observe the 404 error page.

Expected Behavior

The legacy URL should perform a 301 Permanent Redirect to the corresponding section in the new documentation to preserve SEO and user experience.

Technical Details

Source URL (Broken): https://docs.livepeer.org/references/contract-addresses
**Target URL (Expected): http://docs.livepeer.org/v1/references/contract-addresses#</issue_description>

<agent_instructions>Please create a PR to resolve this issue on base branch docs-v2 (not main)</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes 404 Error: "Old Contracts" page failing to redirect to new documentation #766

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[DeveloperAlly]

@copilot the documentation is now at version v2. please establish if v2 documentation navigation provides the correct new addresses and if not establish where it should be and draft this into the current structure of v2

[Copilot]

@copilot the documentation is now at version v2. please establish if v2 documentation navigation provides the correct new addresses and if not establish where it should be and draft ...

Investigated the v2 structure. There is already a comprehensive contract addresses page at v2/resources/references/contract-addresses.mdx with current Arbitrum Mainnet addresses (Governor, Controller, LivepeerToken, BondingManager, TicketBroker, etc.) plus historical entries — it just wasn't wired into the navigation.

Changes made in commit ad29773:

1. Updated the redirect: /references/contract-addresses → /v2/resources/references/contract-addresses (was pointing to v1)
2. Added v2/resources/references/contract-addresses to the Protocol References navigation group in all 4 language tabs (en, es, fr, cn) in docs.json

The page surfaces under Resources → Technical References → Protocol References in the v2 nav. The existing v2/about/resources/blockchain-contracts page (already in nav) covers the conceptual/architectural overview, while this reference page provides the actual deployed addresses.

[DeveloperAlly]

@copilot can you confirm the v1 page now also points to the v2 addresses?

[Copilot]

@copilot can you confirm the v1 page now also points to the v2 addresses?

Added in commit 91c4956. Both the unversioned and v1 URLs now redirect to the v2 page:

• /references/contract-addresses → /v2/resources/references/contract-addresses
• /v1/references/contract-addresses → /v2/resources/references/contract-addresses

[DeveloperAlly]

@rickstaa could you please review if this is now resolved or if errors remain?