Emission amount returning negative values in Beldex API

[Tore-tto]

I noticed that the Beldex Explorer API is returning a negative emission amount, which seems incorrect. This may indicate a calculation bug or a data parsing issue in the backend.

Steps to Reproduce

1. Call the API endpoint:

   https://explorer.beldex.io/api/emission

2. Check the emission field in the response. You’ll see that it returns a negative number, which should not be possible.

The emission should always be a positive value, increasing over time based on Beldex emission rules.

Screenshot

[victor-tucci]

std::optional<std::tuple<int64_t, int64_t, int64_t>> result{{0, 0, 0}}

All three values (emission_amount, total_fee_amount, and burnt_beldex) are stored in signed 64-bit integers (int64_t). As the chain grows, these totals can exceed the maximum range of a signed 64-bit integer. Once the values overflow the signed limit, they wrap into the negative range, which is why the RPC exposes negative emission amounts.

These fields represent monetary quantities that are always non-negative, so using a signed integer is incorrect. The correct fix is to change the accumulator types to unsigned 64-bit integers (unsigned long long ), which support a much larger range and correctly represent emission, fees, and burnt amounts.

Switching the tuple to:

std::optional<std::tuple<unsigned long long, unsigned long long, unsigned long long>> result{{0ULL, 0ULL, 0ULL}}

#179

[victor-tucci]

merged... bf8bb00