@lena:
The importance of the account is 0. The reason why nodes like hugealice show a non-zero importance is as follows:
- When a node is configured with default configuration, after restart of the node and chain loading the poi importance is calculated with current height that the node’s chain has. Since the account did not have a balance that makes it eligible for importance calculation, the importance of the account is not set which means it has 0 importance.
- If a node is configured with the historical account data flag set (like the hugealice node), then upon restart and chain loading the poi calculation is done every 359 blocks and since the account in question once had a balance that made it eligible for importance calculation, it receives importance values during chain loading. At a later point, when you transferred the balance to another account, the account is not eligible for importance calculation any more. But the old importance is not zeroed out and the /account/get request just returns the last non-zero importance it had (that is for a height of ~1690000).
So that explains the different values seen in the request. Now you might ask, if the account can harvest since some nodes have a non-zero importance for the account in the request. The answer is *no. The non-zero importance seen in the response is for a very old height and when NIS internally queries the importance, it sees zero for the account at current height (no matter how the node is configured) and therefore does not let the account harvest.
