Exchange Ranking
Top Exchanges
24h Volume Ranking
Popularity Ranking
Exchange BTC Balance
Proof of Reserves
Decentralized Exchanges
Funding Rate
Funding Heatmap
Liquidation Data
Max Pain
Long/Short Ratio
Whale L/S Ratio
Binance/Okex/Huobi L/S
Bitfinex Margin L/S
ETF Tracker
Solana ETF
XRP ETF
Hong Kong ETF
Bitcoin Treasuries
Crypto Reversal
Ethereum Reserves
HyperLiquid Wallet Analysis
Hyperliquid Whale Watch
Large Transactions
On-chain Movement
Bitcoin ROI
Stablecoin Market Cap
Options Analysis
News
Articles
Economic Calendar
Features
Wallet
Contract Calculator
Security
Collections
Watchlist
Following
XLM Stellar Protocol 28 Upgrade: Focus on Consensus Performance and Developer Maintenance
CAP-83 is designed to cope with the slow spread of transaction data, while CAP-85 and CAP-86 optimize Soroban's upgrade process and contract data migration operations to provide convenience for developers.
According to the roadmap, test-net voting is scheduled to take place on August 27, followed by main-net voting on September 16 to allow for wider deployment on the network.
As Stellar supports financial and tokenized applications, the proposal focuses on infrastructure resilience and developers 'maintenance needs.
Stellar Protocol 28 introduces a series of infrastructure upgrades focusing on consensus performance, Soroban maintenance, and contract migration to cope with continued growth in network usage.
Adapters focus on core network performance
Scopuly said the upcoming upgrade will strengthen Stellar's infrastructure behind the expansion of financial applications. The wallet provider pointed out three changes involving consensus mechanisms and Soroban, which target network resilience, contract maintenance, and developer workflows.
CAP-83 solves the problem of transaction data slowly reaching the verification node. The proposal allows verification nodes to continue advancing despite data delays, thereby maintaining more stable network performance during delays.
This focus has become increasingly important as trading activity on Stellar grows. The network has been described as processing millions of transactions, and its infrastructure is facing increased pressure from growing application activity.
CAP-83 differs from other proposals in that it directly optimizes consensus behavior. CAP-85 and CAP-86 focus on smart contract development. These three changes jointly cover both network operations and application maintenance levels.
Soroban upgrades improve developer efficiency
CAP-85 allows unified upgrades for multiple Soroban contracts that share the same code, which can simplify maintenance during large-scale contract deployments. Developers do not need to treat each related contract as a separate upgrade task.
Coordinated and unified upgrades can also reduce the operation and maintenance complexity of large applications. This feature is particularly important when multiple contracts rely on the same underlying code. A unified process makes future maintenance more controllable.
CAP-86 solves another challenge faced by developers: contract data migration. Applications often require data structures that evolve as software evolves. The proposal aims to simplify these changes without affecting the operation of existing applications.
Therefore, these two Soroban proposals address different maintenance needs: CAP-85 focuses on collaborative code upgrades across contracts, and CAP-86 focuses on evolving contract data while maintaining application continuity.
Governance timeline sets next milestone
The upgrade process includes a testnet vote scheduled for August 27, followed by a mainnet upgrade vote on September 16. These votes represent the next governance node for the proposed changes.
Testnet deployments provide an environment for evaluating proposed modifications. Developers and network participants can observe behavior before mainnet reviews, creating a testing phase before production-level deployment.
The broader context lies in Stellar's growing financial infrastructure. Scoply mentioned tokenized real-world assets and institutional participation. These applications require reliable consensus mechanisms and flexible contract management.
Therefore, the proposal represents infrastructure preparation rather than a single function. Its three components are for verification nodes, smart contracts, and application data. If approved, these changes will support Stellar's continued development around institutional use cases.
