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
For example, if an account starts in an uninit state and then a transaction transfers all its balance out, leaving the final balance as 0, the account’s state changes from uninit to nonexist. However, in PostgreSQL, the latest_account_states remains in the uninit state, and the balance has not changed; it still shows the previous balance (it should be 0).
I checked the code, and when the account is in a nonexist state, no data is retrieved from the block, and the processing of the account will be skipped in this line of code , causing the account_state in a nonexist state not to be inserted.
The text was updated successfully, but these errors were encountered:
For example, if an account starts in an uninit state and then a transaction transfers all its balance out, leaving the final balance as 0, the account’s state changes from uninit to nonexist. However, in PostgreSQL, the latest_account_states remains in the uninit state, and the balance has not changed; it still shows the previous balance (it should be 0).
I checked the code, and when the account is in a nonexist state, no data is retrieved from the block, and the processing of the account will be skipped in this line of code , causing the account_state in a nonexist state not to be inserted.
The text was updated successfully, but these errors were encountered: