beta
/Systems And Methods For Cross-computing Architecture Transfer Message Translation
Abstract

A distributed ledger technology application can establish a first connection with a computing application executed by a banking computing infrastructure and a second connection with one or more nodes hosting a distributed ledger via a second communication protocol. The application can receive, from a client device through the through the first connection using the first communication protocol, a receive instruction to complete an asset transfer to transfer an asset from a source account hosted in the banking computing infrastructure to a DLT-based client account. The application can execute an asset conversion agent to determine whether any asset conversion is required. The application can execute an instruction generation agent to generate a new receive instruction. The application can execute a ledger agent to generate an instruction to cause the one or more nodes to add a record of the asset transfer to the distributed ledger.

Full Text

What is claimed is:

A distributed ledger technology application can establish a first connection with a computing application executed by a banking computing infrastructure and a second connection with one or more nodes hosting a distributed ledger via a second communication protocol. The application can receive, from a client device through the through the first connection using the first communication protocol, a receive instruction to complete an asset transfer to transfer an asset from a source account hosted in the banking computing infrastructure to a DLT-based client account. The application can execute an asset conversion agent to determine whether any asset conversion is required. The application can execute an instruction generation agent to generate a new receive instruction. The application can execute a ledger agent to generate an instruction to cause the one or more nodes to add a record of the asset transfer to the distributed ledger.
Timeline
Filed
03/05/2026
Published
07/09/2026
Granted
Not Available
IPC Codes(4)
G06Q 20/40:Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check of credit lines or negative lists
G06F 16/27:Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
G06Q 20/36:using electronic wallets or electronic money safes