Regarding the potential numeric overflow issue when querying asset values

[davidapp]

Background

Rationale

API example:
https://nile.trongrid.io/wallet/getaccount?address=TQUsaH7DzTAPQEVsUvQsVyzvwqwT2p7WEm&visible=true

The returned value field is currently of numeric type, and its maximum value can reach the int64 limit.

When using JavaScript (e.g., with Axios or other HTTP clients) to send requests, the response body is parsed by default using JSON.

parse(). This automatically converts all numeric values into the Number type, which has a maximum safe integer limit of 2^53 - 1. Therefore, all JavaScript-based integrations may encounter this issue.

Specification

For the returned value field, add an additional “value_string” field that returns the value as a string type to avoid precision loss.

Test Specification

Scope Of Impact

Implementation

Do you have ideas regarding the implementation of this feature?

Are you willing to implement this feature?

[bladehan1]

You can use a third-party library like json-bigint
This library can parse large integers as strings or BigInt, preserving exact precision.

ar JSONbig = require('json-bigint');
 
var json = '{ "value" : 9223372036854775807, "v2": 123 }';
console.log('Input:', json);
console.log('');
 
console.log('node.js built-in JSON:');
var r = JSON.parse(json);
console.log('JSON.parse(input).value : ', r.value.toString());
console.log('JSON.stringify(JSON.parse(input)):', JSON.stringify(r));
 
console.log('\n\nbig number JSON:');
var r1 = JSONbig.parse(json);
console.log('JSONbig.parse(input).value : ', r1.value.toString());
console.log('JSONbig.stringify(JSONbig.parse(input)):', JSONbig.stringify(r1));

[lxcmyf]

@davidapp
You can try to use other compatible third-party libraries to parse the large number fields.

[warku123]

Adding a new value_string field might actually break existing integrations. Also, doubling up on value fields increases payload size for everyone, not just JavaScript clients.

Using json-bigint on the client side is a safer approach — it solves the precision issue without forcing changes on all API consumers.