We built something novel for the new cross-domain economy.
So, protecting it was our responsibility.

VXIR compiles human intent into native execution across heterogeneous chains and commercial rails. It is genuinely new engineering — so we documented it and filed to protect it, the way any serious deep-tech effort protects real work. Ten provisional applications record what was built, stage by stage, with the USPTO — the compilation core, gas abstraction, the wallet-and-terminal node mesh and the commerce it carries, cross-domain reach, compliance at the moment of compile, and the non-custodial signing device at the edge.

This page is the plain landscape view: the architecture first, then where each filing applies. No claims that don’t survive a read.

10
Provisional patents filed — patents pending
May 17 2026
First priority date established
Sole inventor
Ladd Craner · VXIR Labs LLC
One pipeline, any destination.

A user or agent expresses intent in plain terms. VXIR encodes it into a chain-agnostic intermediate representation, lowers it through a deterministic translator into the exact native format the destination expects, and hands it back for the user’s own wallet to sign. Non-custodial, end to end. The same pipeline serves payments, token operations, and cross-domain commerce.

01 · Intent
Express
A user or agent states what they want, in plain terms.
02 · IR
Encode
Intent is captured in a chain-agnostic intermediate representation.
03 · Translate
Compile
A deterministic translator lowers the IR to the target’s native format.
04 · Calldata
Emit
Exact native calldata or instructions for the destination, gas resolved.
05 · Sign
User signs
The user’s own wallet signs. Assets never leave their control.
06 · Execute
Settle
The destination executes and returns a verifiable receipt.
Deterministic, not inferred. The translator is a compilation pipeline, not a model that guesses. The same intent compiles the same way every time. A single protocol-family translator reaches an entire VM family — one EVM translator covers a dozen chains — so coverage scales by family, not by one-off integration.
What the filings cover.

The portfolio is organized the way the system is built — following the pipeline from the compilation core out to the network, the commerce layer, the trust layer, and the device at the edge. Each filing is a U.S. provisional application documenting a real part of the work; claim scope is determined at non-provisional conversion with patent counsel.

Zone A

The Compilation Core

Intent → IR → Calldata

This is the engine every other claim depends on. It turns expressed intent into native execution across architecturally different chains through one deterministic pipeline — the foundation the rest of the protocol is built on top of.

64/067,720
Intent-to-Execution Compilation Across Heterogeneous Blockchain Networks
The foundation claim: translating expressed intent into native execution across architecturally different chains through a single compilation pipeline.
First priority · May 17 2026
64/071,922
General-Purpose Intent Compilation
Extends the core beyond payments: the same IR and translator pattern compiles token operations, RWA transfers, and arbitrary on-chain actions.
Filed · May 22 2026
64/069,078
Compilation-Time Gas Fee Abstraction in Cross-Chain Digital Asset Transactions
Gas is resolved as part of compilation, not pushed onto the user. The destination’s fee model is handled inside the pipeline.
Filed · May 19 2026
Zone B

Cross-Domain Reach

Chains + commercial rails

The protocol doesn’t stop at the chain boundary. A single composed intent can settle on-chain and act on a commercial rail in one pipeline — the cross-domain reach that lets the whole system touch real commerce, not just on-chain transfers.

64/073,386
Cross-Domain Intent Compilation
One composed intent spanning a blockchain transaction and a commercial API in a single pipeline — on-chain settlement and a real commercial-rail action compiled together.
Filed · May 23 2026 · proven cross-domain on mainnet
Zone C

The Self-Expanding Network

Wallet & terminal as nodes

The network builds itself. Because every wallet and every merchant terminal is also a relay node, infrastructure scales in proportion to adoption rather than ahead of it — each new participant is both demand and supply.

64/069,081
Convergent Wallet-Node Architecture for User-Proportional Blockchain Network Infrastructure
Every wallet is also a relay node. Each new user adds both demand and supply, so the network scales in proportion to adoption.
Filed · May 19 2026
64/073,829
Merchant Point-of-Sale Terminal as Dedicated Relay Node in a Tiered Intent Compilation Network
The merchant terminal is not just a checkout — it is a tier-two relay node. Commerce hardware becomes network infrastructure.
Filed · May 25 2026
Zone D

Compiled Commerce

The marketplace on the node mesh

Commerce itself becomes a compiled intent. On top of the node network sits a full marketplace — product registration, discovery, purchase, and fulfillment — each step expressed as intent and compiled to execution. This is where the protocol stops being plumbing and becomes a place people actually buy and sell.

