You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is already an issue in ibc-go to add support for BigInt transfers. Right now, ibc-go supports u64. On solo machine, only u32 is supported because there is no way to store u64 values in SQLite and PostgreSQL using sqlx. Now that we don't maintain accounts and balances on solo machine, it'll be better to convert database type for amount to TEXT and convert u32 to u64 for mint and burn amounts.
The text was updated successfully, but these errors were encountered:
…#50)
Solution:
- Changed amount to `u64` and store it in database as `TEXT`. Fixes#49.
- Change database type from TEXT to BLOB/BYTEA and use little endian encoding to store u64
There is already an issue in
ibc-go
to add support forBigInt
transfers. Right now,ibc-go
supportsu64
. On solo machine, onlyu32
is supported because there is no way to storeu64
values in SQLite and PostgreSQL usingsqlx
. Now that we don't maintain accounts and balances on solo machine, it'll be better to convert database type for amount toTEXT
and convertu32
tou64
for mint and burn amounts.The text was updated successfully, but these errors were encountered: