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
After a recent update, Realio Network fails when restaking. This seems to be caused by the way REStake handles autocompounding - we send a single Delegate message for the amount the user has pending in rewards. Cosmos SDK usually auto-claims the pending rewards and allows these to be delegated in the same transaction; this works for all Cosmos SDK chains to date, and was reportedly working for Realio until their latest update.
After their update, the REStake action now fails with an error <available balance> is smaller than <reward balance>: insufficient funds, since we tried to delegate the <reward balance> but the user only has <available balance>, and autoclaiming in one transaction doesn't seem to be working anymore.
This was raised by STAVR validator, and an example delegator causing this to fail is realio12y45ayntynr07juslvy55v35cnz9hy32kp8qdj
I will raise an issue on the Realio repo and link this issue to find out more information.
The text was updated successfully, but these errors were encountered:
After a recent update, Realio Network fails when restaking. This seems to be caused by the way REStake handles autocompounding - we send a single Delegate message for the amount the user has pending in rewards. Cosmos SDK usually auto-claims the pending rewards and allows these to be delegated in the same transaction; this works for all Cosmos SDK chains to date, and was reportedly working for Realio until their latest update.
After their update, the REStake action now fails with an error
<available balance> is smaller than <reward balance>: insufficient funds
, since we tried to delegate the<reward balance>
but the user only has<available balance>
, and autoclaiming in one transaction doesn't seem to be working anymore.This was raised by STAVR validator, and an example delegator causing this to fail is
realio12y45ayntynr07juslvy55v35cnz9hy32kp8qdj
I will raise an issue on the Realio repo and link this issue to find out more information.
The text was updated successfully, but these errors were encountered: