- CAP-83 targets slower data conditions, while CAP-85 and CAP-86 improve Soroban upgrades and contract-data migration for developers.
- The roadmap schedules a testnet vote for August 27, followed by a mainnet vote on September 16 for broader deployment across the network.
- The proposal focuses on infrastructure resilience and developer maintenance as Stellar supports financial and tokenization applications.
Stellar Protocol 28 introduces infrastructure upgrades focused on consensus performance, Soroban maintenance, and contract migrations as network usage continues expanding.
Adapter Focuses on Core Network Performance
The wallet provider points to three changes involving consensus and Soroban. Those changes target network resilience, contract maintenance, and developer workflows.
CAP-83 addresses situations where transaction data reaches validators slowly. The proposal allows validators to keep progressing under those conditions. This approach aims to support more consistent network performance during delays.
That focus becomes increasingly relevant as transaction activity expands across Stellar. The network is described as processing millions of transactions already. Its infrastructure therefore faces greater demands from growing application activity.
CAP-83 differs from the other proposals by targeting consensus behavior directly. CAP-85 and CAP-86 instead concentrate on smart-contract development. Together, the changes cover both network operations and application maintenance.
Soroban Upgrades Target Developer Efficiency
CAP-85 allows multiple Soroban contracts sharing common code to upgrade together. This could simplify maintenance across larger contract deployments. Developers would avoid handling every related contract as a separate upgrade.
Coordinated upgrades can also reduce operational complexity for larger applications. That matters when several contracts depend upon the same underlying code. A unified process can make future maintenance more manageable.
CAP-86 addresses another developer challenge involving contract data migrations. Applications often need data structures to evolve as software develops. The proposal aims to simplify those changes without disrupting existing applications.
The two Soroban proposals therefore address different maintenance requirements. CAP-85 focuses on coordinated code upgrades across contracts. CAP-86 focuses on evolving contract data while preserving application continuity.
Governance Timeline Sets the Next Milestones
The upgrade process includes a testnet vote scheduled for August 27. A mainnet upgrade vote is then scheduled for September 16. These votes represent the next governance checkpoints for the proposed changes.
Testnet deployment provides an environment for evaluating the proposed modifications. Developers and network participants can examine behavior before mainnet consideration. This creates a testing stage before production-level deployment.
The broader rationale centers on Stellar’s growing financial infrastructure. Scopuly points to tokenized real-world assets and institutional participation. Those applications can require dependable consensus and flexible contract management.
The proposal therefore represents infrastructure preparation rather than one standalone feature. Its three components address validators, smart contracts, and application data. If approved, the changes would support Stellar’s continued development around institutional use cases.
