This proposal seeks community approval to update the on-chain token metadata to correct the token’s decimals field. The token currently displays 0 decimals, which is incorrect and causes UX, accounting, and integration issues across wallets, explorers, and dApps. This update aligns the canonical metadata with the token’s intended specification on Injective-List to ensure consistent display and interpretation across the ecosystem.
- The incorrect decimals break downstream integrations (indexers, explorers, wallets, DEX UIs, portfolio trackers) that rely on on-chain metadata.
- The issue creates friction for partners building on Injective and for exchanges seeking accurate display and accounting.
- Fixing the decimals ensures consistent UX, accurate accounting, and simplifies partner integrations.
Actions:- By voting YES on this proposal, you support updating the token’s on-chain metadata to set the correct
decimals value in alignment with Injective-List. - By voting NO on this proposal, you do not support updating the token’s decimals and prefer retaining the current (incorrect) value of
0. - By voting NO WITH VETO, you consider this proposal spam/irrelevant/malicious and support burning the 500 INJ deposit, provided such votes exceed ⅓ of total voting power.
- By voting ABSTAIN, you wish to contribute to quorum while formally declining to vote either for or against the proposal.
Disclosure: I am a member of the Injective Labs team.