Daily Crypto Briefs 
CASABLANCA, July 11, 2026
Stellar’s Protocol 27 upgrade, known as Zipper, went live on mainnet with new smart-account delegation and replay-protection tools as XLM closed July 9 at $0.1863 after trading volume rose to roughly $623.9 million.
The release makes a technical change that can be felt by wallet users over time rather than by ordinary token holders immediately. It gives developers a supported way to assign signing authority, bundle approvals and build features such as multisig wallets and social recovery.
CoinLore’s historical table showed XLM closing at $0.1863 on July 9, down from $0.2000 on July 6 but above its $0.1739 close on June 28. Its reported daily volume expanded from about $165.2 million on July 8 to $623.9 million on July 9, while market capitalization stood near $5.9 billion.
The Stellar Development Foundation’s upgrade guide said Zipper turns authentication delegation into a “first-class” feature for custom accounts. The foundation said the changes reduce transaction size and simplify simulation for developers, while its documentation describes a planned migration path rather than an immediate break for older credentials.
The activation followed the mainnet upgrade vote scheduled for July 8. Coverage of Stellar’s announcement reported the network was live the next day, after a preparation schedule that had included stable Core, SDK, Horizon and testnet releases.
The near-term implication is practical rather than promotional. A protocol feature can make account security and delegated approvals easier to build, but it does not require wallets or users to adopt it, and it does not by itself create token demand.
What remains unclear is which major wallets, payment apps or Soroban applications will use the new account model first, and whether that usage will become visible in network activity. The next protocol checkpoint is the move away from the older credential type ahead of Protocol 28.
Stellar Zipper Makes Delegated Signing Easier
Before Zipper, delegated authentication was possible but awkward. Stellar said developers had to manually construct inner authorization payloads, run multiple simulation passes and create a separate authorization entry with its own nonce for each delegated signer.
Protocol 27 adds delegate_account_auth and get_delegated_signers_for_current_auth_check, two host functions intended for custom account contracts. It also introduces a credential that can bundle delegated signers and their signatures into one authorization entry, according to the official guide.
That distinction matters for a wallet product. A delegated signer is an address that an account has allowed to help authorize an action. Putting those approvals into one entry can reduce the amount of transaction data and reduce the work needed to prepare a transaction.
The immediate audience is developers working with Soroban, Stellar’s smart-contract environment. The foundation identified wallets, multisig schemes and account-abstraction products as the most direct users, including designs where a customer can recover access through pre-authorized keys or trusted parties.
The design is an infrastructure layer, not a new consumer app. Its success will depend on wallet SDK updates, relayer integrations and applications choosing the pattern in live transactions.
Stellar already has a payments use case that gives that work context. Daily Crypto Briefs previously covered MoneyGram’s MGUSD stablecoin launch on Stellar, where the user-facing product is a dollar token and not XLM. Zipper is aimed at the account controls beneath products of that kind.
Protocol 27 Adds Address Bound Replay Protection
The second central change is an address-bound credential for Soroban. The new signature payload explicitly includes the top-level account address, an extra binding that prevents a signature from being reused across accounts that share private keys when the transaction payload does not otherwise bind the signer address.
The foundation described that risk as narrow. It requires both shared private keys across accounts and an invocation payload without the needed address binding, which means the upgrade is a targeted hardening measure rather than evidence of a broad live exploit.
Existing credentials remain valid for now. Stellar said developers do not have to migrate immediately, but the newer version is expected to replace the older version in Protocol 28. That gives teams a controlled window to update dependencies and test account flows.
This is the type of software lifecycle issue that can be missed in upgrade headlines. A network vote makes a capability available, but wallets, custody providers and application teams still have to choose and correctly integrate it.
The sequence resembles the distinction Daily Crypto Briefs drew in its coverage of the XRP Ledger’s validator rollout. Software distribution, formal activation and end-user demand can move at different speeds, even when the market groups all three under an “upgrade” label.
For builders, the test is not whether the new functions exist. It is whether they reduce enough engineering work and security risk to justify a migration from established account workflows.
XLM Volume Spikes Do Not Settle the Adoption Question
The market response showed attention but not a clean price breakout. CoinLore’s data put XLM at $0.1863 at the July 9 close, a 2.87% gain from the previous day but below the $0.2349 intraday high recorded on June 19. The same data showed about 3.42 billion XLM, or $623.9 million, changing hands on July 9.
That volume increase is a useful signal of interest around the activation, but it is not proof that wallets or applications have adopted delegated authentication. A high-volume day can reflect trader positioning around a headline as easily as new network usage.
The broader context is also mixed. XLM was still down from its early July range, and market data services listed a 7-day trading range between roughly $0.18 and $0.22. The token’s market capitalization around $5.9 billion means even a large percentage move in volume does not resolve the longer-term adoption case.
The commercial opportunity is tied to the kind of payment and asset-issuance systems Stellar is trying to host. Our report on DTCC’s tokenized Treasury work shows the wider competition for regulated onchain infrastructure, where the choice of a ledger often depends on compliance, custody and integration rather than a protocol release alone.
Stellar
XLMFear still dominated the wider crypto market.
Fear & Greed Index
July 10, 2026The next signals are more concrete than price targets: wallet release notes, usage of the new credentials, migration plans for the older credential type and any disclosed increase in Soroban account activity. Zipper is now a live building block. Whether it becomes a visible Stellar product advantage is still an open question.
Stay up to date
Get the latest crypto insights delivered to your inbox
Primary sources and further reading
| Source | Title |
|---|---|
| | Stellar Development Foundation: Zipper Protocol 27 upgrade guide |
| | Stellar developer documentation: software versions |
| | Stellar Protocol: CAP-71 authentication delegation |
| | CoinLore: XLM historical prices |
| | DailyCoin: Stellar Protocol 27 mainnet launch |
| | Alternative.me: Crypto Fear and Greed Index |
Fact-checked by: Daily Crypto Briefs Fact-Check Desk
Related Articles
Frequently Asked Questions
What is Stellar Protocol 27 Zipper?
Zipper is Stellar's Protocol 27 upgrade. It adds first-class authentication delegation for Soroban smart accounts, bundles delegated signatures into a single authorization entry and introduces address-bound credentials that mitigate a narrow replay risk.
When did Stellar Zipper go live on mainnet?
Stellar's mainnet upgrade vote was scheduled for July 8, 2026, and Stellar announced that Protocol 27 was live on mainnet on July 9, according to coverage of the official announcement.
Does the Zipper upgrade require wallet users to migrate immediately?
No. Stellar said the existing credential remains valid for now. Developers using the older credential should plan to adopt the newer address-bound version before Protocol 28, when the older version is scheduled to be replaced.
Why does address-bound authentication matter?
It binds the signature payload to the top-level account address. This reduces the chance of a signature being replayed across accounts that share a private key in a narrow set of circumstances.
Does Protocol 27 make XLM more valuable?
Not automatically. The upgrade improves wallet and developer capabilities, while XLM price still depends on token demand, liquidity, broader market conditions and the adoption of applications built with the new tools.