[Bug]: Native Asset indexing and endpoint response has issues that need correcting.

[stevenj]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Native Assets names are 32 byte maximum binary fields.
The index stores them as strings, not strings.
The endpoint response also does not consider that each asset hash (id) can have multiple asset names associated with it.
Currently it is only handling one asset name per asset hash.
The Value of the asset is also restricted to u64, but it can be in the range:
minInt64 = -9223372036854775808
maxInt64 = 9223372036854775807

Expected Behavior

To fix:

1. The Asset name needs to be stored in the index as binary bytes.
2. Multiple asset names per asset id need to be properly reported.
3. The asset name in the response needs to be converted to a string using the AssetName types From<Vec<u8>> implementation.
4. Change the value for Native assets to be i128, to handle the extended range they support.

Project

Backend

What operating system are you seeing the problem on?

macOS, Linux, Windows

What browsers are you seeing the problem on?

Not Applicable

Relevant log output

No response

Anything else?

No response

Code of Conduct

• I agree to follow this project's Code of Conduct