This repository was archived by the owner on Mar 11, 2025. It is now read-only.
token-2022: adjust PodAccount
initialized check
#6953
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
The method to determine if a particular
PodAccount
is initialized simply checkswhether or not the
state
field (AccountState
) is not equal to zero.However, this means that any number besides
0
is considered to be an initializedPodAccount
. This allows arbitrary data with size 165 to be considered a valid tokenaccount. For example,
&[5; 165]
registers as an initialized token account.Summary of Changes
Adjust the
is_initialized
method to explicitly check the two initializedAccountState
variants, rather than
!= 0
.