feat: account serialization overhaul #12794
Open
+249
−348
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.
Change
Account
to be enum and use different representations for serde and borsh ser/deser:SerdeAccount
is introduced for serde to maintain backward and forward compatibility. PreviouslyAccount
struct was directly annotated to support serde, we are opting out of this.BorshVersionedAccount
is introduced for borsh serialization. Accounts in old format are serialized directly asAccountV1
. Note that we continue serializing in old format when possible to avoid 16 bytes overhead of sentinel padding.Account::SERIALIZATION_SENTINEL
hack is preserved for borsh serialization as I could not find a better way to handle backward compatibility.This is part of #12716, in a separate PR global contracts related fields will be added as part of Account.