# US 2026/0245057 A1 · Multi-Form Currency and Banking System Integrating Multi-Domain Distributed Ledgers, AI-Driven Risk Control, Brand-Franchise Expansion, and Co-Ownership Tokens

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0245057 A1
- Document ID: US20260245057A1
- Status: Published application
- Kind: A1
- Application number: 19/056,745
- Filed: 2025-02-19
- Published: 2026-08-20
- Earliest claimed: 2025-02-19
- Inventors: FURONG BEI
- Web page: https://patentgrep.com/patent/US20260245057A1

## CPC

- G06Q 20/065: {using e-cash}
- G06Q 20/4016: {involving fraud or risk level assessment in transaction processing}
- G06Q 30/0275: {Auctions}
- G06Q 40/024: {Anti-fraud, anti-money laundering or know-your-customer}
- G06Q 40/0325: {specially adapted for detecting or preventing credit or loan fraud}
- G06Q 40/033: {Analysing or forecasting financial condition of borrowers}
- G06Q 40/04: Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
- G06Q 40/06: Asset management; Financial planning or analysis
- G06Q 2220/00: Business processing using cryptography
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

A domain-routed distributed transaction computing system is disclosed. A domain identifier is canonicalized and resolved against a domain namespace registry to retrieve a route object identifying a ledger route, ledger-resident contract interface, compliance metadata, gateway policy, and settlement-evidence schema. A selected versioned compliance block is executed against a transaction request, and an AI-driven risk control module generates a risk indicator converted into a machine-readable enforcement directive. A protocol-level gate prevents signing, ledger submission, cross-ledger bridging, or external payment-network transmission unless the compliance result and enforcement directive satisfy the route object's gateway policy. When permitted, a cross-ledger gateway or external payment-network adapter routes the request and returns gateway execution data. An evidence recorder stores an auditable settlement evidence record linking the domain identifier, route object, compliance block, risk indicator, enforcement directive, gateway execution data, settlement state, and bounded recovery state.

## Claims

### Claim 1

A domain-routed distributed transaction computing system for operating a plurality of domain-routed ledger contract instances, the system comprising:
one or more processors, one or more memories storing executable instructions, and one or more network interfaces:
a domain namespace registry configured to store a plurality of mappings between respective domain identifiers and respective route objects, each route object identifying at least a ledger route, a ledger-resident contract interface, a compliance profile identifier, a gateway policy identifier, a route status, and a settlement-evidence schema identifier:
a namespace resolution module configured to canonicalize a domain identifier included in a transaction request and to deterministically resolve the canonicalized domain identifier against the domain namespace registry to retrieve a corresponding route object:
a contract binding module configured to bind the transaction request to the ledger-resident contract interface identified by the corresponding route object and to verify that the corresponding route object has an active route status before transaction execution;
a pluggable compliance enforcement module configured to select, based on compliance metadata of the corresponding route object, a selected compliance block from a plurality of versioned compliance blocks and to execute the selected compliance block against the transaction request before ledger submission;
an AI-driven risk control module configured to generate a risk indicator for the transaction request from at least ledger transaction history and identity or behavioral evidence and to convert the risk indicator into a machine-readable enforcement directive:
a protocol-level gate configured to prevent signing. ledger submission, cross-ledger bridging, or external payment-network transmission of the transaction request unless a compliance result from the selected compliance block and the machine-readable enforcement directive satisfy the gateway policy of the corresponding route object;
a cross-ledger gateway configured, when the protocol-level gate permits the transaction request. to route the transaction request between the ledger-resident contract interface and at least one external ledger or payment network; and
an evidence recorder configured to generate and store a settlement evidence record linking the domain identifier, the corresponding route object, the selected compliance block, the risk indicator the machine-readable enforcement directive, gateway execution data. and a settlement state.

### Claim 2 (depends on 1)

