Friday, September 18, 2026

Creating liberating content

XRPL’s new lending tool...

XRP Ledger's (XRPL) newest server release defines a future lending market in which...

Bitcoin Price Unlikely To...

The Federal Reserve hiked interest rates for the first time since...

From Kaiko to OpenZeppelin,...

S&P Global agreed to acquire smart contract security firm OpenZeppelin, expanding its digital...

Digital Credit Could Rival...

Two years ago, Bitcoin-backed digital credit barely existed. Today...

Stellar activates Protocol 28 as network hits record throughput and RWA value climbs

Stellar activated Protocol 28 as the blockchain hit a new sustained throughput record, adding tools designed for larger smart-contract deployments.

The network ran Protocol 28 by Sept. 17 after a scheduled mainnet upgrade vote a day earlier. The release lets developers move groups of Soroban smart contracts to new code at once and introduces changes intended to make contract data easier to migrate as applications evolve.

The upgrade coincided with a fresh performance milestone. Blockchain analysis firm Chainspect said Stellar averaged more than 211 transactions per second across 100 consecutive blocks, its highest sustained throughput on record.

Protocol 28’s CAP-85 targets protocols that run multiple instances of the same smart contract. Developers can now have those contracts reference an externally managed executable, so changing the shared reference moves every participating contract to new code in a single atomic operation.

That can narrow the window during security fixes or software migrations when some contracts are running updated code while others remain on an older version. Adoption remains optional, meaning existing Soroban applications must choose to implement the new architecture.

Read More:  XRP’s $1 rebound faces holders trapped above $2

CAP-86 tackles another problem that emerges as applications mature: changing the structure of data already stored by live contracts. New sparse-map functions can accommodate missing or additional fields, allowing developers to migrate information progressively rather than requiring records to conform immediately to a new schema.

Protocol 28 also introduces consensus changes through CAP-83. The design lets validators progress through parts of consensus without waiting for complete transaction sets to arrive and provides a mechanism to discard late or invalid sets.