On May 28, 2026, the U.S. Patent and Trademark Office published a patent application titled “Liveness in Consensus Protocol” (US20260149735A1). The record's assignee field is blank, but its two named inventors, Stephen John Buttolph and Kevin Sekniqi, are the same pair listed on the issued US12549594B2 — a granted patent of the identical title assigned to Ava Labs, Inc., the developer behind the Avalanche network — which places this published application squarely inside that company's filing program. A published application is not an issued patent; it is an roughly 18-month-delayed window onto where a company directed its effort. This one is worth reading because of what it protects: not a product feature, but the chain's ability to keep running when something tries to stop it.

The disclosed method treats consensus as something that can be swapped under pressure. The system runs a first consensus protocol, detects a liveness attack against it, suspends acceptance of new blocks, and then transitions to a second protocol until agreement is reached. The abstract lays out the recovery path:

Aspects may also include transitioning from the first consensus protocol to the second consensus protocol and running the second consensus protocol until a consensus value or a new accepted block is decided.— Liveness in consensus protocol, US20260149735A1

“Liveness,” in distributed-systems terms, is the property that a network keeps making progress — keeps deciding and adding blocks — rather than freezing. A liveness attack tries to stall that progress. The filing's answer is a fallback: when the primary protocol is being prevented from finalizing, the network shifts to a second protocol, reaches a decision, and then reinstates the first. The two CPC classes on the record, H04L 63/1441 (responding to network intrusion) and H04L 9/50 (blockchain cryptography), frame this as a security-and-resilience mechanism for the protocol layer, not as a payments or token feature.

A cluster centered on the chain itself

That framing is consistent across the company's recent records. Across the indexed Ava Labs portfolio of 32 records, the disclosures concentrate on how the chain is built, performs, and recovers rather than on a single consumer application. The granted US12640946B2 (“Customized blockchain infrastructure”), issued May 26, 2026 — two days before this application published — covers generating a heterogeneous network of blockchains, where a platform chain spawns subnets by bonding or burning a base asset. The granted US12591450B2 (“Framework for high performance blockchains”) covers configuring a virtual machine from custom definitions to run a bespoke chain. And US12530678B2 (“Congestion control protocol”) covers sampling validators and scaling the set of block proposers based on a temporal parameter — another reliability-and-throughput concern.

The performance-and-storage line runs deeper still. US12591566B2 covers a “compaction-less database for storing blockchain state,” and US12586063B2 covers “fortified decoupled state machine replication,” partitioning transactions across validators and assembling blocks from replicated chunks. Alongside these sit interoperability and privacy records — US12567988B2 on a secure cross-network asset bridge and US12626254B2 on encrypted transfers with zero-knowledge proofs in a distributed ledger. Read as a body, the cluster points in one direction: the company is documenting, repeatedly and recently, work on the resilience, configurability, performance, and interconnection of base-layer chain infrastructure.

The timing inside the portfolio is itself informative. The issued US12549594B2 — the granted twin of this application — was issued February 10, 2026, and the customized-infrastructure grant US12640946B2 issued May 26, 2026, two days before the liveness application published. A published application typically reflects filing work done well before its publication date, so the cluster represents a multi-year effort whose grants and publications are now landing in close succession. The classification spread across the portfolio underscores the infrastructure focus: H04L 9/50 (blockchain cryptography) is the most common class, appearing on 14 of the indexed records, with the payment classes G06Q 20/3829 and G06Q 20/3825 next. For a sector reader, the practical translation is that a chunk of this company's documented engineering sits at the protocol and data-layer level — consensus, state storage, validator scheduling — rather than at the wallet or token-product level where much crypto attention concentrates.

What the filings disclose, and what they don't

The directional signal is reasonably clear from the records: Ava Labs' published and granted filings concentrate on the chain as infrastructure — keeping it live under attack, letting operators spin up customized subnets, moving state efficiently, and bridging assets across networks. The new liveness application is the most pointed statement of the resilience strand, because it addresses the failure mode that matters most to an institution evaluating whether to build on a given chain: whether the network keeps producing blocks when someone tries to halt it. That is the kind of property a customizable, multi-subnet platform would need to be able to promise.

The caveats apply with force, and the thin week sharpens them. This is a published application, not a grant; its claims may narrow or fail before issuance, and a filing discloses an intent to seek coverage, not a shipped feature or a market position. Blockchain publication volume is also low, and the U.S. blockchain publication window of May 26 to June 1, 2026 was especially sparse — the records indexed for the sector keyword set number 22 published applications, the majority from unnamed assignees or carrying only incidental ledger mentions inside vehicle and energy filings — so the signal here rests on the consistency of the Ava Labs cluster rather than on the volume of any single week. What the records establish is the disclosed direction: a protocol developer documenting, grant after grant and now application after application, the machinery that keeps a configurable blockchain running, fast, and connected — with this filing focused on the part that keeps it from stalling.