64/075,262
Decentralized Commerce Network via Intent Compilation Nodes
The four-tier commerce mesh: discovery, multi-step commercial intents, cryptographic receipts, and a node topology that deploys by region.
Filed · May 27 2026
64/079,781
Compiled Commerce Marketplace: Intent-Compiled Product Registration, Discovery, Purchase, and Fulfillment Through a Decentralized Point-of-Sale Node Network
The end-to-end marketplace claim — listing a product, finding it, buying it, and fulfilling it, all compiled through the decentralized POS node network. The storefront the customer sees; the compilation engine underneath.
Filed · May 2026
Zone E

Trust at Compile Time

Compliance & provenance

The regulatory gap, closed at the source. Compliance and provenance aren’t bolted on after a transaction — they’re bound to the intent the instant it compiles. Every settlement the protocol produces, on any chain or rail, carries a verifiable intent → calldata → receipt trail by construction. That is what lets regulated capital touch the network: you can prove what was authorized and that execution matched it — uniformly, across every intent type.

64/080,007
Compile-Time Compliance Verification and Provenance-at-Origin for Intent Compilation Protocols
Compliance checks and provenance are bound to the intent at the moment it compiles — every settlement carries a verifiable intent-to-calldata-to-receipt trail by construction, so trust is a property of the architecture rather than something reconstructed after the fact.
Filed · Jun 1 2026
Zone F

The Signing Edge

Non-custodial device, any form factor

The non-custodial promise has a physical terminus. The user’s own keys, in cold storage, signing compiled cross-domain calldata — and a provider interface that isn’t married to any one device. The same secure signing surface spans a cold-storage wallet, a handheld, or an embedded terminal. It is the wallet reimagined as the universal, device-independent endpoint of a compilation network.

64/081,973
Non-Custodial Cold-Storage Wallet Device and Form-Factor-Agnostic Provider Interface for Cross-Domain Compilation and Execution
A non-custodial cold-storage signing device — and a provider interface decoupled from any single form factor — bringing cross-domain compile-and-execute to the hardware edge of the network without ever taking custody.
Filed · Jun 3 2026
All ten provisional applications, mapped to the part of the protocol each one protects — from the compilation core to the signing device at the edge. Priority dates run from May 17 2026; the full portfolio is on file with the USPTO.
Non-custodial by construction.

VXIR compiles calldata. The user’s own wallet signs every transaction, and assets never leave their control. That is good architecture — and it produces a clean regulatory profile that the IP is built around.

Not a custodian

Never holds, stores, or controls user assets. The pipeline only produces signable instructions.

Not an exchange

Does not match buyers and sellers or maintain order books. It compiles; it does not trade.

Not a money transmitter

Infrastructure protocol, not a financial service. Value moves between the user and the chain directly.

Full self-custody

The user signs every transaction with their own keys. No temporary custody, no escrow, no exceptions.

Protection, not a flag in the ground.

It’s a discipline, not a land grab

These filings exist for one reason: the work is real and it’s new. Building something genuinely novel and not protecting it isn’t restraint — it’s negligence. So the portfolio is documented the same way the system is built: the core, the network, the commerce layer, and the trust layer recorded together, as one coherent architecture rather than a scattering of isolated tricks.

The point isn’t to fence off a market. It’s to protect what was actually invented — and to do it on the public record, in plain terms, so the claims can be read and checked.

What is — and isn’t — published

  • Provisional, not granted. These are provisional applications — “patents pending.” They establish a priority date; they are not issued patents, and we don’t describe them as such.
  • Claim scope is counsel’s call. Final scope is set during non-provisional prosecution with patent counsel, not asserted here.
  • The architecture is public; the implementation is protected. The pipeline is explained on this page in what-and-why terms. The compilation internals stay in licensed developer documentation — the practical security boundary that protects the engineering, by design.
Priority, and the window.

A provisional application starts a twelve-month clock to non-provisional prosecution. The first priority date is locked; the conversion window runs through mid-2027.

May 17 2026
First priority date established with the foundation compilation filing (64/067,720).
May – Jun 2026
The portfolio was filed across the core, network, commerce, compliance, and device layers as each piece of the work was documented.
May 2027
Non-provisional conversion window opens for the earliest filings; counsel-led prosecution sets final claim scope.

The architecture is provable today.

The compilation engine behind these filings is not a diagram — it has settled 111 real transactions across three VM families, every hash clickable on a public explorer. See the proof for yourself, then see the network it builds.