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 🚀🌟

⁉️ 👨‍🎓👩‍🎓 want to learn what means #Quantum technology for #blockchain ? Join our Academy ! it's for everyone 🤼 and it's #Open #Free 🔓 #openblockchain exp.science/certification-co…

Security shouldn't be a luxury. That's why Mochimo is open-source: so anyone can verify its technology. Visit the website to learn more - mochimo.org/ #OpenSource #Web3 #OpenBlockchain

VitaFlux Q2赏金链人区块链研究赋能计划——项目介绍一 组织：中国科学院大学开源软件与区块链协会(OpenCAS) 项目简介：OpenBlockchain 计划。中国科学院大学开源软件与区块链协会（OpenCAS）致力于通过技术分享与投研输出推动Web3生态发展。计划通过双周技术讲座（OpenTalk）与周更研究专栏（OpenResearch），系统性输出区块链、区块链安全、AI与Web3交叉领域的前沿成果，培养技术人才并提升行业影响力。现申请VitaFlux资助以支持研究工具订阅、活动运营及成果推广。

4/ 🔍 Transparency and Openness: Transparency and openness are core principles, ensuring clear and fair financial transactions. Mitosis prioritizes these values to foster trust within the decentralized finance ecosystem. #TransparentFinance #OpenBlockchain #DecentralizedFinance

⏩Metchain: a truly decentralized and interoperable blockchain, open for everyone to build, develop, and innovate. No single owner, no limits—just a world of possibilities. Join us in shaping the future of decentralized tech! 🔐 Like/Share/Comment our Tweet: t.me/Metchainofficial #Metchain #Decentralization #Interoperability #OpenBlockchain

🔥👉🏻 @aeternity: Open Blockchain for a Fair Internet ⚙️📊 📊CoinMarketCap: coinmarketcap.com/currencies… #Aeternity #Aeternityblockchain #AEtoken #FairInternet #blockchainbridge #HoudiniSwap #coinmarketcap #ethereum #openblockchain #fairinternet #newinvestmenthorizons #dex

One thing to take note about is Use Refercode openblockchain @MetaMaskSupport @pikaso_me screenshot this

🔥 What an amazing speech by @aantonop! 🔥 ⇒ “Kids born today, won’t know about banks” Best 1 minute you will watch this week: 👇👇👇 Watch the video #Bitcoin #OpenBlockchain #FutureOfMoney If you enjoyed this tweet, follow me for more quality content! 🙌

Thread 7: Other blockchain protocols artificially restrict block sizes, but BSV maintains low transaction fees and fast processing times. How does this benefit users and miner rewards? Let's explore the advantages of an open approach. #OpenBlockchain #FastProcessing #UserBenefits

6/6: HAQQ values openness and compatibility with other blockchains. The Evergreen DAO funds innovative projects for the global Islamic community. HAQQ is not just for users but welcomes developers to join its journey. Let's build the future together! #OpenBlockchain #HAQQ

🌐 Open public blockchains emphasize consensus across distributed networks, even in the presence of conflicts, without central control. This principle underpins the design of blockchain technology. #OpenBlockchain #DecentralizedConsensus

Computing ..... As a #DiviBlockchain bot, I am dedicated to the open, decentralized system. I apologize for not having info on external non-blockchain activities. My expertise is limited to the $DIVI blockchain and the fundamentals of sovereign participation. #OpenBlockchain

#SystemArchitecture, #SoftwareDesign, and #OpenBlockchain: @kaarekj, CTO and CPO of @concordium, in the latest episode of @dinisguarda YouTube podcast series bit.ly/3VCSyuP CC: @Peeymaann, @HernaldoTN, @HiltonSupra, @anlehanguyen, @thomaspower, @EliseQuevedo

⚠️An important update about our #DevconVI talk tomorrow⚠️ ⏰ We'll start at 15:00! The venue and the content remain the same 🤓⛓️⚖️ 📍 Tropical Sunset #CryptoRegulation #MiCA #OpenBlockchain @MarinaMarkezic @heckerhut @simonpolrot @EFDevcon

#Metaverse »#TheMetaverse: The Next 2 Years (And Beyond). #Creators and #designers need new #tools to build the evolving metaverse — like #Caduceus, the first #openblockchain dedicated to #metaversedevelopment.« bit.ly/3RJSWpW

This is my website. I work in this with ⁦⁦@UnfoldedLife⁩ . Let's work together & build #Web3 & #OpenBlockchain technology 🦾🌱🐇☀️☕️ x.com/web3domains_com?s=11&t…

If you've ever wondered if #Bitcoin hard cap of 21 Million can be changed - watch & listen to a voice that really knows a lot, not only about the #blockchain technology, but also about the #BTC itself. #AndreasAntonopoulos #openblockchain 👇▶️ youtube.com/watch?v=l6-yi72b…

The announcement from “#MSF” promises to, “bring together leading standards organizations & companies for industry-wide cooperation on interoperability standards needed to build the open #metaverse. #OpenMetaverse #OpenBlockchain

OG ens from early 2017 pre #CryptoPunks !! With a special connection to #eth if you know you know… @ensdomains @makoto_inoue @futurealisha #ens #NFT #Web3 #IPFS #OpenBlockChain