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
Currently a string is used and converted to byte slice for token forwarding: []byte("forwarded packet succeeded")
This is a total of 26 bytes.
I propose maintaining parity with regular ibc transfers and storing a single byte for the result ack - since the result ack does not need to communicate any data but rather signal success.
As it exists today, osmosis db state contains something like 2.x GB of ack data on mainnet. This would be potentially upwards of 50GB if we used a similar size byte string in regular transfers.
This may seem like a small issue but at scale its impact is massive.
Summary
Currently a string is used and converted to byte slice for token forwarding:
[]byte("forwarded packet succeeded")
This is a total of 26 bytes.
I propose maintaining parity with regular ibc transfers and storing a single byte for the result ack - since the result ack does not need to communicate any data but rather signal success.
As it exists today, osmosis db state contains something like 2.x GB of ack data on mainnet. This would be potentially upwards of 50GB if we used a similar size byte string in regular transfers.
This may seem like a small issue but at scale its impact is massive.
see thread ref: #6574 (comment)
For Admin Use
The text was updated successfully, but these errors were encountered: