Stellar’s Bell Protocol 30 proposal includes a technical change that may look small but matters for future performance work: recording ledger close times with millisecond precision. CAP-88 updates the ledger timing format so the network is no longer constrained by a timestamp representation that records only whole seconds.
The current timing limitation
Stellar records each ledger’s close time in whole seconds. This is sufficient when ledgers close several seconds apart, but it limits the protocol’s ability to target intervals finer than one second. As the network explores faster ledger operation, the timestamp format itself becomes a constraint.
What CAP-88 changes
The proposal changes the ledger header format to support millisecond timing. It is a protocol-level prerequisite for future changes that may target shorter close intervals. Stellar notes that the existing closeTime field continues to report whole seconds, while the new format provides more precise timing information in the ledger structure.
Does it make Stellar faster immediately?
No. CAP-88 alone does not make ledgers close faster than the current interval. It removes a representation barrier so later protocol work can safely experiment with finer timing. The Stellar Core team says it is already using the capability to test faster ledger close times on experimental branches. Those experiments should not be confused with a mainnet performance guarantee.
Why precision matters in distributed systems
Distributed networks need a shared way to record events and agree on ordering. More precise timestamps can support tighter timing targets, monitoring and analysis, but they do not replace consensus. Validators must still agree on ledger contents and follow the protocol’s rules. Timing changes must be tested against network conditions, clock behavior and the risk of inconsistent observations.
Developer preparation
Because the ledger header format changes, software that decodes raw ledger data needs attention. Stellar advises SDK users to update compatible versions before the Protocol 30 votes. Teams that parse ledger data directly, including indexers, explorers and analytics pipelines, should update their XDR definitions. A parser that assumes the old format could fail to interpret new ledger data correctly.
Potential ecosystem benefits
Faster ledger close times could improve the responsiveness of payment and application experiences, provided the network can maintain reliability and validator participation. For businesses, shorter settlement intervals may help services that depend on rapid confirmation. But real-world user experience also depends on wallet design, RPC infrastructure, application logic and the number of confirmations a service requires.
Conclusion
CAP-88 is infrastructure groundwork rather than an immediate speed boost. It changes how ledger timing can be represented, allowing future protocol upgrades to target finer intervals. Developers should prepare their data tooling, while users should wait for official activation details before expecting different confirmation times.