Stellar's Bell Vote Is Eight Days Out and XLM Sits 0.5% Off a 60-Session Floor: 0.1663 Decides 0.1830 or 0.1524

Stellar validators vote on Bell, Protocol 30, in eight days. The testnet vote is 3 November at 17:00 UTC and the mainnet vote follows on 23 November, both at the same hour. XLM, meanwhile, closed Sunday at $0.1681 — half a percent above the lowest level it has printed in sixty sessions. One of those facts is a calendar entry and the other is a tape, and for a month the tape has been winning.

What Bell actually changes

The upgrade carries three changes, all additive and opt-in for existing contracts. The first is CAP-84, muxed contract addresses: a smart account can now carry a 64-bit ID written as a new address type that starts with W, so one contract can hold balances for many customers and record which one paid. It is the omnibus model exchanges and custodians already run on classic muxed M accounts, extended to accounts that are contracts rather than keypairs. Without it, a business holding customer funds in a smart account needed one contract per customer.

The second is CAP-87, post-quantum signature verification. Soroban contracts can verify ML-DSA signatures — one of the standards NIST finalised in 2024 — through three new host functions covering the 44, 65 and 87 parameter sets. Verification runs inside Stellar Core rather than in contract code, so it is cheap to call and written once against the official test vectors. Stellar calls this the first onchain piece of its quantum preparedness plan.

The third is CAP-88, a millisecond ledger clock. Stellar records each ledger's close time in whole seconds today, which caps the network at whole-second intervals and never less than one second apart. Protocol 28, Adapter, brought mainnet close times from about 5.7 seconds to 5 in September. A millisecond clock is the prerequisite for going below that, not the thing that does it.

What Bell does not do

Two clarifications matter more than the announcement. Bell does not make Stellar post-quantum: network transaction signatures stay Ed25519, and what the upgrade adds is the ability for a contract account to require a quantum-safe signature to spend. And Bell does not make Stellar produce blocks faster than five seconds by itself — it removes the one-ledger-per-second floor so a later protocol change can target finer intervals.

Nor is a vote a demand event. Bell is plumbing for the businesses that want a smart account to behave like a bank account: exchanges, on and off ramps, custodians, issuers. Plumbing gets adopted after it ships. The full detail is in the Stellar Development Foundation announcement and the Protocol 30 upgrade guide.

Eight days, and a mandatory SDK upgrade for anyone who decodes the ledger

Stellar Core v30.0.0 shipped on 16 October and the infrastructure and SDK releases followed through 23 October. The SDK bump is not optional this cycle. CAP-88 changes the ledger header format, so an older SDK can fail to decode Protocol 30 ledgers, and anything reading raw ledger data — indexers, explorers, analytics pipelines, custom XDR decoders — has to update its definitions before the vote or its decoder will fail on the new union arms. Applications that validate or store addresses need to accept the W variant, not merely parse it.

One caution on the dates, and it is the foundation's own: the timeline is labelled subject to change, and a validator vote is not an activation. Testnet votes on 3 November, mainnet votes on 23 November, and the rules change if validators approve. The v30.0.0 release is what node operators are being asked to run before either date.

A 29.9% slide into a three-session floor

XLM does not look like an asset waiting for a vote. The high of the last sixty sessions was 0.2371 on 29 September, printed on 191.4 million XLM — 2.7 times the sixty-session median volume — and sold to a 4.35% lower close in the same session. The breakout session before it, on 28 September, traded 318.0 million XLM, 4.6 times the median. That is a distribution pattern, not accumulation.

From that high the token has given back 29.9%, bottoming at 0.1663 on 24 October. The last four sessions all closed lower. The last five all printed lower highs, a staircase from 0.1845 down to 0.1688. On CoinGecko's numbers XLM is 6.2% lower over seven days and 23.7% lower over thirty, ranked 20th at a $5.89 billion market cap and 80.9% below its all-time high.

What is interesting is the volume into the low. Sunday traded 31.3 million XLM, 0.45 times the sixty-session median and the quietest session of the decline. And the floor has now been tested three sessions running: 0.1663 on 24 October, then 0.1668 on both 25 and 26 October. Sellers are not pressing here. They are simply absent, which is a different problem.

The three levels that decide it

The line is 0.1663. A daily close below it opens the 18 August low at 0.1524, and the 0.0175 measure of the 22-24 October leg projects to 0.1488, just underneath that shelf. There is nothing in between to catch a fall.

Overhead, the first lid is 0.1741 to 0.1742 — a level the market touched on 17 October, again on 22 October, and tapped as a high on 24 October before it broke. Above that, the 0.236 retrace of the entire 0.2371-to-0.1663 leg sits at 0.1830, within a rounding error of the 0.1838 close the market gave back on 22 October. The 0.382 lands at 0.1933. Between 0.1663 and 0.1742 there is a 4.7% pocket with no structure in it at all.

So the setup has a cleaner shape than most. The calendar gives the network a reason to be talked about on 3 November and again on 23 November, and the tape gives it one line in the sand at 0.1663. An upgrade that ships W addresses and ML-DSA verification is worth something real to the exchanges and custodians who have to build on it. Whether it is worth anything to the token depends on flows arriving after the vote — and on a close that finally stops printing lower highs.