Skip to content

fix(chains): correct Sova block explorer default URL#4599

Open
esorense wants to merge 1 commit into
wevm:mainfrom
esorense:sova-block-explorer-url-typo
Open

fix(chains): correct Sova block explorer default URL#4599
esorense wants to merge 1 commit into
wevm:mainfrom
esorense:sova-block-explorer-url-typo

Conversation

@esorense
Copy link
Copy Markdown

What is this PR solving?

This PR fixes a typo in the Sova chain definition:

  • src/chains/definitions/sova.ts
  • blockExplorers.default.url was hhttps://explorer.sova.io
  • corrected to https://explorer.sova.io

This is a real correctness issue (not a design change).
The invalid scheme can break URL parsing and cause explorer-link checks/usages to fail.

Alternatives considered

  • Keep the current value and rely on consumers to handle malformed URLs.
    • Rejected: pushes a bad config downstream.
  • Add runtime normalization/fallback for malformed explorer URLs.
    • Rejected: unnecessary complexity for a single source typo.
  • Apply a minimal source fix in the chain definition.
    • Chosen: smallest, safest, and most maintainable change.

Reviewer attention

Please focus on:

  • The one-line change in src/chains/definitions/sova.ts.
  • Confirming no unrelated chain definitions were modified.

Documentation impact

No documentation changes are required (no API or behavior contract changes beyond correcting bad data).

Tests

No new tests were added because existing coverage already validates explorer URLs in test/scripts/chains.test.ts (blockExplorer.url check).
This change is intended to make Sova pass that existing path with a valid URL scheme.

@vercel
Copy link
Copy Markdown

vercel Bot commented May 12, 2026

@esorense is attempting to deploy a commit to the Wevm Team on Vercel.

A member of the Team first needs to authorize it.

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented May 12, 2026

⚠️ No Changeset found

Latest commit: 76ec2f5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant