fix: formatting issue for negative tokens

[paanSinghCoder]

Summary

Issue:

• Values like -595 were shown as -,595 because the minus sign was included in the length used for comma placement, so a comma was inserted after the sign.
• Very big values loose accuracy as Number() is used.

Fix:

• Use BigInt() to convert the string to a bigInt without loosing the accuracy.
• Implement num.toLocaleString(); to format the number.
• Get locale from frontier config. Defaults to undefined.

Test Plan

• Manually tested on local
• Build and type checking passes

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
frontier	Ready	Preview, Comment	Feb 3, 2026 0:25am

[coveralls]

Pull Request Test Coverage Report for Build 21630079402

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 37.983%

---

Totals
Change from base Build 21623958951:	0.0%
Covered Lines:	15956
Relevant Lines:	42008

---

💛 - Coveralls

[rohanchkrabrty]

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number/toLocaleString

Let's use this to format the number.

const n = 34523453.345;
console.log(n.toLocaleString());    // "34,523,453.345"