One of the quieter strategic questions in crypto is which chain a token should live on — and the increasingly common answer from payment companies is: don't make the user decide, decide it for them at transaction time. Block, Inc. has been patenting that answer repeatedly. US12,211,042, granted January 28, 2025, is the latest grant in a family built on a single specification, and the family — not the lone patent — is what a landscape reader should weigh.

The shared disclosure opens the same way across the lineage.

A blockchain agnostic token network is described. In an example, a request to purchase a non-fungible token (NFT) minted on a blockchain from a seller is received.

The mechanism is a routing decision. On receiving a request to purchase a token, the system uses context data — about the user, the seller, or the digital asset — to determine a plurality of available blockchains that could hold the token, surfaces information about them, selects one, and transfers the token to the determined chain, associating it with a user account. The word doing the heaviest lifting is agnostic: the network is designed so the holding chain is a runtime choice, not a fixed property of the token.

The portfolio view is the reason this is a Grant Watch. The same abstract anchors at least four issued grants in Block's name: US11,501,297 (the original, 2022), US11,900,373 (2024), US12,175,464 (December 2024), and US12,211,042 (January 2025). The same core inventors — Ryan Tai, Madeeha Ghori, and Daniel Barrett — recur across them, with later grants adding co-inventors. Four grants, one specification, a steady cadence of issue dates: this is a deliberate continuation family, the same prosecution pattern incumbents use to fence a mechanism from several claim angles while keeping an application live as the field shifts.

There is a stablecoin thread worth pulling, because it is what ties this NFT-framed family to the settlement story. The supporting disclosure across the family describes payment flows where a payer may hold a stablecoin balance alongside fiat, and the payment service deducts, converts, and routes across those balances by conversion rate. The headline examples are NFTs, but the plumbing underneath contemplates stablecoin-denominated value moving through the same agnostic network — which is the more durable commercial idea hiding inside a tokens-and-collectibles wrapper.

The CPC tags keep it grounded in payments rather than protocol: G06Q 20/401 (transaction verification), G06Q 20/20 (point-of-sale / payment architectures), and G06Q 2220/00 (the business-method/payment cross-reference tag). Notably, this family does not lean on the H04L 9/50 blockchain-cryptography class — it is classified as a payments invention that happens to route across chains, which is a faithful description of what Block is: a payments company, not a protocol lab.

The scope caution applies as always. This family does not fence “multi-chain wallets” or “cross-chain transfers” as categories — that space is crowded with bridges, aggregators, and routing protocols. The grants are bounded by their specific context-data-driven chain-selection-at-purchase mechanism. A wallet that lets a user manually pick a chain, or a bridge that moves an existing token without this purchase-time selection flow, has room outside the recited claims.

It is worth dwelling on why "agnostic" is the commercially loaded word, because it is also where the IP value concentrates. If a token's host chain is fixed at mint, the user bears the chain-selection problem: they must understand gas costs, finality, bridge risk, and liquidity differences before they transact. Block's family pushes that problem to the service, deciding the host chain from context data at purchase time. For a payments company, abstracting the chain away is the whole pitch — the user experiences a payment, not a blockchain choice. Patenting that abstraction is patenting the seam between consumer simplicity and multi-chain reality, which is a more durable position than any single-chain feature, because it survives whichever chains win or lose.

The honest counterweight is that "context data" is doing a lot of undefined work in the abstract, and a scope reader should treat the dependent claims, not the summary, as the real boundary. Selecting a chain "based on context data associated with the user, the seller, or the digital asset" is broad enough to invite design-arounds: a competitor that selects a chain by an explicit user setting, or by a fixed routing table, or by liquidity alone, may not perform the recited context-driven determination in the same way. The breadth of the abstract is not the breadth of the claim. As always on this beat, the title and summary are the invitation; the independent claim and its dependents are the contract, and they are what the canonical record exists to let you read.

What the landscape reader should take away is the intent the estate reveals. Block has spent four grants fencing the idea that the host blockchain is a service-side routing decision made per transaction, with stablecoin value threaded through the same rails. As a listed operator (XYZ), Block also describes its crypto and payments strategy to investors — making this family a useful counterpart to that disclosure: the patents are the engineering commitment behind the strategic language. The right way to weigh it is by the family and the prosecution cadence, not by reading the newest grant as a standalone landgrab. All three representative canonical records are deep-linked above so you can walk the claim sets and watch the scope evolve across the lineage.