osmosis-frontend
osmosis-frontend copied to clipboard
Pool 722, multiple Lock IDs and a misconfigured error code.
Myself, and a few users who bonded for 14 days in pool 722 had an issue where when we attempted to enable SFS, we would get a generic "internal" error. This error was broadcast on chain as a failed tx.
Through a little testing we were able to figure out some users had multiple lock IDs when attempting to enable SFS in this pool.
This was causing an out of gas error, however, that error message was never relayed. Significantly increasing the gas fixed this error and let users enable SFS successfully.
Assuming fixing the multiple lock IDs for some users isn't easily achievable, can we enable the proper "out of gas" error message for failures of this nature?
Root problem:
- Delegating on multiple locks requires more gas than suggested, perhaps related to multi msg.
- Out of gas error is returned from chain as
internalmessage. May be chain issue.
Good first issue if you're interested in working on multi msg tx gas estimations