.png%3Falt%3Dmedia%26token%3Dbac8f114-f7a7-4e88-8396-75aa9cbef3e2){kind=spacer}
.png%3Falt%3Dmedia%26token%3Dbac8f114-f7a7-4e88-8396-75aa9cbef3e2){kind=spacer}
Storage
As more blocks are added to the blockchain, chain data also pile up. Chain data are necessary for node operation, so they are stored in the node storage as a data structure called trie, and ultimately in a database called LevelDB. So with more blocks, comes more chain data in the storage, along with increasing cost. Klaytn, therefore, provides a feature called State Migration that allows you to reduce the amount of required storage space.
State Migration targets state tries, which comprise most of the chain data. It deletes state trie nodes that are not required for processing new blocks. It only leaves the state trie nodes that are reachable from the state trie root of a specific block. After State Migration, you are only left with the latest data required for node synchronization, consisting of state trie nodes of the target block as well as newly added blocks.
Note that a node can't read old states from blocks previous to the target block after State Migration. In other words, you can't return the balance from an old block number using the
klay_getBalance API.More details on the mechanism of State Migration can be found below: Klaytn v1.5.0 State Migration: Saving Node Storage Klaytn State Migration: An Efficient Way to Reduce Blockchain Data
To use State Migration, please refer to the documentation on admin APIs.
admin_startStateMigration lets you start State Migration, admin_stateMigrationStatus allows you to check the Migration status, and admin_stopStateMigration allows you to stop the process.Last modified 6mo ago