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
Proposed is an evolution of the Storage Fee charging scheme where a category of storage fee (dubbed "bytes deposit") is charged and refunded according to the number of bytes a state item itself occupies in the current state, in addition to the existing "slot deposit" which reflects the storage impact imposed by a individual state item via the authenticated data structures.
Specifically, the legacy "free quota" mechanism which heavily punishes updating a large state item is removed.
The updated scheme aligns better with the reality of disk space consumption by the transactions hence serves as a better economic benchmark for the developers to optimize the cost of transactions.
AIP Discussion
Summary
Proposed is an evolution of the Storage Fee charging scheme where a category of storage fee (dubbed "bytes deposit") is charged and refunded according to the number of bytes a state item itself occupies in the current state, in addition to the existing "slot deposit" which reflects the storage impact imposed by a individual state item via the authenticated data structures.
Specifically, the legacy "free quota" mechanism which heavily punishes updating a large state item is removed.
The updated scheme aligns better with the reality of disk space consumption by the transactions hence serves as a better economic benchmark for the developers to optimize the cost of transactions.
Read more about it here: https://github.com/aptos-foundation/AIPs/blob/main/aips/aip-65.md
The text was updated successfully, but these errors were encountered: