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
It would be highly beneficial for HashScan to display whether an account is frozen for HTS tokens. Currently, if a token has a freeze key and an account holding that token is frozen, the account holder cannot send or receive the token. However, there is currently no way to determine if an account is frozen for a specific token unless a transaction is attempted. This limitation can cause confusion and prevent users from understanding their token's status without trial and error.
Proposed Solution:
Add a feature to HashScan that displays whether an account is frozen for specific HTS tokens.
Ideally, this information would be available on the account’s page, showing the status for each token it holds.
Additional Context:
Kabuto Explorer previously provided this feature, but it has been shut down. This capability is crucial for users managing multiple tokens and ensuring smooth transactions.
@mgarbs - The mirror-node API does not provide any information related to the frozen state of tokens for an account.
I currently do not see any way for HashScan to display this (I believe Kabuto Explorer was based on their own mirror node).
Would you mind logging an enhancement on the mirror node REST API if this support is required?
@mgarbs - Correction, I was thinking about the fact the TOKEN FREEZE transaction information we get does not indicate which token is concerned.
We can indeed obtain the freeze status of a token for an account from the /api/v1/accounts/{id}/tokens API.
svienot
removed
the
dependency
Feature requesting an enhancement in a dependency (typically the mirror-node API)
label
Aug 20, 2024
Description:
It would be highly beneficial for HashScan to display whether an account is frozen for HTS tokens. Currently, if a token has a freeze key and an account holding that token is frozen, the account holder cannot send or receive the token. However, there is currently no way to determine if an account is frozen for a specific token unless a transaction is attempted. This limitation can cause confusion and prevent users from understanding their token's status without trial and error.
Proposed Solution:
Additional Context:
Kabuto Explorer previously provided this feature, but it has been shut down. This capability is crucial for users managing multiple tokens and ensuring smooth transactions.
@nubeasado
The text was updated successfully, but these errors were encountered: