8000 Transient issue with displaying time to unstaking · Issue #516 · sudoblockio/icon-tracker-frontend · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Transient issue with displaying time to unstaking #516

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
robcxyz opened this issue Jan 8, 2025 · 2 comments
Open

Transient issue with displaying time to unstaking #516

robcxyz opened this issue Jan 8, 2025 · 2 comments

Comments

@robcxyz
Copy link
Contributor
robcxyz commented Jan 8, 2025

https://tracker.icon.community/address/hx06fbca6526684c9727218ea5532f9110395fc3ca

User claims to have not been bonding (and doesnt know what that is).
Unstaked their ICX 7 days ago, but the tracker is still showing around 7days until the unstaking block.
Is this a display issue on the tracker or is something else amiss, surely the unstaking timeline isnt now 14 days.

This should not be the case as unstaking time should be a total of 7 days, not 14. At the time the tracker looked like it was showing the wrong date which is generally calculated off estimates from the block height. Double check this by doing a Tx on mainnet and seeing how the unstaking time is estimated.
@athoifss
Copy link
Contributor

Time to unstake is calculated as remaining blocks times two and we get remainingBlocks from the 'getStake' rpc.
Did a tx and getting unstake time as 7 days. One way this could happen is if the RPC is returning the wrong remainingBlocks? @robcxyz

@robcxyz
Copy link
Contributor Author
robcxyz commented Jan 28, 2025

@athoifss - RPC is always right - so lets not doubt that and keep this open. If we can observe this / reproduce then can do but doubting RPC calls is likely not what we want to spend time on

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@robcxyz @athoifss
0