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
Is your feature request related to a problem? Please describe.
Currently, we only query how much INTR was staked in total. However, it is possible to stake both liquid and unvested INTR.
This makes it impossible to check how much of the actual liquid supply has been staked. This metric is important to understand the attractivity of staking as a product and user behavior (unvested tokens "mess" this up because there is nothing else users can do with these unvested tokens).
Describe the solution you'd like
Add a query to compute how much vested (i.e., liquid) INTR has been staked.
Note: unvested = cannot be claimed. The query should exclude tokens that are theoretically vested but have not yet been claimed yet (users must manually call vesting.claim() to actually make the vested share of tokens transferable in their account).
Describe alternatives you've considered
None
Additional context
Note that storage keys for user accounts are different for each pallet. This is probably a non-issue for squid but adding just in case - this is how to convert storage keys to actual accounts in JS:
Is your feature request related to a problem? Please describe.
Currently, we only query how much INTR was staked in total. However, it is possible to stake both liquid and unvested INTR.
This makes it impossible to check how much of the actual liquid supply has been staked. This metric is important to understand the attractivity of staking as a product and user behavior (unvested tokens "mess" this up because there is nothing else users can do with these unvested tokens).
Describe the solution you'd like
Add a query to compute how much vested (i.e., liquid) INTR has been staked.
Note: unvested = cannot be claimed. The query should exclude tokens that are theoretically vested but have not yet been claimed yet (users must manually call vesting.claim() to actually make the vested share of tokens transferable in their account).
Describe alternatives you've considered
None
Additional context
Note that storage keys for user accounts are different for each pallet. This is probably a non-issue for squid but adding just in case - this is how to convert storage keys to actual accounts in JS:
storage key (in this case) is basically [pallet, itemName, mapKey]
hence key.args[0] to get the mapKey - the account
The text was updated successfully, but these errors were encountered: