# US 2026/0312810 A1 · Autonomous computing system for digital asset redemption state control and synchronization of distributed ledger records

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

- Number: US 2026/0312810 A1
- Document ID: US20260312810A1
- Status: Published application
- Kind: A1
- Application number: 19/710,421
- Filed: 2026-06-17
- Published: 2026-10-08
- Earliest claimed: 2024-04-29
- Inventors: John Radman
- Web page: https://patentgrep.com/patent/US20260312810A1

## CPC

- H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)}
- G06Q 20/38215: {Use of certificates or encrypted proofs of transaction rights}
- G06Q 20/3823: {combining multiple encryption tools for a transaction}
- G06Q 20/3825: {Use of electronic signatures}
- G06Q 20/3829: {involving key management}
- G06Q 20/401: {Transaction verification}
- H04L 9/008: {involving homomorphic encryption}
- H04L 9/0825: {using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates}
- H04L 9/3221: {interactive zero-knowledge proofs}
- H04L 9/3247: {involving digital signatures}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- 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 computing system executes redemption-related token state transitions and maintains consistency between token states, ledger states, asset states, and corresponding off-chain records associated with asset tokens, digital currency, or both. The system comprises a network of computing nodes and a redemption module configured to receive redemption requests, evaluate and confirm satisfaction of predefined redemption conditions, execute redemption operations, apply redemption ratios, and cause release, transfer, settlement, or reinstatement of associated assets and reserves. Redemption operations render tokens inoperable, restricted, or eliminated within the current token lifecycle as determined by reference to the token contract, smart contract, legal instrument, or issuance programme from which the tokens were issued or originated. The system generates instructions, authorizations, or triggers to effect corresponding releases or transfers and records cryptographic proofs and ledger entries reflecting resulting token and asset state changes, maintaining synchronization across on-chain, off-chain, and hybrid ledger components upon completion.

## Claims

### Claim 1

A computing system for controlling redemption-related token state transitions and maintaining consistency between token states, ledger states, asset states, and corresponding off-chain records associated with asset tokens, digital currency, or both, the computing system comprising:
(a) a network of computing nodes configured to execute redemption operations, the redemption operations being implementable by any combination of on-chain smart contracts, off-chain applications, backend systems, or computing environments combining on-chain and off-chain components, wherein the computing nodes are configured to record entries in, update entries in, or maintain a ledger system; and
(b) a redemption module, operable by at least one processor and stored on a non-transitory computer-readable medium, configured to:
(i) receive a redemption request associated with one or more asset tokens, digital currency, or both;
(ii) evaluate and confirm satisfaction of one or more predefined redemption conditions associated with the redemption request, wherein the one or more predefined redemption conditions comprise one or more selected from the group consisting of:
(A) expiration of a contractual, staking, or pledge period verified by timestamp data or contract data;
(B) a user-initiated redemption request executed via a secure interface or digital wallet; and
(C) satisfaction of compliance, identity verification, legal, contractual, or governance controls based on one or more of compliance data, identity verification data, legal data, contractual data, or governance data associated with the redemption request and one or more corresponding rules implemented by a smart contract or a programmable rule set;
(iii) execute a redemption operation on the one or more asset tokens, digital currency, or both, wherein the redemption operation causes the one or more asset tokens, digital currency, or both to undergo a token state transition that renders them inoperable, restricted, or eliminated within a current token lifecycle, the token state transition comprising one or more operations selected from the group consisting of:
(A) token elimination operations, comprising burning the one or more asset tokens, digital currency, or both, or rendering the one or more asset tokens, digital currency, or both permanently inoperable and incapable of further transfer, redemption, or use within the current token lifecycle;
(B) token suspension operations, comprising locking, staking, or freezing the one or more asset tokens, digital currency, or both such that the one or more asset tokens, digital currency, or both are prevented from transfer or reuse within the current token lifecycle; and
(C) accounting reversal operations, comprising reversing one or more ledger entries associated with the one or more asset tokens, digital currency, or both;
such that, following the token state transition, the one or more asset tokens, digital currency, or both are prevented from further circulation, transfer, redemption, or reuse within the current token lifecycle, wherein the current token lifecycle is determined by reference to the smart contract, token contract, digital legal instrument, or issuance programme from which the one or more asset tokens, digital currency, or both were issued or originated, including by reference to a contract address or deployment identifier recorded on the ledger system;
(iv) apply a redemption ratio to determine a quantitative relationship between an amount of the one or more asset tokens, digital currency, or both subject to the redemption operation and a corresponding amount of one or more of:
(A) asset tokens to be reinstated upon redemption of digital currency;
(B) pledged or encumbered assets to be released or transferred;
(C) underlying assets or underlying reserves to be released or transferred; or
(D) fiat currency or digital currency equivalents to be released or transferred;
wherein the redemption ratio comprises a fixed ratio, a programmable ratio, a dynamically computed ratio, or a ratio derived from an external data feed, valuation model, oracle, or governance-approved parameter;
(v) cause, based on the redemption ratio and satisfaction of the one or more predefined redemption conditions, one or more of:
(A) reinstatement of the one or more asset tokens;
(B) release of the pledged or encumbered assets;
(C) release or transfer of the underlying assets or underlying reserves;
(D) release or transfer of the fiat currency or digital currency equivalents; or
(E) where the one or more asset tokens, digital currency, or both are created, originated, and exist wholly within the ledger system without any corresponding off-chain underlying asset, reserve, fiat currency equivalent, or digital currency equivalent, recording a settled or terminal redemption status in the ledger system to reflect the resulting on-chain asset state change;
wherein causing the release or transfer comprises generating, transmitting, or recording an instruction, authorization, or trigger that directly or indirectly causes the release, transfer, settlement, or reinstatement to be performed by the computing system or by one or more associated off-chain systems, registries, or infrastructure acting in response to such instruction, authorization, or trigger, whether simultaneously with or following the token state transition;
(vi) record, on the ledger system, a cryptographic proof, a ledger entry, or both, associating the redemption request, the redemption operation, and a token state record reflecting a resulting token state of the one or more asset tokens, digital currency, or both and any associated asset state change arising from the redemption operation; and
(vii) update, in the ledger system, one or more of ledger state records, encumbrance records, lien records, transfer restriction records, compliance records, or settlement records based on completion of the redemption operation and satisfaction of the one or more predefined redemption conditions;
wherein the ledger system comprises at least one of:
(A) an on-chain component configured to validate redemption-related state transitions and, upon validation, record each validated redemption-related state transition as a committed ledger entry in the ledger system; or
(B) an off-chain component configured to maintain one or more off-chain records and, in response to a redemption-related state transition recorded as a committed ledger entry in the ledger system, update the one or more off-chain records to reflect a corresponding release, transfer, settlement, or reinstatement resulting from the redemption operation.

### Claim 2 (depends on 1)

The computing system of claim 1, wherein the one or more asset tokens, digital currency, or both subject to the redemption operation represent at least one of:
(a) real-world assets, comprising real estate, tangible goods or commodities, or cash deposits or currency;
(b) financial assets, comprising debt instruments, equity instruments, financial derivatives, convertible instruments, hybrid securities, or digitally native instruments issued and maintained within the computing system; or
(c) intangible assets, comprising intellectual property, royalties, accounts receivable, digital assets, or other contractual or legally enforceable rights or claims.

### Claim 3 (depends on 1)

The computing system of claim 1, wherein the one or more asset tokens subject to the redemption operation are configured as at least one of:
(a) parameterised representations of monetary, physical, statistical, contractual, or performance-related attributes of an underlying asset;
(b) units, portions, time-based entitlements, or shares representing an economic, contractual, or temporal interest associated with an underlying asset; or
(c) rights-linked or utility-linked digital representations configured to provide authorization, control, or access to functions relating to an underlying asset, or to enable participation in corporate action events, distribution events, reward disbursement events, or governance actions.

### Claim 4 (depends on 1)

The computing system of claim 1, wherein the redemption ratio is one of:
(a) a fixed ratio, predetermined and immutable for the duration of the current token lifecycle;
(b) a programmable or dynamically computed ratio, calculated at the time of redemption based on system-configured parameters, market conditions, or governance rules; or
(c) a ratio derived from an external data feed or oracle;
and wherein, for ratios under (b) or (c), one or more governance rules permit the redemption ratio to be adjusted in response to market conditions, risk parameters, or predefined governance rules, with any adjustment recorded as a committed ledger entry prior to application in a subsequent redemption operation.

### Claim 5 (depends on 1)

The computing system of claim 1, wherein one or more smart contracts are configured to autonomously enforce predefined redemption conditions and rules by performing one or more of:
(a) executing token state transitions and applying the redemption ratio in response to user-initiated redemption requests or system-detected redemption-triggering conditions;
(b) automatically initiating release or transfer of pledged or encumbered assets, underlying assets or underlying reserves, or fiat currency or digital currency equivalents upon satisfaction of predefined redemption conditions;
(c) establishing, managing, and extinguishing pledged, encumbered, or linked states of underlying assets or underlying reserves, including through digital liens, digitally represented mortgage instruments, or digitally represented contractual instruments; or
(d) consuming external data provided through authenticated oracle mechanisms to autonomously trigger redemption operations or update ledger-recorded states of asset tokens or digital currency.

### Claim 6 (depends on 1)

The computing system of claim 1, wherein one or more smart contracts implement a dual contract architecture comprising:
(a) a base lifecycle smart contract configured to encode and enforce system-wide rules governing redemption conditions, token state transitions, and redemption ratios; and
(b) a per-asset or per-issuance smart contract instance configured to store asset-specific parameters, compliance conditions, pledge, encumbrance, or linkage rules, and redemption ratio parameters;
wherein each per-asset or per-issuance smart contract instance is linked to the base lifecycle smart contract such that redemption operations are governed by both the system-wide rules and the asset-specific parameters.

### Claim 7 (depends on 1)

The computing system of claim 1, wherein the network of computing nodes implements a decentralised ledger architecture comprising one or more of a blockchain-based network, a peer-to-peer system, or another distributed ledger technology, wherein the ledger system is realised as a public, private, or hybrid distributed ledger in a permissioned or permissionless configuration, and wherein the network is further configured to validate and record redemption operations and token state transitions using one or more consensus mechanisms comprising proof-based, voting-based, or hybrid consensus protocols.

### Claim 8 (depends on 1)

The computing system of claim 1, wherein cryptographic verification protocols and at least one of a secure software interface or a secure wallet interface are configured to authenticate user interactions and authorize redemption operations, the computing system being further configured to perform one or more of:
(a) employing asymmetric cryptography, multi-signature authentication, or threshold signature schemes to authorize redemption operations and corresponding release, transfer, or reinstatement operations;
(b) applying post-quantum cryptographic signature schemes, zero-knowledge proofs, or multi-factor authentication to verify user identity or transaction authorization prior to execution of a redemption operation; or
(c) implementing time-locked transaction releases or hardware-wallet-based or cold-wallet-based key storage to secure authorization of redemption operations.

### Claim 9 (depends on 1)

The computing system of claim 1, wherein causing the release or transfer comprises generating, transmitting, or recording an instruction, authorization, or trigger communicated to one or more off-chain systems, and wherein the computing system is further configured to perform one or more of:
(a) monitoring the status of off-chain release or transfer operations initiated in response to the token state transition and recording a confirmed or failed settlement status as a committed ledger entry in the ledger system, wherein the committed ledger entry records the confirmed or failed settlement outcome; or
(b) where an off-chain release or transfer operation fails, initiating a reversal or remediation operation comprising retrying, reversing, or recording a failed status for the release or transfer operation and recording a failed redemption status or a redemption status corresponding to reversal of the release or transfer operation in the ledger system.

### Claim 10 (depends on 1)

The computing system of claim 1, wherein the one or more predefined redemption conditions further comprise one or more of:
(a) a regulatory trigger event determined by a regulatory authority, supervisory body, or automated compliance system;
(b) a counterparty default or insolvency event associated with the asset tokens or digital currency subject to the redemption request;
(c) a collateral deficiency condition determined by reference to market pricing data, valuation data, or oracle-provided data;
(d) a scheduled maturity date or contractual termination event recorded in a token contract, digital legal instrument, or issuance programme; or
(e) a governance-approved redemption condition comprising satisfaction of a voting threshold, quorum requirement, or other governance decision-making process encoded in the smart contract or programmable rule set.