The system of claim 1, wherein the domain identifier comprises a hierarchical domain namespace including at least one of a country or region layer, an industry layer, an institution layer, an operator layer, a user laver. a delegated sub-namespace laver, or a domain-bound ledger contract layer.

### Claim 3 (depends on 1)

The system of claim 1, wherein the corresponding route object includes at least a domain-identifier hash, a registry version, a contract address, a contract interface identifier, a ledger network identifier, a jurisdiction parameter, the compliance profile identifier, the gateway policy identifier, the route status, and the settlement-evidence schema identifier.

### Claim 4 (depends on 1)

The system of claim 1, wherein the namespace resolution module is further configured to detect whether the domain identifier is unmapped, duplicated, transferred, suspended, revoked. disputed, reserved, or mismatched with the ledger-resident contract interface before the protocol-level gate permits the transaction request.

### Claim 5 (depends on 1)

The system of claim 1, wherein the selected compliance block includes at least one of a know-your-customer rule set, an anti-money-laundering rule set, a sanctions screening rule set, a tax reporting rule set, a stable-token issuance or redemption rule set, an asset-transfer constraint, or a money-transmission constraint.

### Claim 6 (depends on 1)

The system of claim 1, wherein the pluggable compliance enforcement module includes an update interface configured to receive an updated compliance block, validate the updated compliance block, assign a version identifier to the updated compliance block, and apply the updated compliance block to future transaction requests while preserving an existing domain-to-contract mapping and ledger-resident contract state.

### Claim 7 (depends on 1)

The system of claim 1, wherein the machine-readable enforcement directive comprises at least one of approve, deny, hold, throttle, freeze, limit amount, require step-up verification, require collateral-state verification, route to escrow, route to review, use a restricted gateway, or initiate bounded recovery.

### Claim 8 (depends on 1)

The system of claim 1, wherein the AI-driven risk control module generates a feature vector including at least one of a namespace history, a transaction-history value, a compliance-block result, an identity-status value, a behavioral-evidence value, a collateral-status value, a device or session signal, or a prior settlement-outcome value.

### Claim 9 (depends on 1)

The system of claim 1. wherein the cross-ledger gateway includes a lock or escrow interface, a proof generator, a settlement controller, a reconciliation module, and an audit log module configured to maintain state consistency across heterogeneous ledger environments or external payment-network adapters.

### Claim 10 (depends on 1)

The system of claim 1, wherein the settlement evidence record includes at least a namespace header identifying the domain identifier, a route header identifying the corresponding route object, a compliance header identifying a compliance-block version, a risk header identifying the risk indicator or enforcement directive, a gateway header identifying an adapter or proof, and a settlement header identifying a ledger transaction, payment-network reference, proof, or reconciliation state.

### Claim 11 (depends on 1)

The system of claim 1. further comprising a value-instrument routing module configured to associate at least two of physical currency instruments, payment cards, biometric cards, electronic account credits, stable-value digital tokens, algorithmic tokens, cryptocurrencies, non-fungible tokens, time-based token representations, or behavior-based token representations with asset-type fields in the corresponding route object and to submit such value instruments to the protocol-level gate before settlement.

### Claim 12 (depends on 1)

The system of claim 1. further comprising a collateral-state module configured to register collateral-state records, monitor collateral value or borrower status, and generate a machine-readable collateral-state signal that causes the protocol-level gate to select at least one of escrow routing, hold routing, threshold review, collateral substitution, evidence update, quarantine, or a permitted recovery action.

### Claim 13 (depends on 1)

The system of claim 1, further comprising a namespace policy-metadata module configured to store operator parameters, brand-standard parameters, participation-state records, governance-state records, or service-level records as route-controlled metadata associated with the domain identifier, wherein the route-controlled metadata is converted into at least one of a route-status flag, gateway-policy parameter, throttling parameter, operator-permission parameter, suspension flag, or audit flag used by the protocol-level gate.

### Claim 14

