Stellar (XLM) to Remove SQL Database Support for Ledger State in Version 22.1

In a significant development for the Stellar (XLM) blockchain community, the upcoming release of stellar-core version 22.1 will see the removal of SQL support for most ledger state and transaction history, according to Stellar. This change marks a pivotal shift in how Stellar will manage its database configurations moving forward.

Details of the Transition

With the release of stellar-core 22.1, several SQL tables utilized for maintaining ledger state and transaction history will be completely dropped. Among the tables to be removed are ACCOUNT, TRUSTLINE, DATA, CLAIMABLE_BALANCE, LIQUIDITY_POOL, CONTRACT_DATA, CONTRACT_CODE, CONFIG_SETTING, TTL, TXSETHISTORY, and TXHISTORY. These tables have been deprecated for multiple releases, but users could still access them via the DEPRECATED_SQL_LEDGER_STATE configuration option.

Impact on Existing Configurations

The current version, stellar-core 22.0, will be the last to support the DEPRECATED_SQL_LEDGER_STATE configuration. Starting with version 22.1, this configuration option will be ignored, and the tables will be dropped unconditionally. By the time version 23.0 is released, this configuration option will be completely removed, reinforcing Stellar’s commitment to transitioning away from SQL databases.

Changes to Operational Flags

In addition to the removal of SQL support, the --in memory mode flag will also be deprecated in version 22.1. If this flag is set, it will be ignored, and the validator will automatically start in BucketListDB mode. This change aims to streamline operations and will see the complete removal of the --in memory flag in version 23.0.

These shifts are indicative of Stellar's evolving approach to blockchain infrastructure, focusing on enhancing efficiency and scalability. Stakeholders and developers within the Stellar ecosystem should prepare for these updates and adjust their systems accordingly to ensure seamless integration with the new version.