fix: correct decimals for MOLLARS and imgnAI (9, not 18)#645
Closed
RAVIKUMAR96 wants to merge 1 commit into
Closed
fix: correct decimals for MOLLARS and imgnAI (9, not 18)#645RAVIKUMAR96 wants to merge 1 commit into
RAVIKUMAR96 wants to merge 1 commit into
Conversation
On-chain decimals() for these tokens is 9, but the custom list had 18, which overrode the correct value and broke exchanges (reported by Tangem). - MOLLARS 0x385d65ed9241e415cfc689c3e0bcf5ab2f0505c2 (Ethereum): 18 -> 9 - imgnAI 0xA735A3AF76CC30791C61c10d585833829d36CBe0 (Ethereum): 18 -> 9 - imgnAI 0x18e692c03de43972fe81058f322fa542ae1a5e2c (Base): 18 -> 9 Verified via eth_call decimals() (0x313ce567) on Ethereum and Base RPCs. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Hi @RAVIKUMAR96 — thanks for contributing! 🙏 We don't accept pull requests from forks on this repo. Instead, please open an issue using one of these templates:
An internal LI.FI team member will pick it up and turn it into a PR within a few working days. Closing this PR for now — see the README for the full process. |
RAVIKUMAR96
commented
Jul 10, 2026
RAVIKUMAR96
left a comment
RAVIKUMAR96
left a comment
Contributor
Author
There was a problem hiding this comment.
Updating Decimals
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
1 participant
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.
Summary
Corrects the
decimalsfield for 3 token entries that were set to18but are actually9on-chain. The wrong value in this custom list overrides the correct on-chain value in the backend pricing pipeline, which broke exchanges for these tokens.Reported by Tangem: users were unable to perform exchanges due to the decimals mismatch.
0x385d65ed9241e415cfc689c3e0bcf5ab2f0505c20xA735A3AF76CC30791C61c10d585833829d36CBe00x18e692c03de43972fe81058f322fa542ae1a5e2cVerification
On-chain
decimals()(selector0x313ce567) returns0x...09= 9 for all three:Notes
PATCH /v1/tokenre-fetch does not fix this, becauseCustomListOraclemetadata overrides the fetched decimals — the correction has to happen in this list.Made with Cursor