A computer-implemented method for operating a domain-routed ledger network, the method comprising:
receiving, by one or more processors, a transaction request associated with a domain identifier:
canonicalizing the domain identifier to produce a canonicalized domain identifier:
resolving the canonicalized domain identifier against a domain namespace registry to retrieve a route object identifying a ledger route, a ledger-resident contract interface, a compliance profile identifier, a gateway policy identifier, and a route status;
verifying that the route object has an active route status;
selecting, based on compliance metadata in the route object, a selected compliance block from a plurality of versioned compliance blocks;
executing the selected compliance block against the transaction request to generate a compliance result;
generating, by an AI-driven risk control module, a risk indicator for the transaction request based on ledger transaction history and identity or behavioral evidence;
converting the risk indicator into a machine-readable enforcement directive;
applying a protocol-level gate based on the compliance result and the machine-readable enforcement directive before signing, ledger submission, cross-ledger bridging, or external payment-network transmission;
when the protocol-level gate permits the transaction request, invoking the ledger-resident contract interface or routing the transaction request through a cross-ledger gateway; and
recording a settlement evidence record linking the domain identifier, the route object, the selected compliance block, the risk indicator, the machine-readable enforcement directive, gateway execution data, and a settlement state.

### Claim 15 (depends on 14)

The method of claim 14, further comprising receiving an updated compliance block through an update interface, validating the updated compliance block, assigning a version identifier to the updated compliance block, and applying the updated compliance block to future transaction requests while preserving an existing domain-to-contract mapping and ledger-resident contract state.

### Claim 16 (depends on 14)

The method of claim 14, wherein applying the protocol-level gate comprises preventing execution of the transaction request when the compliance result fails, when the risk indicator exceeds a threshold, when the route object is inactive, or when the route object fails to satisfy the gateway policy.

### Claim 17 (depends on 14)

The method of claim 14, further comprising routing the transaction request through the cross-ledger gateway to an external payment network or a second distributed ledger having a different address format, contract model, or consensus mechanism.

### Claim 18 (depends on 14)

The method of claim 14, further comprising, responsive to a failed settlement, proof inconsistency, risk threshold breach, compliance violation, route-object mismatch, or namespace mismatch, initiating a bounded recovery action comprising escrow, freeze, retry, hold, reversal where permitted, compensating transaction, dispute marking, quarantine, or administrative review, and updating the settlement evidence record to identify the bounded recovery action.

### Claim 19

A non-transitory computer-readable medium storing instructions that, when executed by one or more processors of a distributed computing system, cause the distributed computing system to perform operations comprising:
maintaining a domain namespace registry comprising mappings between domain identifiers and route objects, each route object identifying at least a ledger route, a ledger-resident contract interface, a compliance profile identifier, a gateway policy identifier, a route status, and a settlement-evidence schema identifier;
receiving a transaction request associated with a domain identifier;
canonicalizing the domain identifier and resolving the canonicalized domain identifier to a corresponding route object:
verifying that the corresponding route object has an active route status and binding the transaction request to the ledger-resident contract interface identified by the corresponding route object;
selecting a versioned compliance block based on compliance metadata associated with the corresponding route object;
generating a risk indicator for the transaction request using an AI-driven risk control module:
generating a machine-readable enforcement directive from the risk indicator;
applying a protocol-level gate before signing, ledger submission, cross-ledger bridging, or external payment-network transmission based on the selected versioned compliance block and the machine-readable enforcement directive; and
recording an auditable evidence record linking the domain identifier, the corresponding route object, the selected versioned compliance block, the risk indicator, the machine-readable enforcement directive, gateway execution data, and a settlement state.

### Claim 20 (depends on 19)

The non-transitory computer-readable medium of claim 19, wherein the operations further comprise storing the auditable evidence record in an append-only log or ledger-anchored record and using the auditable evidence record to verify a bounded recovery action after a failed settlement, compliance violation, risk breach, or route-object mismatch.
