Why expires timestamp is keep changing on node running on mainnet v4.0.1

General
1

Algo team,

I am running a node on mainnet v4.0.1. In Accounts/Keys section, I noticed “Expires” timestamp is keep changing after a minute or two. Any idea why?.
Please find attached the screenshots

issue1
issue11776×220 26 KB

2

Hi @AlgoUser1, for faster replies about node running, please join the #node-runners channel on our Discord server https://discord.com/invite/algorand.

4

Hi @AlgoUser1

The expiration time is actually specified in rounds (you can find your specific expiration round if you press ENTER in that screen)

Since a “round” is not a meaningful unit of time for most humans, we try to estimate when this will happen based on the average round time of the last 100 blocks (which fluctuates, as it is dynamically adaptive by design)

Your expiration round/date is far enough in the future that a tiny change in the round time creates large differences in the projected expiration time

E.g. over the course of 30 days, a difference in average round time of 2.8s vs 2.81s will result in a 7.2 hour change in the estimated time 86400 * 30 * 0.01 / 3600 = 7.2

1 Like
5

Thank you, Adriana. I joined discord and issue got resolved.

1 Like
6

Happy days! My pleasure.