Stellar core developers discuss three approaches for storing scalable network configuration settings in dedicated ledger entries instead of the ledger header, with approach two using Soroban emerging as the preferred option for simplicity and flexibility.
In this technical discussion, Stellar developers evaluate three approaches for managing network configuration settings that are too large for the current ledger header mechanism. Approach one uses overlay distribution with validator voting on configuration hashes; approach two leverages Soroban to store settings as ledger entries with user-submitted transactions; approach three uses a new Stellar classic operation with XLM withdrawal to prevent spam. The team converges on approach two as simplest to implement, reusing existing Soroban metering mechanics. Key considerations include validator coordination, security implications of configuration changes, potential for DAO governance of network parameters, and whether to split the invoke host function into dedicated operations. The discussion also covers state expiration and archival mechanisms, introducing three storage types: unique storage with proof requirements for security-critical data, recreatable storage for flexible data like balances, and temporary storage for ephemeral entries.