Stellar Zipper: Complete Guide to the Protocol 27 Upgrade
Published on June 4, 2026, by the Stellar Development Foundation
The Stellar ecosystem is preparing for a major milestone with the deployment of Zipper, the upgrade associated with Protocol 27. This update introduces significant improvements for Soroban developers, infrastructure providers, wallets, and businesses building on the Stellar network.
In this article, we explore the key dates, technical innovations, important changes, and recommended actions to ensure your infrastructure is ready for the upgrade.
What Is Stellar Zipper?
Zipper is the codename for Stellarโs upcoming Protocol 27 network upgrade. Its primary goal is to enhance authentication management for smart accounts, strengthen Soroban signature security, and simplify the development of decentralized applications.
The upgrade is part of Stellarโs broader roadmap to expand account abstraction capabilities and advanced authorization features.
Official Deployment Timeline
Developers, validators, and businesses integrating Stellar should prepare for the following milestones:
DateEventJune 5, 2026Stable release of Stellar CoreJune 5โ11, 2026SDK releasesJune 10, 2026RPC and Galexie releasesJune 12, 2026Horizon releaseJune 18, 2026Testnet upgradeJuly 8, 2026Mainnet upgrade vote
The Stellar Development Foundation strongly recommends upgrading integrations before deployment dates to avoid service interruptions or compatibility issues.
Components Affected by the Upgrade
Protocol 27 impacts the entire Stellar ecosystem.
Stellar Infrastructure
Updated versions will be available for:
Stellar Core
Horizon
RPC
Galexie
Supported SDKs
The following SDKs will receive Protocol 27-compatible releases:
Rust SDK
JavaScript Base
JavaScript SDK
Go SDK
Java SDK
Python SDK
iOS SDK
PHP SDK
C# .NET SDK
Flutter SDK
Elixir Stellar SDK
Major Feature: Authentication Delegation for Custom Accounts (CAP-0071-01)
One of the most significant enhancements introduced by Zipper is a native mechanism for authentication delegation in smart accounts.
How It Works
Until now, custom accounts could technically delegate authentication to another address, but doing so relied on an unintended side effect of the authorization framework and was difficult to implement correctly.
Protocol 27 introduces:
New Host Functions
delegate_account_auth
get_delegated_signers_for_current_auth_check
These functions allow smart contracts to explicitly delegate authentication to another address and retrieve delegated signers involved in the authorization process.
New Credential Type
A new credential format is introduced:
SOROBAN_CREDENTIALS_ADDRESS_WITH_DELEGATES
This credential allows multiple delegated signers to be bundled into a single authorization entry, significantly reducing:
Transaction size
Simulation complexity
Number of required nonces
Associated transaction costs
Delegation can also be nested, meaning delegated signers may themselves have additional delegated signers.
Why This Matters
Before Zipper:
Each delegated signer required a separate authorization entry.
Developers often needed multiple simulation passes.
Authorization payloads had to be manually constructed.
Transactions became unnecessarily large and expensive.
With Protocol 27:
Delegation becomes a native protocol feature.
Transactions become more efficient.
Simulations are simplified.
Development becomes significantly easier.
Who Benefits?
Soroban Developers
Builders creating:
Smart wallets
Multisignature systems
Account abstraction solutions
Advanced authorization frameworks
will benefit the most.
Wallet Providers
New signing models become easier to implement, including:
Social recovery mechanisms
Temporary signing delegation
Modular multisig architectures
Granular permission management
End Users
Even non-technical users will benefit through:
Potentially lower transaction fees
More flexible account structures
Improved wallet experiences
Enhanced Security with Address-Bound Credentials (CAP-0071-02)
The second major improvement focuses on strengthening Soroban signature security.
Introducing SOROBAN_CREDENTIALS_ADDRESS_V2
Protocol 27 introduces:
SOROBAN_CREDENTIALS_ADDRESS_V2
This new credential format uses a signature payload explicitly bound to the signer's address.
What Problem Does It Solve?
In rare scenarios where:
Multiple accounts share the same private key.
The signed payload does not explicitly include the account address.
A replay attack could theoretically occur.
The new credential format eliminates this possibility by cryptographically binding signatures to the associated address.
Is Immediate Migration Required?
No.
Stellar has provided a transition period:
SOROBAN_CREDENTIALS_ADDRESS (V1) remains valid throughout Protocol 27.
Full migration will become necessary before Protocol 28.
Developers are nevertheless encouraged to begin preparing their applications as soon as possible.
Breaking Changes and Migration Considerations
Most Protocol 27 additions are backward-compatible, but some updates require attention.
JavaScript SDK Consolidation
One of the most visible changes affects JavaScript developers.
Previous Package
@stellar/stellar-base
New Standard
@stellar/stellar-sdk
The stellar-base package is being consolidated into stellar-sdk.
Projects currently importing:
import ... from '@stellar/stellar-base'
should migrate to:
import ... from '@stellar/stellar-sdk'
Long-Term Impact on Stellar
Beyond its immediate improvements, CAP-0071-01 serves as a foundational building block for future Stellar enhancements.
According to the Stellar Development Foundation, this upgrade lays the groundwork for:
CAP-0072, which will enable contract-based authentication for traditional Stellar (G-) accounts.
In other words, Zipper represents a strategic step toward a more advanced and flexible account abstraction model across the Stellar network.
Recommendations for Developers
Before Protocol 27 goes live, developers should:
โ Upgrade Stellar Core to the latest stable release.
โ Verify SDK compatibility.
โ Migrate JavaScript projects to @stellar/stellar-sdk.
โ Test delegation features on Testnet beginning June 18.
โ Plan migration toward SOROBAN_CREDENTIALS_ADDRESS_V2.
โ Review official release notes for all deployed components.
Conclusion
Protocol 27 "Zipper" marks a major evolution for the Stellar ecosystem. By introducing native authentication delegation and stronger Soroban signature security, the upgrade simplifies the development of sophisticated decentralized applications while paving the way for future account abstraction capabilities.
For developers, wallet providers, validators, and enterprises building on Stellar, preparing now is essential to ensure a smooth transition ahead of the July 8, 2026 Mainnet upgrade vote.
#Stellar #XLM #StellarNetwork #Soroban #Protocol27 #Zipper #Blockchain #Crypto #Cryptocurrency #Web3 #DeFi #SmartContracts #CryptoCommunity #XLMArmy #StellarDevelopmentFoundation #SDF #CryptoUpdate #Mainnet #Testnet #Developer #BuildOnStellar #StellarBuilders #StellarCommunity #SmartAccounts #CAP0071 #CAP0072 #BlockchainUpdates #XLMNews #SorobanSmartContracts #CryptoTwitter #XFinance #FutureOfWeb3 #EnterpriseBlockchain #DecentralizedApps #DApps #CryptoEngineering #Web3Ecosystem #OpenBlockchain #StellarEcosystem #SorobanDevelopers #Web3Infrastructure #XLMCommunity #SmartWallets #DigitalEconomy #TechInnovation #BUIDL #DYOR #LFG ๐๐
Blockchain in healthcare
How blockchain could help secure patient records, improve interoperability, and track pharmaceuticals.
Read more ๐
https://t.co/7I1gEHzZ5k
The Romans didnโt mine mountains, but collapsed them instead.
Using aqueducts, they blasted water into hillsides until entire sections gave way, exposing gold deposits beneath.
Landscape-scale mining isnโt new. The Romans were doing it 2,000 years ago.