2.5 million USD (about 350k) atoms between stride and the hub
I should not need to be writing this.
But nobody else did.
There are 2.5 million USD of atoms (about 350k) stuck between stride and the Hub.
Most likely the problem has something to do with gas configuration that changed when the fee market was added to the hub.
Certainly there’s been more than enough time to inform users of this.
Neither the hub team nor stride bothered to do so.
x.comquestions
- When was this issue known?
- Was stride informed of changes to gas?
- Why has there been no information provided to users?
Hey Jacob! Thanks for raising this. I mentioned to you this morning that I needed to chat with our eng team to get a bit more context. I have that context now and we’re working on a broader post with all of the details, but here’s some background: x.com Vishal | Stride (@shellvish) on X @shellvish @AnonNgmi @interchainriley @WhisperNode We’re writing up a more thorough explanation right now, but the gist of the issue: - Hub gas limit was 100M per block - Latest Hub upgrade added x/feemarket, which limits individual txs to 30M gas. The block gas limit is unchanged, but ICA messages are now limited to 30M gas - and a TLDR for non-technical folks: x.com Riley | Stride (@interchainriley) on X @interchainriley @AirdropGlideapp Quick explainer for anyone wondering: All unbondings are safe and will process, some are just delayed due to an upgrade on the Cosmos Hub that interacted with the handling of LSM shares. Most unbondings processed normally and all funds are safe, this only delayed some users' We definitely weren’t trying to hide anything, in this case we’ve been in touch with…
Excerpt (1195 of 1574 characters). Read the whole post on the forum ↗
But impacted users were every staked atom user, if they tried to unbond.
Not quite. It only impacted certain undelegation batches that involved an excess of LSM liquid stakes. Here’s the explanation from Vishal’s tweet:
Normally, this wouldn’t be an issue, but Stride accepts LSM delegations on the Cosmos Hub. The way this works today is Stride accepts the delegations, then rebalances+undelegates afterwards towards Stride’s target delegations (subject to standard Cosmos SDK x/staking restrictions). Depending on the LSM delegations that Stride has, unbondings can stochastically fail. In particular, sometimes Stride will try to unbond from 35-40+ validators, which consumes > 30M gas
Most undelegations processed as normal. The larger impacted users reached out to us and we’ve been talking with them directly.
And the smaller impacted users?
What was done to warn them?
Like this guy
x.comLincoin 🛡️ (@lincoin_x) on X
Here is a good example of a footgun warning, from Penumbra
x.compenumbra 🌘 (@penumbrazone) on X
See how it leads people away from danger?
I think that is a good approach.
Because there was absolutely legitimate danger.
People really do not like to be suddenly unable to access their assets.
And that’s really very sensible.
Yet the dashboard shows: “all good yo”
That’s a huge footgun left for users. It does not need to be there.
Anyone who was impacted and opened up a ticket has gotten help from our support team (including, AFAIK, the user that made this tweet)!
I definitely can appreciate the point that we should have posted this on twitter or the status page, and we’ll be adjusting the way we handle these comms to do so moving forward. Re: the status page, this is due to a missing flag that we’ll be adding that should reflect this issue in the future.
Informal was aware of this problem, and did not inform the user community?
I can’t really speak for informal on this, I just have context on the actions we’ve taken at Stride to help get these edge-case undelegations “unstuck” (so to speak).
Do you think that stride has been given stable platform services ?
How about that peg? We have invested so heavily in it But now, statom isn’t redeemable in some cases. And it has been that way for a month. But the community only learned of this today. Except some knew much earlier. Why was I told today that stride is not broken on the hub? I don’t get it, the present situation is fully incompatible with that claim. Since there are users who are aware of this, and users who aren’t, is it possible the information was bandied about in a privileged manner that allowed some access to the exits faster than others? That… Seems certain to me. @RoboMcGobo are you saying that this condition existed, and Stride did not speak to informal? …well that would be quite bad, deeply irresponsible even. Otherwise, I think it is essential for atom holders to know when informal knew that their upgrade had broken redeemability. @jtremback so… When did you learn that 330k statom were stuck? What did you do to address it? Did stride inform you? Why can’t I get answers to basic questions? x.com @ I am not a security researcher. …at least that’s a really popular claim at informal. Why did I…
Excerpt (1196 of 1653 characters). Read the whole post on the forum ↗
So, let’s see what’s happened:
I spend a full day finding out what’s up
Total silence from icformal and stride on the issues I think matter.
Status page be like:
That doesn’t make sense.
Why does no one care that users are losing their shirts?
x.comJacob Gadikian 🐳⚛️⚗️ (@gadikian) on X
I want to know:
- Did informal ask stride not to say anything? (there’s a lot of precedent here)
- When did stride speak to informal? (If they did not, well, yeah that would be strides fault big time)
- What has informal done to help?
- Why not param change gov prop on the hub, weeks ago? (I am NOT blaming stride here. Issue is solvable on the hub side, with ease, without guesswork)
I think that these are very reasonable questions to be asking at this time.
jacobgadikian:I should not need to be writing this.
But nobody else did.
Keep up the work, Jacobgadikian. Your work is extremely appreciated by, if not all, other communities of the Cosmos Hub.
Just wanted to post this so that everybody is aware, yesterday the stride status page did actually show that the funds were stuck.
It now shows all systems operational. If anyone has funds stuck, you should probably say so here, but as far as I know, stride is now working again.
Yesterday:
Today:
When there are issues like these, it is important that the community is made aware of them, because their assets can get stuck.