Blockstream has released Core Lightning 26.06, introducing an update that moves the implementation away from its legacy pay command and toward xpay. The change is being framed as part of a broader modernization of payment handling inside one of the Lightning Network’s major node implementations.
The release deprecates pay rather than removing it outright, giving node operators and developers a transition window before xpay becomes the clearer reference workflow. That distinction matters because deprecated commands can remain usable for a period, even as projects signal that future development attention is shifting elsewhere.
xpay Becomes the New Payment Direction
The move toward xpay suggests that Core Lightning is preparing users for a cleaner or more capable payment flow without immediately breaking existing integrations. For operators, the practical implication is that scripts, tools and workflows using the older command should begin accounting for the newer path.
Core Lightning updates are especially relevant for node operators, wallet developers and infrastructure teams that need to track compatibility across Lightning implementations. Even small command-level changes can affect automated payment systems, monitoring tools and operational procedures.
The release also introduces features described as quantum-resistant and BOLT12-related, expanding the update beyond a simple command deprecation. However, the announcement does not establish broad live usage of those capabilities across the Lightning Network.
Security Features Still Need Adoption Context
That point is important because software availability is not the same as network adoption. Core Lightning 26.06 may include new security-oriented functionality, but its real-world impact will depend on how quickly operators upgrade and how developers integrate the new features.
The BOLT12-related additions also fit a longer-running effort to improve Lightning payment experiences and protocol flexibility. Still, without a full deployment picture, the update should be read as a release milestone, not proof that the wider Lightning ecosystem has already moved to a new standard.
For now, the clearest confirmed change is the deprecation of pay in favor of xpay. The broader significance will become clearer as node operators test the release, developers update tooling and Blockstream provides more detail on the new security and BOLT12 capabilities.