Bug: Missing canonical Base network metadata causes inconsistent chain detection across apps

[flytrapturtle]

Describe the bug

Applications built on base/web rely on consistent network metadata (chain ID, name, RPC references) to correctly detect and display Base network information. In some cases, network metadata is duplicated or partially defined, leading to inconsistent chain detection and UI labeling across different parts of the site.

Steps

Developers and users may encounter situations where:

• Base Mainnet / Base Sepolia are labeled differently across pages
• Chain metadata (name, ID, explorer links) is redefined in multiple places
• Updates to network info require changes in several files

Steps to Reproduce

1. Inspect different sections of the base/web codebase where network info is referenced.
2. Compare how Base Mainnet or Base Sepolia metadata is defined or displayed.
3. Observe small inconsistencies or duplicated definitions.

Expected behavior

• Base network metadata should be defined once and reused everywhere.
• Chain name, chainId, explorer URL, and related metadata should be consistent across the site.
• Future network changes should require minimal updates.

Additional info

Proposed Solution

• Introduce a single source of truth for Base network metadata (e.g. networks.ts).
• Export canonical definitions for Base Mainnet and Base Sepolia (chainId, name, explorer URLs).
• Refactor existing usages to import from the shared module.

Environment

No response