Blockstream mapped Liquid upgrades from zero-confirmation payments to a BitVM bridge

Roadmap sets a multi-track agenda

On May 6, 2026, Blockstream published an updated development roadmap for Liquid, the federated Bitcoin sidechain built on the Elements codebase. The plan put near-term work on payments and asset issuance beside longer-range research into post-quantum security and a BitVM-style bridge. The verified event was the publication of that roadmap; it was not a network activation, product launch or claim that Bitcoin's base-layer rules had changed.

The most concrete consensus item was ELIP 203, a proposal to remove Elements' inherited 21 million-unit ceiling for explicit issuance and reissuance of assets other than the pegged bitcoin asset. Blockstream said the change required a coordinated hard fork and targeted late May 2026 activation. The underlying specification described ELIP 203 as a draft standards-track, consensus-layer change and included a policy safeguard intended to stop upgraded functionaries from confirming incompatible transactions before coordinated deployment.

A separate payment track proposed zero-confirmation handling so selected services could act on Liquid transactions before the next block when their risk policies and network conditions allowed. Blockstream described testing with federation members and targeted June 2026 for release. It also said ELIP 204, a multi-asset-fee proposal, remained under Technology Board review. That distinction matters: ELIP 203 had an identified hard-fork path, while multi-asset fees were still a proposal and the BitVM-style bridge was explicitly research.

Why it mattered

Liquid connects bitcoin locked on the main chain with LBTC on a federation-operated sidechain. Its design offers roughly one-minute blocks, confidential transfers and native asset issuance, but it also substitutes a federation and threshold-signature bridge for Bitcoin's proof-of-work settlement. The May 6 roadmap mattered because it addressed both sides of that tradeoff: reducing payment and issuance friction in the near term, while examining the bridge's operating costs and trust assumptions over a longer horizon.

Removing the non-LBTC issuance ceiling was aimed at fiat-denominated instruments and high-unit-count securities, for which Bitcoin's 21 million monetary limit has no economic relevance. Zero-confirmation support sought to make swaps and payments feel immediate, but “safe to act on” was conditional, not equivalent to final settlement. Multi-asset fees could let a user holding an issued asset avoid maintaining a separate LBTC fee balance, subject to local acceptance policies and federation governance.

The roadmap also connected Liquid's Simplicity smart-contract environment with post-quantum experiments and described work toward a BitVM-style one-of-n bridge. On May 6, those were research directions, not deployed protections or a production replacement for Liquid's existing bridge.

What was verified — and what was not

The contemporaneous Blockstream record establishes the date, roadmap scope, target windows and status labels. The ELIP 203 repository record establishes the proposed consensus change, draft status, compatibility risk and reference implementation. A May 1 Liquid Federation update independently within the project ecosystem confirms that zero-confirmation capabilities, multi-asset fees and the issuance-limit hard fork were already on the 2026 upgrade agenda.

No market-price reaction is attributed to the roadmap. No company-supplied adoption, transaction-volume or tokenized-asset total is used here because the reviewed records did not provide an independently reproducible measurement window for those claims. Planned dates were targets subject to federation governance, Technology Board review, testing and release changes.

Later context

In a July 3, 2026 quarterly update, Blockstream said ELIP 203 had activated and that the zero-confirmation feature was in public beta with a full release targeted for early July. That later statement helps separate the May 6 plan from subsequent progress, but it does not retroactively turn every roadmap item into an event-day release.