Stellar CAP-88: Millisecond Ledger Times and Indexer Updates

Aayushi Shukla
Aayushi Shukla
Published:
Share:
Stellar CAP-88 millisecond ledger times illustration

Why Is Stellar CAP-88 Getting So Much Attention?

Stellar CAP-88 changes how the network marks time on each ledger. Instead of whole seconds, it’ll use milliseconds. It’s a small-sounding tweak, but wallet teams, blockchain explorers, and data providers are all checking their software this week.

The proposal is called Millisecond-Resolution Close Times. It comes with the Bell upgrade, also known as Protocol 30. Validators vote on it for the mainnet on November 23, 2026, at 17:00 UTC.

This guide covers what the change does, how millisecond ledger times work, why indexers need to pay attention, and where the limits are. It also keeps confirmed facts apart from guesses.

What Is Stellar CAP-88 and What Does It Change?

Right now, every ledger’s close time has to be at least one second later than the one before it. That rule puts a hard floor on how fast Stellar can close ledgers.

The proposal doesn’t change that old field. It adds a new millisecond field next to it. Why? Because changing the old field’s units would’ve broken explorers, SDKs, and smart contracts that read it as seconds.

Here’s what CAP-88 adds:

  • A new field called closeTimeMs stores the close time in milliseconds since the Unix epoch.

  • A new type, TimePointMilliseconds, holds that value.

  • Two new StellarValue arms, STELLAR_VALUE_SIGNED_MS and STELLAR_VALUE_EMPTY_TX_SET_MS, carry the field.

  • The old whole-second close time stays. It must equal closeTimeMs rounded down.

  • Validator signatures cover the new field, so nobody can change it in transit.

How Do Stellar Millisecond Ledger Times Work?

A ledger still has to close after the one before it. But the minimum gap shrinks from one second to one millisecond. So two ledgers in a row can show the same whole-second close time and differ only in closeTimeMs.

Think of it this way. The old field keeps working for older tools, and the new one gives consensus a finer clock. If a tool doesn’t need extra precision, whole-second timestamps are still fine.

One detail to note: the ledger that applies the upgrade keeps the old format. The next ledger is the first to carry a millisecond value.

Why Do Indexers Need Stellar Indexer Updates?

Indexers read ledger data, decode it, and organize it for explorers, dashboards, and wallets. They matter here because XDR, the binary format behind ledger data, can’t decode a union value it doesn’t know.

That’s the whole risk. Software built on older definitions might stop reading Protocol 30 ledgers. Anything that only uses closeTime doesn’t need logic changes, though.

The Stellar Development Foundation has also said the SDK upgrade isn’t optional this time. The official docs list the tools that ingest ledger data, and those teams should check compatibility before the vote.

How Should Developers Prepare for the Stellar Core Upgrade?

Validators should install Stellar Core v30.0.0, released in October, before the vote. Compatible SDK, Horizon, RPC, and Galexie releases are already out.

Here’s a simple checklist for builders:

  • Upgrade to the latest compatible Stellar SDK.

  • Refresh XDR definitions to Protocol 30 in any custom decoders.

  • Handle the two new StellarValue arms the same way as their whole-second versions.

  • Update indexers and pipelines, including code that reads raw consensus history.

  • Test decoding on testnet. Bell has been running there since the Stellar testnet vote on November 3.

  • Check any code that assumes one record always equals a fixed stretch of time.

Does Stellar CAP-88 Change Transaction Time Rules?

No. Transaction time bounds, minSeqAge, claimable balance time conditions, and the Soroban ledger timestamp all keep using the whole-second closeTime, rounded down.

That comes with a few side effects, though. A transaction whose maxTime equals the current second can stay valid across several records that close inside that second. Contracts may also see the same timestamp twice in a row.

One maintainer asked about immutable contracts that expect a fresh timestamp every ledger. The author said nobody had studied existing contract code at that point.

What Is the Link Between CAP-88 and Bell, Protocol 30?

CAP-88 ships alongside CAP-84, which adds muxed contract addresses. Bell also includes other changes, like post-quantum signature checks for smart contracts. The Foundation calls the transaction-level changes additive.

Timing is the big story in Stellar News today. Bell passed its testnet vote and now runs on testnet. The mainnet vote comes on November 23, and activation depends on validators approving it.

Separately, Securitize has announced plans to add Stellar, and that’s pushed up searches for Securitize Stellar fund rights. That’s an issuer plan, and nobody has linked it to CAP-88.

What Are the Benefits and Risks of Stellar CAP-88?

The upsides are more exact ledger timing, room for targets that aren’t whole seconds, and a base for shorter record close times through future network settings changes.

The risks matter just as much:

  • Mainnet still closes ledgers about every five seconds after September’s Protocol 28. CAP-88 alone doesn’t change that.

  • Decoders that miss the new arms can fail outright.

  • Apps that tie one ledger to a fixed length of time may act strangely.

  • If close times ever drop below one second, whole-second transaction features would be coarser than the record gap. The proposal itself says those would need a second look.

Expert Take: What Should Readers Watch?

The smartest part is the design choice. By leaving CloseTime alone, the proposal protects explorers, wallets, and contracts. That’s why most users probably won’t notice the upgrade at all.

At first glance, it looks like housekeeping. But that undersells it, because one missed decoder update can stall a whole data pipeline.

The real worry is old habits. Tools across the ecosystem have treated five seconds per ledger as fixed for years, and the proposal’s author has warned that many of them may break when that changes. So, is the ecosystem ready for ledgers that don’t keep a steady beat?

If you’re expecting faster Stellar transactions from this proposal alone, you’re reading too much into it. Nothing in the text promises a date for shorter ledger times. The biggest open question is when, or if, a faster target gets set.

For background, check the official documentation and the project’s whitepaper. For exact specs, read the proposal text.

Conclusion: Can Stellar CAP-88 Make Ledgers Faster?

Stellar CAP-88 adds a millisecond close time, keeps whole-second features working, and leaves room for faster ledgers down the road. It doesn’t guarantee any specific close time.

Builders still need to update SDKs, XDR definitions, and indexers before the mainnet vote. And the result of that vote stays uncertain until validators act.

Disclaimer

This article is for information only and isn’t financial, investment, or legal advice. Crypto assets carry high risk, protocol upgrades can change or be delayed, and readers should do their own research before making any decision.

Aayushi Shukla

About the Author Aayushi Shukla

English Blog Writer coingabbar.com

I am Aayushi Shukla, a passionate Content Writer with 6 months of professional experience in the Crypto and Web3 industry I specialize in developing informative and engaging content around blockchain technology, cryptocurrencies, DeFi, tokenomics, Web3 platforms, and the evolving digital asset ecosystem. My work involves conducting in-depth research, understanding technical concepts, and presenting them in a simple and reader-friendly manner.

Frequently Asked Questions (FAQ)

Faq Got any doubts? Get In Touch With Us