Add SDK Inspector panel with real-time call visualization #7
Merged
Conversation
…r optimizations - SDK Inspector: new shared infrastructure (store, types, components) in shared-utils/inspector and shared-components/inspector with lazy-loaded panel, phase grouping, annotations, and badges - Instrument all SDK calls in example 03 with logSDKCall wrappers across all 4 phases (Setup, Estimation, Transfer, Tracking) - Optimize transfer phase: cache estimation results, pass remoteToken from PoolInfo to skip redundant registry lookups (11 → 5 calls) - Harden ChainContext: dedup concurrent getChain calls, error cooldown, phase-aware logging - Switch tracking hooks to sequential timeout-based polling to prevent connection exhaustion - Tune polling intervals (balance 15s, rate limits 30s, message status 15s initial / 60s max) - Improve rate limit display: card styling, taller progress bars, section label - Add SDK Inspector README section explaining how to read through instrumented code - Fix EVM fee token: use 0n native value when paying with ERC-20
|
👋 aelmanaa, thanks for creating this pull request! To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team. Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks! |
SyedAsadKazmi
approved these changes
Mar 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces several improvements and new features to the multichain bridge dapp, focusing on enhanced developer experience and UI clarity, especially around SDK call inspection and rate limit displays. The most significant change is the addition of an SDK Inspector panel, which provides real-time visualization and educational annotations for all SDK calls made during the bridge flow. Additionally, the bridge form and pool info components are updated to better handle and display remote token information, and the rate limit UI receives a visual overhaul for improved clarity.
SDK Inspector Integration and Instrumentation:
Bridge Flow and Remote Token Handling:
remoteTokeninformation between components, ensuring accurate cross-chain token mapping and user feedback. [1] [2] [3] [4] [5]PoolInfocomponent to reportremoteTokenchanges to its parent via a callback, enabling the bridge form to use this information in transfers. [1] [2] [3]UI/UX Improvements:
Developer Experience and Documentation:
Code Quality and Maintainability:
These changes collectively make the bridge dapp more transparent and educational for developers, while also improving the user interface and reliability of cross-chain transfers.