fix: correct WBTC and vbWBTC decimals to 8 on X Layer and Ternoa#833
Merged
Conversation
WBTC is an 8-decimal token. Two agglayer token-list entries declared 18 decimals, which made the bridge UI misrender every amount and balance by 10^10 (e.g. 1 vbWBTC showed as 10,000,000,000 WBTC): - X Layer (196) WBTC 0xea03...08e1 - Ternoa (752025) vbWBTC 0x593a...213e Both contracts report decimals() == 8 on-chain; corrected to match. A full 158-token on-chain decimals audit across all 11 chains found no other mismatches. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
py-zoid
approved these changes
Jun 26, 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.
What
Corrects the
decimalsfield on two agglayer token-list entries from18to8:0xea034fb02eb1808c2cc3adbc15f447b93cbe08e10x593A86cB824e0e3546fAE6bbC56e6f3f3EB6213E