Skip to content

feat(#231): add testnet asset configuration consistency check - #247

Merged
karagozemin merged 1 commit into
karagozemin:masterfrom
CemAyyildiz:fix/issue-231-testnet-asset-consistency
Aug 31, 2026
Merged

feat(#231): add testnet asset configuration consistency check#247
karagozemin merged 1 commit into
karagozemin:masterfrom
CemAyyildiz:fix/issue-231-testnet-asset-consistency

Conversation

@CemAyyildiz

Copy link
Copy Markdown

Closes #231

Summary

  • Add read-only check-testnet-assets.mjs script with field-level mismatch reporting
  • Add passing and mismatch fixture tests
  • Wire npm script check:testnet-assets
  • Align frontend Sepolia USDC (networks.ts sepolia.testToken, TokenSelector.tsx) with SDK canonical mapping (0xa0b86a33e6417c4fd30ad9d05d6b9b7cd6dd11b)
  • Add @oversync/sdk workspace dependency to coordinator so backend services stay tied to canonical asset mappings

Testing

  • node scripts/check-testnet-assets.mjs
  • pnpm --filter @oversync/sdk test

Made with Cursor

@vercel

vercel Bot commented Aug 31, 2026

Copy link
Copy Markdown

@CemAyyildiz is attempting to deploy a commit to the karagoz's projects Team on Vercel.

A member of the Team first needs to authorize it.

@drips-wave

drips-wave Bot commented Aug 31, 2026

Copy link
Copy Markdown

@CemAyyildiz Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

@karagozemin
karagozemin merged commit 33b718c into karagozemin:master Aug 31, 2026
1 check failed
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.

[SCF high][easy] Add testnet asset configuration consistency check

2 participants