fetch unstaking tokens

[gonzamontiel]

Closes #176

[netlify]

✅ Deploy Preview for rococo-souffle-a625f5 ready!

Name	Link
🔨 Latest commit	79a9a5a
🔍 Latest deploy log	https://app.netlify.com/sites/rococo-souffle-a625f5/deploys/64cb51ef5193310008c2e9a9
😎 Deploy Preview	https://deploy-preview-218--rococo-souffle-a625f5.netlify.app/
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[ebma]

Looks good overall but I still find the terminology confusing.
Why are we saying 'Unbond' in one case and 'unboard' in another. Shouldn't we make that consistent? It's the same thing afterall @prayagd?
Also, Kilt is using a different terminology, ie. they phrase it as 'unlocking unstaked tokens', see here.

[prayagd]

Why are we saying 'Unbond' in one case and 'unboard' in another. Shouldn't we make that consistent? It's the same thing afterall @prayagd?

@ebma Yes they are the same, its a typo. @gonzamontiel Can we make it unbonding? I find the KILT phrase too long.

[gonzamontiel]

Looks good overall but I still find the terminology confusing. Why are we saying 'Unbond' in one case and 'unboard' in another. Shouldn't we make that consistent? It's the same thing afterall @prayagd? Also, Kilt is using a different terminology, ie. they phrase it as 'unlocking unstaked tokens', see here.

Yeah I agree, it's a nice chance for changing that for good. I like 'unlocking unstaked tokens', it is clearer.

[gonzamontiel]

Why are we saying 'Unbond' in one case and 'unboard' in another. Shouldn't we make that consistent? It's the same thing afterall @prayagd?

@ebma Yes they are the same, its a typo. @gonzamontiel Can we make it unbonding? I find the KILT phrase too long.

All this time it has been a typo? lol
I see this other issue is connected though, and it's about naming, so I'll resolve this conversation here.