Protocol 23 introduces CAP-67 events that can emit data for both new and historical ledgers. Operators must enable two new core flags—EMIT_CLASSIC_EVENTS and BACKFILL_STELLAR_ASSET_EVENTS—to build a complete unified events feed covering classic operations and Soroban transactions.
Protocol 23 brings a significant upgrade to Stellar's event system through CAP-67, enabling the emission of event data not just for new ledgers but also retroactively for past ledgers. The article outlines two new configuration flags that operators must explicitly enable: EMIT_CLASSIC_EVENTS (to include fee events and classic operation token movements) and BACKFILL_STELLAR_ASSET_EVENTS (to generate events for all historical ledgers from genesis onward). Three upgrade paths are presented, with the recommended approach requiring full-history re-ingestion to achieve complete coverage. The benefits include comprehensive analytics, uniform API schemas, and consistent user experience across wallets and exchanges, though trade-offs include increased database size (~2.5 GB per day) and storage requirements (~7TB uncompressed). The guide provides operators with clear next steps for implementation.
