Skip to content

Conversation

@chasefleming
Copy link
Member

Closes #???

Description


For contributor use:

  • Targeted PR against master branch
  • Linked to Github issue with discussion and accepted design OR link to spec that describes this work
  • Code follows the standards mentioned here
  • Updated relevant documentation
  • Re-reviewed Files changed in the Github PR explorer
  • Added appropriate labels

@github-actions
Copy link

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@codecov-commenter
Copy link

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Comment on lines +67 to +69
// For custom networks, we can't validate the address format without knowing the chain ID,
// so we allow all addresses
return true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like we could try to use something like GetNetworkParameters chain ID for some stronger validation here in the future, but probably not strictly necessary for this fix.

@chasefleming chasefleming merged commit 37485d4 into master Dec 29, 2025
9 checks passed
@chasefleming chasefleming deleted the cf/fix-network-case branch December 29, 2025 03:57
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.

5 participants