WO2022125726A1

WO2022125726A1 - System and method for decentralized exchange of digital assets on a computer network

Info

Publication number: WO2022125726A1
Application number: PCT/US2021/062521
Authority: WO
Inventors: Levy Cohen
Original assignee: Wellfield Technology Ir Limited; The IP Law Firm of Guy Levi, LLC
Priority date: 2020-12-09
Filing date: 2021-12-09
Publication date: 2022-06-16

Abstract

The disclosure relates to systems, methods and programs for automatic conversion/exchange of digital assets on decentralized computerized networks. Specifically, the disclosure relates to systems, programs and methods for independent validation of conversion and/or exchange of digital assets associated with blockchain networks by forming trans action- specific marketplace of traders resulting in the conversion/exchange of digital assets, using an exchange-network specific and blockchain- agnostic conversion token.

Description

SYSTEM AND METHOD FOR DECENTRALIZED EXCHANGE OF DIGITAL

ASSETS ON A COMPUTER NETWORK

BACKGROUND

[001] The present disclosure is directed to exchange of digital assets on decentralized computerized systems. Specifically, the disclosure is directed to systems, methods and articles of manufacture with computer-readable media for independent validation of conversion and/or exchange of digital assets in decentralized computer networks.

[002] The exchange of data or goods should ideally only be carried out between trusted (or known) parties, such that at least the source and the target of the exchange are known to each other. Alternatively, a centralized entity, trusted by both parties to the exchange can act as an intermediary to the exchange. Recently blockchain technology has been integrated into multiple new domains such as shipping container management, smart contracts, and medical record databases, while creating decentralized computer networks that are capable of performing complex computations without a central processor (in other words, the trusted intermediary), allowing various actions in at least pseudotrustless environment. Each such decentralized computer network maintains a data ledger where all operations on the network are registered, and where each computing node of the network has a full copy of the ledger so that there is no need for a central processor to facilitate the computations.

[003] Algorithms for operation of decentralized computer networks typically require that data transfer between nodes of the computer network be registered on the data ledger and also be accompanied with an exchange of data tokens. Each data token comprises dedicated code that is associated with the corresponding decentralized computer network. Tokens associated with a specific digital asset, may comprise various data types, for example addresses, passwords, medical records, inventory list, images, etc., where different computer networks may be dedicated to different digital-asset-specific token. [004] Currently automatic, decentralized solution for matching and exchanging between different types of digital- as set- specific tokens as well as exchanging between completely trustless and/or anonymous parties. In order to exchange two different types of such digital-asset-specific tokens, a user typically must use a third trusted central intermediate party to exchange a data token (e.g., a “Bitcoin” of type ‘A’) with a commonly available commodity (e.g., fiat currency, typically government issued currency) and then exchange again the received commodity, usually with a different trusted party, for a data token of a different type (e.g., Ethereum of type ‘B’).

[005] These shortcomings are addressed by the following disclosure.

SUMMARY:

[006] In exemplary implementations, provided herein are systems, methods and programs for independent validation of conversion and/or exchange of digital assets in computer networks using a conversion and/or exchange token specific to the exchangenetwork.

[007] In another exemplary implementation, provided herein is an article of manufacture comprising a non-transitory memory storage device storing thereon a computer readable medium (CRM) for converting digital assets on a computer network having a plurality of nodes, the CRM comprising a set of executable instructions configured to, when executed by at least one processor, cause the at least one processor to perform the steps of: receiving a plurality of requests for conversion between digital assets; matching at least one pair of digital assets sought to be exchanged; assigning, a first node of the computer network for: receiving at least a portion of the first digital asset of the pair of digital assets sought to be converted from a first computerized device associated with the computer network; and exchanging the at least portion of the first digital asset of the pair of digital assets sought to be converted, with a first amount of a conversion token; and assigning a second node of the computer network for: receiving at least a portion of a second digital asset of the pair of digital assets sought to be converted from a second computerized device associated with the computer network; and exchanging the at least portion of the second digital asset of the pair of digital assets sought to be converted with a second amount of the conversion token data type, wherein the conversion token is associated with the computer network, and wherein the amount of conversion token associated with each of the first and second digital assets corresponds to an exchange rate between each digital asset. [008] In yet another exemplary implementation, provided herein is a computerized system for converting digital assets, the system comprising: a computer network with a plurality of nodes, whereby each computing node comprises at least one processor and is assigned to perform digital asset conversion for a digital-asset- specific token; and a plurality of data receivers, operable to receive requests from a plurality of computerized devices, each computerized device associated with the computer network, wherein the system further comprises a distributed processing module (DPM) having at least one processor, the DPM being in communication with each node on the computer network, and with a non-transitory memory storage device storing thereon a processor-readable medium (CRM) with a set of executable instructions, configured, when executed to cause at least one of: the at least one node processor, and the at least one DPM processor to: receive a plurality of requests for conversion between digital-asset- specific tokens; match at least on pair of digital assets sought to be exchanged; assign a first node of the computer network to: receive at least a portion of the first digital asset of the pair of digital assets sought to be converted from a first computerized device associated with the computer network; and exchange the at least portion of the first digital asset of the pair of digital assets sought to be converted, with a first amount of a conversion token; and assign a second node of the computer network to: receive at least a portion of a second digital asset of the pair of digital assets sought to be converted from a second computerized device associated with the computer network; and exchange the at least portion of the second digital asset of the pair of digital assets sought to be converted with a second amount of the conversion token data type, wherein the conversion token is associated with the computer network, and wherein the amount of conversion token associated with each of the first and second digital assets corresponds to an exchange rate between each digital asset.

BRIEF DESCRIPTION OF THE DRAWINGS

[009] For a better understanding of the systems, programs and methods for for independent validation of conversion and/or exchange of digital assets in computer networks using a conversion and/or exchange token specific to the exchange-network, with regard to the implementations thereof, reference is made to the accompanying examples and figures, in which:

[010] Fig. 1 shows a block diagram of an exemplary implementation of the computing device;

[Oi l] Fig. 2 A shows a block diagram of an exemplary implementation of the data conversion system, with Fig. 2B showing a block diagram of an exemplary implementation of the computer network;

[012] Fig. 3A shows a block diagram of an exemplary implementation of the conversions in the computer network, with Fig. 3B schematically illustrating an exemplary implementation of the initial data type conversions between computerized devices with the data conversion system, and Fig. 3C schematically illustrates an exemplary implementation of the final data type conversions between computerized devices with the data conversion system; and

[013] Fig. 4 shows a flowchart for an exemplary implementation of a method of data conversion in a computer network.

[014] It will be appreciated that for simplicity and clarity of illustration, elements shown in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity. Further, where considered appropriate, reference numerals may be repeated among the figures to indicate corresponding or analogous elements.

DETAILED DESCRIPTION

[015] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the invention. However, it will be understood by those skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, and components have not been described in detail so as not to obscure the present invention. [016] Although exemplary implementations of the invention are not limited in this regard, discussions utilizing terms such as, for example, “processing,” “computing,” “calculating,” “determining,” “establishing”, “analyzing”, “checking”, or the like, may refer to operation(s) and/or process(es) of a computer, a computing platform, a computing system, or other electronic computing device, that manipulates and/or transforms data represented as physical (e.g., electronic) quantities within the computer’s registers and/or memories into other data similarly represented as physical quantities within the computer’s registers and/or memories or other information non-transitory storage medium that may store instructions to perform operations and/or processes. Although exemplary implementations of the invention are not limited in this regard, the terms “plurality” and “a plurality” as used herein may comprise, for example, “multiple” or “two or more”. The terms “plurality” or “a plurality” may be used throughout the specification to describe two or more components, devices, elements, units, parameters, or the like. The term set when used herein may comprise one or more items. Unless explicitly stated, the method exemplary implementations described herein are not constrained to a particular order or sequence. Additionally, some of the described method exemplary implementations or elements thereof can occur or be performed simultaneously, at the same point in time, or concurrently.

[017] According to some exemplary implementations, methods and systems are provided for automatic validation (in other words, the successful demonstration that a process, procedure, method, or activity - actually and consistently fulfills specific, predetermined and ascertainable requirement(s)) of data conversion and/or exchange in a trustless decentralized computer network, with automatic identification of compatible requests for conversion and/or exchange between digital-asset-specific tokens and assignment of computing nodes to convert and/or exchange the tokens. In some exemplary implementations, conversion between different data types may be facilitated with at least one conversion token that is associated solely with the computer network, for example a data token facilitating data exchange in an associated blockchain network or a data token including information of data type that was exchanged between at least two computing nodes of the computer network. It should be noted that while digitalas set- specific tokens are discussed hereinafter, the following may also apply to any type of data exchange.

[018] In the context of the disclosure, the term “node” means a computing system operable to handle blockchain transactions. The nodes may be of various type and/or architecture and may run different operating systems. Their performance abilities to handle blockchain transactions, network bandwidth, storage and/or memory capacities, and processing power may vary from node to node. Likewise, in the context of the disclosure, the term “transaction” refers to a transfer, record, or authorization of access of one or more assets. A transaction can be a transfer of one or more assets between one or more parties. For example, a transaction can be a sale of one asset for an amount of another asset (e.g., sale of one Bitcoin for Dogecoin). A transaction can be a record of access and/or authorization of access of data corresponding to one or more assets. For example, if medical records are stored as an asset, a transaction can be a record of access of medical records associated with an individual and/or authorization of access to the medical records.

[019] In the context of the disclosure, a “compatible request” means any exchange and/or transaction request, which, when entered into the system, can result in the fulfillment of the request.

[020] Reference is made to Fig. 1, which shows block diagram of an exemplary implementation of the computing device. Device 100 may comprise controller 105 that may be, for example, central processing unit processor (CPU), chip or any suitable computing or computational device, operating system 115, memory 120, executable code 125, storage system 130 that may comprise input devices 135 and output devices 140. Controller 105 (or one or more controllers or processors, possibly across multiple units or devices) may be configured to carry out methods described herein, and/or to execute or act as the various modules, units, etc. More than one computing device 100 may be comprised in, and one or more computing devices 100 may act as the components of, system according to exemplary implementations of the invention.

[021] Operating system 115 may be or may comprise any code segment (e.g., one similar to executable code 125 described herein) designed and/or configured to perform tasks involving coordination, scheduling, arbitration, supervising, controlling or otherwise managing operation of computing device 100, for example, scheduling execution of software programs or tasks or enabling software programs or other modules or units to communicate. Operating system 115 may be a commercial operating system. It will be noted that operating system 115 may be an optional component, e.g., in some exemplary implementations, a system may comprise a computing device that does not require or comprise an operating system 115. For example, a computer system may be, or may comprise, a microcontroller, an application specific circuit (ASIC), a field programmable array (FPGA) and/or system on a chip (SOC) that may be used without an operating system.

[022] Memory 120 may be or may comprise, for example, a Random Access Memory (RAM), a read only memory (ROM), a Dynamic RAM (DRAM), a Synchronous DRAM (SD-RAM), a double data rate (DDR) memory chip, a Flash memory, a volatile memory, a non-volatile memory, a cache memory, a buffer, a short term memory unit, a long term memory unit, or other suitable memory units or storage units. Memory 120 may be or may comprise a plurality of, possibly different memory units. Memory 120 may be a computer or processor non-transitory readable medium, or a computer non-transitory storage medium, e.g., a RAM.

[023] Executable code, or set of instructions 125 may be any executable code, e.g., an application, a program, a process, task or script. Executable code 125 may be executed by controller 105 possibly under control of operating system 115. Although, for the sake of clarity, a single item of executable code 125 is shown in Fig. 1, a system may comprise a plurality of executable code segments similar to executable code 125 that may be loaded into memory 120 and cause controller 105 to carry out methods described herein.

[024] Accordingly and in an exemplary implementation, provided herein is an article of manufacture comprising a non-transitory memory storage device storing thereon a computer readable medium (CRM) for converting digital assets on a computer network having a plurality of nodes, the CRM comprising a set of executable instructions configured to, when executed by at least one processor, cause the at least one processor to perform the steps of: receiving a plurality of requests for conversion between digital assets; matching at least on pair of digital assets sought to be exchanged; assigning, a first node of the computer network for: receiving at least a portion of the first digital asset of the pair of digital assets sought to be converted from a first computerized device associated with the computer network; and exchanging the at least portion of the first digital asset of the pair of digital assets sought to be converted, with a first amount of a conversion token; and assigning a second node of the computer network for: receiving at least a portion of a second digital asset of the pair of digital assets sought to be converted from a second computerized device associated with the computer network; and exchanging the at least portion of the second digital asset of the pair of digital assets sought to be converted with a second amount of the conversion token data type, wherein the conversion token is associated with the computer network, and wherein the amount of conversion token associated with each of the first and second digital assets corresponds to an exchange rate between each digital asset.

[025] Storage system 130 may be or may comprise, for example, a flash memory as known in the art, a memory that is internal to, or embedded in, a micro controller or chip as known in the art, a hard disk drive, a CD-Recordable (CD-R) drive, a Blu-ray disk (BD), a universal serial bus (USB) device or other suitable removable and/or fixed storage unit. Content may be stored in storage system 130 and may be loaded from storage system 130 into memory 120 where it may be processed by controller 105. In some exemplary implementations, some of the components shown in Fig. 1 may be omitted. For example, memory 120 may be a non-volatile memory having the storage capacity of storage system 130. Accordingly, although shown as a separate component, storage system 130 may be embedded or comprised in memory 120.

[026] Input devices 135 may be or may comprise any suitable input devices, components or systems, e.g., a detachable keyboard or keypad, a mouse and the like. Output devices 140 may comprise one or more (possibly detachable) displays or monitors, speakers and/or any other suitable output devices. Any applicable input/output (RO) devices may be connected to computing device 100 as shown by blocks 135 and 140. For example, a wired or wireless network interface card (NIC), a universal serial bus (USB) device or external hard drive may be comprised in input devices 135 and/or output devices 140. It will be recognized that any suitable number of input devices 135 and output device 140 may be operatively connected to computing device 100 as shown by blocks 135 and 140. For example, input devices 135 and output devices 140 may be used by a technician or engineer in order to connect to a computing device 100, update software and the like. Input and/or output devices or components 135 and 140 may be adapted to interface or communicate.

[027] Exemplary implementations of the systems, methods and programs disclosed and claimed herein may comprise an article such as a computer or processor non-transitory readable medium (interchangeable with CRM), or a computer or processor non-transitory storage medium, such as for example a memory, a disk drive, or a USB flash memory, encoding, including or storing instructions, e.g., computer-executable instructions, which, when executed by a processor or controller, carry out methods disclosed herein. For example, a storage medium such as memory 120, computer-executable instructions such as executable code 125 and a controller such as controller 105.

[028] The storage medium may comprise, but is not limited to, any type of disk including magneto-optical disks, semiconductor devices such as read-only memories (ROMs), random access memories (RAMs), such as a dynamic RAM (DRAM), erasable programmable read-only memories (EPROMs), flash memories, electrically erasable programmable read-only memories (EEPROMs), magnetic or optical cards, or any type of media suitable for storing electronic instructions, including programmable storage devices.

[029] Exemplary implementations may comprise components such as, but not limited to, a plurality of central processing units (CPU) or any other suitable multi-purpose or specific processors or controllers (e.g., controllers similar to controller 105), a plurality of input units, a plurality of output units, a plurality of memory units, and a plurality of storage units. A system may additionally comprise other suitable hardware components and/or software components. In some exemplary implementations, a system may comprise or may be, for example, a personal computer, a desktop computer, a mobile computer, a laptop computer, a notebook computer, a terminal, a workstation, a server computer, a Personal Digital Assistant (PDA) device, a tablet computer, a network device, or any other suitable computing device.

[030] In some exemplary implementations, the system may comprise or may be, for example, a plurality of components that comprise a respective plurality of central processing units (in other words, distributed processing module DPM), e.g., a plurality of CPUs as described, a plurality of chips, FPGAs or SOCs, a plurality of computer or network devices, or any other suitable computing device. For example, a system as described herein may comprise one or more devices such as the computing device 100.

[031] Accordingly and in another exemplary implementation, provided herein is a computerized system for converting digital assets, the system comprising: a computer network with a plurality of nodes, whereby each computing node comprises at least one processor and is assigned to perform digital asset conversion for a digital- as set- specific token; and a plurality of data receivers, operable to receive requests from a plurality of computerized devices, each computerized device associated with the computer network, wherein the system further comprises a distributed processing module (DPM) having at least one processor, the DPM being in communication with each node on the computer network, and with a non-volatile memory storage device storing thereon a processor- readable medium with a set of executable instructions, configured, when executed to cause at least one of the at least one node processor, and the at least one DPM processor to: receive a plurality of requests for conversion between digital- as set- specific tokens; match at least on pair of digital assets sought to be exchanged; assign a first node of the computer network to: receive at least a portion of the first digital asset of the pair of digital assets sought to be converted from a first computerized device associated with the computer network; and exchange the at least portion of the first digital asset of the pair of digital assets sought to be converted, with a first amount of a conversion token; and assign a second node of the computer network to: receive at least a portion of a second digital asset of the pair of digital assets sought to be converted from a second computerized device associated with the computer network; and exchange the at least portion of the second digital asset of the pair of digital assets sought to be converted with a second amount of the conversion token data type, wherein the conversion token is associated with the computer network, and wherein the amount of conversion token associated with each of the first and second digital assets corresponds to an exchange rate between each digital asset.

[032] Turning to Fig. 2A which shows a block diagram of a data conversion system 200. The direction of arrows in Fig. 2A may indicate the direction of information flow.

[033] The data conversion system 200 may comprise a decentralized computer network 210 with a plurality of computing nodes 201a, 201b, 201c. Each computing node may comprise a processor (e.g., similar to controller 105 as shown in Fig. 1) and perform data type conversions and/or exchange for at least one specific token data type. It should be noted that while only three computing nodes are shown in Fig. 2 A, computer network

210 may comprise any number of such nodes. [034] According to some exemplary implementations, conversion and/or exchange between digital-asset- specific tokens may refer to conversion between different data types. Therefore and in the context of the disclosure, the term “digital asset” means any electronic data capable of being presented in digital form that can be assigned a value, and be stored and shared (transmitted) between devices.

[035] For example, conversion and/or exchange between digital-asset- specific tokens may refer to conversion and/or exchange between different data formats (e.g., exchanging an loT data with an electric power meter data). In some exemplary implementations, conversion and/or exchange between data types may be carried out with digital-asset- specific tokens having different cryptographic codes (e.g., converting a digital-asset-specific token with SHA-256 hash for a token with MD5 hash cryptographic codes).

[036] The various computing devices described in the figures may comprise components such as shown in Fig. 1. For example, in some exemplary implementations, each computing node may comprise memory and a dedicated operating system (e.g., similar to memory 120 and a dedicated operating system 115 as shown in Fig. 1) such that a conversion algorithm (e.g., similar to executable code 125 as shown in Fig. 1) may be implemented in computer network 210 in each computing nodes 201a, 201b, 201c. In some exemplary implementations, computing nodes 201a, 201b, 201c may be connected via a network 212, for example associated with a decentralized blockchain network. Network 212 is shown in the figures only partially, but may be one or more networks connecting all relevant devices, such as the internet.

[037] In some exemplary implementations, decentralized computer network 210 may comprise at least two data receivers (interchangeable with transceivers) 202 operable to receive conversion requests for data 205a, 205b from a plurality of computerized devices 203, 204 associated with computer network 210. For example, a user may use computerized device 204 (e.g., a PC, similar to device 100 as shown in Fig. 1) with a dedicated algorithm to allow data exchange with the decentralized computer network 210.

[038] In some exemplary implementations, data receivers (transceivers) 202 may distribute the received conversion requests 205a, 205b throughout computer network 210 such that each computing node 201a, 201b, 201c may anonymously record all of the received conversion requests 205a, 205b, since the source and target of the requests are unaware of the each other thereby creating trustless data exchange. It should be noted that data receivers (transceivers) 202 may only receive requests in unidirectional communication, whereby users of computerized devices 203, 204 associated with computer network 210 may check operations of computer network 210 using a network connection 20 (e.g., via the internet) to blockchain networks 221a, 221b, 221c to observe transactions carried thereon, thus also reducing processing power on computer network 210 since computerized devices 203, 204 only broadcast requests 205a, 205b without a corresponding response for each request.

[039] In order to perform a transaction of digital-asset-specific tokens in a single blockchain network, users with digital-asset- specific tokens are typically required to use dedicated software applications (or “wallets”) with their personal password (or private key) such that tokens may be transferred to different nodes of that blockchain network. In some exemplary implementations, users with digital-asset-specific token may utilize data conversion system 200 to convert and/or exchange the digital assets associated with some or all of their tokens.

[040] In certain exemplary implementations, at least one computing node 201a, 201b, 201c is assigned by computer network 210 to analyze the received conversion and/or exchange requests 205a, 205b and determine a first request 205a (e.g., as shown in Fig. 3 A) corresponding to a first conversion/exchange 301 from a first digital- as set- specific token 211a to/with a second digital-asset-specific token 211b and a second request 205b corresponding to a second conversion/exchange 302 from the second digital-asset- specific token 21 lb to/with the first digital-asset-specific token 211a, the first and second conversions 301, 302 being paired and transacted in opposite direction. In some exemplary implementations, the at least one computing node 201a, 201b, 201c may also determine a third request 205c corresponding to a third conversion/exchange 303 from the second digital-asset-specific token 211b to/with a third digital-asset-specific token 211c. For example, the first conversion/exchange 301 may be from type ‘A’ to/with type ‘B’, the second conversion/exchange 302 may be from type ‘B’ to/with type ‘C’, and the third conversion/exchange 303 may be from type ‘C’ to/with type ‘A’ so that decentralized computer network 210 may determine an exchange between the first, second, and third conversions/exchanges 301, 302, 303 to finally convert type ‘A’ to ‘C’, while satisfying all the exchange requirements (e.g., amounts, price, timing, consensus and the like). It should be noted that any other number of conversions/exchanges may be determined such that a long chain of such conversions may be created to allow all parties to anonymously exchange their digital-asset- specific tokens, as further described hereinafter. In addition, in certain implementations the decentralized computer network 210 is operable to determine and execute partial exchange between the first, second, and third (or conversions/exchanges 301, 302, 303.

[041] According to some exemplary implementations, computer network 210 may be associated with a decentralized blockchain network having a dedicated conversion token 206, and all operations of the computer network may be carried out automatically (in other words, without a user’s intervention beyond sending the exchange/conversion request). In some exemplary implementations, operations of conversion token 206, such as switching between different computing nodes and/or computerized devices, is registered on the associated decentralized blockchain network. For example, exchanges may be registered on the ledger of the corresponding blockchain network, while other operations (e.g., exchange rate determination, recording of requests, creating the exchange flow etc.) may be registered elsewhere, for example on a dedicated decentralized database 250 as shown in Fig. 2B, thereby also reducing processing requirements of the associated decentralized blockchain network. Conversion tokens’ registration on a ledger may be, in some exemplary implementations, carried out with registration of token exchange between at least two computing nodes (e.g., registering amount of tokens before and after the exchange in each computing node). In certain exemplary implementations, each digital-asset-specific token 211a, 211b, 211c processed by computer network 210 may be associated with a single blockchain network 221a, 221b, 221c. For example, digital-asset-specific token 211b (e.g., a token with information from an internet of things (loT) devices) may be handled by an loT-dedicated blockchain network 221b.

[042] It should be noted that since the majority of current blockchain networks use different technologies and/or different algorithms, formatting a conversion token operable to communicate between blockchain networks dedicated to different digital assets may be required in order to switch two digital-asset- specific tokens.

[043] In another exemplary implementation, each computing node 201a, 201b, 201c may store a predetermined amount (e.g., number of tokens) of conversion tokens 206 in order to enable conversions and/or exchanges between digital-asset-specific tokens. Conversion token 206 may be utilized for data transfer with a blockchain network associated with computer network 210, wherein conversion token 206 may differ from other digital-asset- specific tokens in data type. For example, conversion token 206 may comprise data that may be transferred between computing nodes of computer network 210 via an exchange of conversion token 206.

[044] In an exemplary implementation, single computing node(s) 201a, 201b, 201c may be assigned by computer network 210 to carry out each data type conversion. For example, first computing node 201a is assigned to the first digital-asset-specific token 211a and carry out the first conversion 301, and second computing node 201b is assigned to the second token data type 211b and carry out the second conversion 302. In an exemplary implementation, computer network 210 is operable to determine an exchange rate (e.g., for a limited time period) for each conversion between two digital assets sought to be converted/exchanged such that an amount of digital-asset-specific token for each exchange may thereby be determined. An example of conversion between two digital assets is shown in Figs. 3B-3C.

[045] Turning now to Fig. 2B, illustrating an example block diagram of computer network 210. The direction of arrows in Fig. 2B indicates the direction of information flow. In some exemplary implementations, computer network 210 comprise at least one database 250, for example each computing node(s) 201a, 201b, 201c is in communication with corresponding databases 250 (e.g., similar to the storage system 130 as shown in Fig. 1), operable to store received conversion requests 205. All databases 250 store in certain configurations, received conversion requests 205 in parallel and/or store the determined first conversion 301 and second conversion 302 in parallel. Moreover, computer network 210 may be associated with a decentralized blockchain network with dedicated conversion token 206, and thus each database 250 (and for that matter, each node 201a, 201b, 201c associated therewith) stores a complete data ledger of the entire blockchain for exchanges of conversion token 206, such that operations of computer network 210 may be substantially simultaneously registered in each database 250.

[046] Turning back to Fig. 2A, computer network 210 used in the systems implementing the programs and methods disclosed, may be configured to assign the first computing node 201a to receive a first amount of first digital-asset specific token 211a from first computerized device 203 associated with the computer network in accordance with at least one conversion request 205a, 205b, and convert and/or exchange from the first amount of first digital-asset specific token 211a to a first amount of conversion token 206. Computer network 210 may also assign second computing node 201b to receive a second amount of second digital-asset specific token 211b from second computerized device 204 associated with computer network 210, and convert and/or exchange the second amount of second digital-asset specific token 211b with a second amount of the conversion token 206. Accordingly, the amount of conversion token 206 is configured to correspond to an exchange rate from each digital-asset-specific token(s) 211a, 21 lb, 211c to conversion token 206, for example an aggregated exchange rate that may be determined for a predetermined time period (e.g., calculated every five minutes, or may be valid for only a certain time period) by at least one computing node 201a, 201b, 201c (e.g., selected randomly). For example, an exchange rate may be determined for a predetermined limited time period (e.g., five minutes) and accordingly the amount of digital-asset-specific tokens corresponding to that exchange rate may be determined (e.g., four tokens of digital asset ‘A’ in exchange for seven tokens of digital asset ‘B’) until the exchange rate changes. Accordingly, each conversion from digital-asset-specific token(s) 211a, 211b, 211c to conversion token 206 may be at least partially registered on a separate blockchain network 221a, 221b, 221c, as further described hereinafter.

[047] In the systems comprising the programs disclosed and implementing the methods described, at least some operations of computer network 210 are executed utilizing the processing power of computerized devices 203, 204 associated with computer network 210. For example, calculation of the aggregated exchange rate may be carried out utilizing the processing power of at least one computerized device 203, 204 and then distributed to computer network 210. [048] For example, a first user of first computerized device 203 associated with computer network 210 (e.g., associated with a dedicated software code embedded therein) may request a conversion and/or exchange from a first digital-asset specific token 211a in an amount of five tokens to be exchanged with a second digital-asset specific token 211b in accordance with predetermined (time-limited) exchange rate where each first digital-asset specific token 211a may be exchanged for two second digital-asset specific token 211b. A second user of second computerized device 204 associated with computer network 210 may request an opposite conversion and/or exchange, from a second digital-asset specific token 211b in an amount of ten tokens to be exchanged with a first digital-asset specific token 21 la according to the predetermined exchange rate. Thus, computer network 210 assigns first computing node 201a for the first conversion 301, and the second computing node 201b for the second conversion 302. As described herein, at least three conversions 301, 302, 303 may be calculated by computer network 210 to perform a complex exchange such that all parties receive the desired digital assets, for example if a pair of opposite conversions is not identified.

[049] In other words, in matching a pair of traders, each with their own digital-asset- specific tokens, each who wishes to trade (convert or exchange) their digital asset, the systems and programs disclosed herein will automatically search among computing node(s) 201a, 201b, 201c for a third trader having its own digital-asset- specific token wishing to trade, that will satisfy all parties’ trades.

[050] It should be noted that using system 200 the overall processing power used for the conversion between different types of digital-asset- specific tokens may be reduced since there is no longer a need to comprise third parties to calculate exchange rates, separately register on blockchain networks and validate transactions.

[051] Turning now to Fig. 3A illustrating a block diagram of digital asset conversions 301, 302, 303 in computer network 210. The direction of arrows in Fig. 3A may indicate the direction of information flow.

[052] In an exemplary implementation, computer network 210 may be configured to assign the first computing node 201a to carry out the first conversion 301 (for the first conversion request 205a) and transfer the first amount of first digital-asset specific token 211a to the second computerized device 204, and receive the second amount of the conversion token 206. Similarly, computer network 210 may be configured to assign second computing node 201b to carry out the second conversion 302 (for the second conversion request 205b) and transfer the second amount of second digital-asset specific token 211b to the first computerized device 203, and receive the first amount of conversion token 206. Computer network 210 may similarly be configured to assign the third computing node 201c to carry out the third conversion 303 (for the third conversion request 205c) and transfer a third amount of second digital-asset-specific token 211c to the first computerized device 203, and receive a third amount of conversion token 206. It should be noted that each conversion and/or exchange between digital assets 301, 302, 303 may be accomplished with at least two computing nodes 221a, 221b, 221c, since each conversion request 205a, 205b, 205c requires two computing nodes 221a, 221b, 221c (one for each digital-asset-specific token).

[053] Data conversion facilitated with conversion token 206 may, in certain configurations, be carried out with at least one smart contract. In the context of the disclosure, the term “smart contract” means a computer protocol, or manifestations thereof, intended to facilitate, verify, validate, or enforce the negotiation or performance of a contract. Additionally, smart contracts facilitate the automatic self-execution or selfenforcement of contractual clauses. Moreover, smart contracts provide security superior to traditional contract law and reduce transaction costs associated with contracting. For example the smart contract facilitated using the systems and methods disclosed utilizes ‘ERC20’ compatible “Ethereum” blockchain network.

[054] Reference is made to Figs. 3B-3C illustrating an example of digital asset conversions between computerized devices 203, 204 with data conversion system 200. As illustrated, first computerized device 203 may send a first request 205a to computer network 210 for conversion of first digital-asset specific token 211a with second digitalasset specific token 211b (to be determined as a first conversion 301), and similarly the second computerized device 204 may send a second request 205 to computer network 210 for conversion of second digital-asset specific token 211b with first digital-asset specific token 211a (to be determined as a second conversion 302).

[055] In the first conversion 301, first computing node 201a associated with first conversion 301 may receive a first amount of first digital-asset specific token 211a from first computerized device 203 via a registered transaction in first blockchain network 221a and in exchange send a first amount of conversion token 206 to first computerized device 203. Similarly, in second conversion 302, second computing node 201b associated with second conversion 302 may receive a second amount of second digital-asset specific token 211b from second computerized device 204 via a registered transaction in second blockchain network 221b and in exchange send a second amount of conversion token 206 to second computerized device 204. Sending the amount of digital-asset-specific tokens may correspond to automatic registration on the ledger of an associated blockchain network that this amount of digital-asset-specific tokens is exchanged between two parties, such that the target of the exchange owns the digital- as set- specific tokens at the end of the exchange.

[056] It should be noted that at this stage, first and second computerized devices 203, 204 are holding conversion token 206, while first and second computing nodes 201a, 201b are holding (e.g., registered as owners of digital-asset- specific tokens on a ledger of an associated blockchain network) the first and second data token type 211a, 211b respectively. For example a transaction may be registered in a blockchain network assigning a particular amount of data token type to the corresponding computing node. [057] At the final stage of the transaction, the first amount of conversion token 206 may be transferred from first computerized device 203 to second computing node 201b in exchange of the second amount of second digital-asset specific token 211b. Similarly, the second amount of conversion token 206 may be transferred from second computerized device 204 to first computing node 201a in exchange of the first amount of first digital-asset specific token 211a such that the final transaction of digital-asset- specific token(s) 211a, 211b may also be registered on the corresponding blockchain network 221a, 221b. Transactions of conversion token 206 are thereby registered on a ledger of a blockchain network associated with computer network 210.

[058] It should be noted that at the end of the transactions, each computerized device 203, 204 receives the desired type of digital- as set- specific token(s) 211a, 211b in a trustless (e.g., without a single party guaranteeing successful exchange) and anonymous manner wherein each party is unaware of the number of other parties and number of the computing nodes that carried out the data conversion and/or exchange. Thus, decentralized computer network 210 of system 200 enables decentralized validation of exchanges of digital assets, whereby each computerized device 203, 204 only sent a conversion request and decentralized computer network 210 automatically maintained, executed and validated the execution of the exchange via the computing nodes. Additionally, each computing node 201a, 201b are each dedicated to only a single digitalas set- specific token(s) 211a, 211b as well as conversion token 206.

[059] In an exemplary implementation, a single computing node may be registered with several blockchain networks 221a, 221b and multiple types of digital- as set- specific tokens.

[060] In one exemplary implementation, a first user of first computerized device 203 uses a dedicated software algorithm (e.g., an electronic (cryptocurrency) wallet) associated with computer network 210 to send a first conversion request for conversion from six “Bitcoin” tokens 211a owned by the first user (e.g., registered on a “Bitcoin” blockchain 221a) to a different type of token, e.g., “Ripple” tokens 211b. A second user of second computerized device 204 may use the dedicated software algorithm associated with computer network 210 to send a second conversion request for conversion from twenty “Ripple” tokens 211b owned by the second user to “Bitcoin” tokens 211a.

[061] Computer network 210 may receive conversion requests and determine a match between the first and second conversion requests, with a corresponding exchange rate of 1:3 between “Bitcoin” and “Ripple” tokens (e.g., calculated for a predetermined time period with an aggregated average of exchange rates). A first computing node 201a may be assigned for conversion of “Bitcoin” tokens 211a and automatically communicate with the “Bitcoin” blockchain 221a (e.g., via network connection 20) to register an exchange of six “Bitcoin” tokens 211a from an address associated with the first user to an address associated with the first computing node 201a. Similarly, a second computing node 201b may be assigned for conversion of “Ripple” tokens 211b and automatically communicate with the “Ripple” blockchain 221b to register an exchange of eighteen “Ripple” tokens 211b from an address associated with the second user to an address associated with the second computing node 201b, such that the second user keeps two “Ripple” tokens 21 lb in accordance with the calculated exchange rate. [062] In exchange of the “Bitcoin” 211a and “Ripple” 211b tokens, the first and second users may receive conversion token 206. For example the first and second users may receive three and nine conversion token 206 respectively in accordance with a conversion token exchange rate, and the exchange registered on a blockchain network associated with computer network 210.

[063] At the final stage, the first computing node 201a may register on the “Bitcoin” blockchain 221a an exchange of six “Bitcoin” tokens 21 la to the address associated with the second computerized device 204, while nine conversion token 206 may be exchanged from the second computerized device 204 to the first computing node 201a. Similarly, the second computing node 201b may register on the “Ripple” blockchain 221b an exchange of eighteen “Ripple” tokens 211b to the address associated with the first computerized device 203, while three conversion token 206 may be exchanged from the first computerized device 203 to the second computing node 201b. Thus, at the end of the exchange each user may receive the desire token without knowing and/or trusting other parties involved with the exchange, wherein tokens of different data formats were exchanged (or converted).

[064] Reference is made to Fig. 4 which shows a flowchart for a method of data conversion in a computer network. At least one processor (e.g., in a computing node) of computer network 210 may receive 401 a plurality of requests 205 for conversion between tokens 211a, 211b, 211c with different digital assets. In some exemplary implementations, the at least one processor may determine 402 a first request 205a corresponding to a first conversion 301 from a first digital-asset specific token 211a, to a second digital-asset specific token 211b, and a second request 205b corresponding to a second conversion 302 from the second digital-asset specific token 211b to the first digital-asset specific token 211a (in other words, pair the traders), the first and second conversions 301, 302 being opposite to each other.

[065] In some exemplary implementations, the at least one processor may receive 403 a first amount of the first digital-asset specific token 211a from first computerized device 203 associated with computer network 210, and convert and/or exchange 404 the first amount of first digital-asset specific token 211a with a first amount of conversion token 206. Likewise, the at least one processor may receive 405 a second amount of second digital-asset specific token 211b from second computerized device 204 associated with computer network 210, and convert and/or exchange 406 the second amount of second digital-asset specific token 211b with a second amount of the conversion token 206.

[066] The systems, methods and programs disclosed herein allow in certain implementations the conversion and/or exchange between digital-asset-specific tokens or between digital assets having different data formats.

[067] Unless explicitly stated, the exemplary implementations of the methods described herein are not constrained to a particular order in time or chronological sequence. Additionally, some of the described method elements may be skipped, or they may be repeated, during a sequence of operations of a method.

[068] Various exemplary implementations have been presented. Each of these exemplary implementations may of course comprise features from other exemplary implementations presented, and exemplary implementations not specifically described may comprise various features described herein.

[069] In the context of the disclosure, the term ‘module’, means, but is not limited to, a software or hardware component, such as a Field Programmable Gate- Array (FPGA) or Application-Specific Integrated Circuit (ASIC), which performs certain tasks. A module may advantageously be configured to reside on the addressable storage medium and configured to execute on one or more processors. Thus, a module may include, by way of example, components, such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. The functionality provided for in the components and modules may be combined into fewer components and modules or further separated into additional components and modules.

[070] Furthermore, in the context of the disclosure, the term ‘operable’ means the system and/or the device and/or the program, or a certain element or step is fully functional, sized, adapted and calibrated, comprises elements for, and meets applicable operability requirements to perform a recited function when activated, coupled, implemented, actuated, effected, realized, or when an executable program is executed by at least one processor associated with the system and/or the device. In relation to systems and circuits, the term "operable" means the system and/or the circuit is fully functional and calibrated, comprises logic for, having the hardware and firmware necessary, as well as the circuitry for, and meets applicable operability requirements to perform a recited function when executed by at least one processor.

[071] Accordingly and in an exemplary implementation, provided herein is an article of manufacture comprising a non-transitory memory storage device storing thereon a computer readable medium (CRM) for converting digital assets on a computer network having a plurality of nodes, the CRM comprising a set of executable instructions configured to, when executed by at least one processor, cause the at least one processor to perform the steps of: receiving a plurality of requests for conversion between digital assets; matching at least on pair of digital assets sought to be exchanged; assigning, a first node of the computer network for: receiving at least a portion of the first digital asset of the pair of digital assets sought to be converted from a first computerized device associated with the computer network; and exchanging the at least portion of the first digital asset of the pair of digital assets sought to be converted, with a first amount of a conversion token; and assigning a second node of the computer network for: receiving at least a portion of a second digital asset of the pair of digital assets sought to be converted from a second computerized device associated with the computer network; and exchanging the at least portion of the second digital asset of the pair of digital assets sought to be converted with a second amount of the conversion token data type, wherein the conversion token is associated with the computer network, and wherein the amount of conversion token associated with each of the first and second digital assets corresponds to an exchange rate between each digital asset, wherein (i) each digital asset in the pair of digital assets sought to be converted is associated with a digital-asset- specific token and wherein the amount of conversion token exchanged corresponds to an exchange rate between each digital-asset-specific token and the conversion token data type, wherein (ii) the set of executable instructions is further configured to, when executed by at least one processor, cause the at least one processor to perform the steps of: transferring, by the first node, the first amount of first digital-asset-specific token to the second computerized device associated with the computer network; receiving, by the first node, the second amount of the conversion token; transferring, by the second node, the second amount of the second digital-asset-specific token to the first computerized device associated with the computer network; and receiving, by the second node, the first amount of the conversion token, wherein (iii) the computer network is associated with a decentralized blockchain network, and wherein all operations of the computer network are carried out automatically (in other words, without user input), wherein (iv) each conversion from a digital-asset-specific token to a conversion token data type is registered on a separate blockchain network (interchangeable with distributed ledger systems (DLS), consensus networks), wherein (v) the set of executable instructions is further configured to, when executed by at least one processor, cause the at least one processor to perform the steps of determining the exchange rate from each digital-asset-specific token to the conversion token, wherein (vi) the exchange rate is time-limited, wherein (vii) at least one operation of the computer network is carried out utilizing the processing power of at least one computerized device associated with the computer network (in other words, one of the edge nodes’ processors, rather than a backend management server processor, the backend management server associated with one or both distributed computer networks), and wherein (viii) each node of the computer network is assigned to perform conversions for the digital-asset- specific token.

[072] In another exemplary implementation, provided herein is a computerized system for converting digital assets, the system comprising: a computer network with a plurality of nodes, whereby each computing node comprises at least one processor and is assigned to perform digital asset conversion for a digital- as set- specific token; and a plurality of data receivers, operable to receive requests from a plurality of computerized devices, each computerized device associated with the computer network, wherein the system further comprises a distributed processing module (DPM) having at least one processor, the DPM being in communication with each node on the computer network, and with a non-volatile memory storage device storing thereon a processor-readable medium with a set of executable instructions, configured, when executed to cause at least one of the at least one node processor, and the at least one DPM processor to: receive a plurality of requests for conversion between digital- as set- specific tokens; match at least on pair of digital assets sought to be exchanged; assign a first node of the computer network to: receive at least a portion of the first digital asset of the pair of digital assets sought to be converted from a first computerized device associated with the computer network; and exchange the at least portion of the first digital asset of the pair of digital assets sought to be converted, with a first amount of a conversion token; and assign a second node of the computer network to: receive at least a portion of a second digital asset of the pair of digital assets sought to be converted from a second computerized device associated with the computer network; and exchange the at least portion of the second digital asset of the pair of digital assets sought to be converted with a second amount of the conversion token data type, wherein the conversion token is associated with the computer network, and wherein the amount of conversion token associated with each of the first and second digital assets corresponds to an exchange rate between each digital asset, wherein (ix) the amount of conversion token exchanged corresponds to an exchange rate between each digital-asset-specific token and the conversion token, wherein (x) the set of executable instructions, is further configured, when executed to cause the at least one processor associated with the first node to: transfer the first amount of first digital-asset-specific token to the second computerized device associated with the computer network; and receive the second amount of the conversion token, wherein (xi) the set of executable instructions, is further configured, when executed to cause the at least one processor associated with the second node to: transfer the second amount of second digital-asset- specific token to the first computerized device associated with the computer network; and receive the first amount of the conversion token, wherein (xii) each computing node of the computer network is associated with a single blockchain, and wherein each conversion from a digital-asset-specific token to a conversion token is registered on a separate blockchain network (such that for example, a single transaction can be registered in the distributed ledgers of two different blockchains), wherein (xiii) at least one node of the computer network is operable to determine an exchange rate from each digitalas set- specific token to the conversion token, (xiv) the exchange rate being time-limited, wherein (xv) at least one operation of the computer network is carried out utilizing the processing power of computerized devices associated with the computer network, and wherein (xvi) the computer network is associated with a decentralized blockchain network, and wherein all operations of the computer network are carried out automatically. [073] Although the foregoing disclosure has been described in terms of some exemplary implementations, other exemplary implementations will be apparent to those of ordinary skill in the art from the disclosure herein. Moreover, the described exemplary implementations have been presented by way of technical example only, and are not intended to limit the scope of the disclosure. Indeed, the novel methods, programs, computer-readable media and systems described herein may be exemplified in a variety of other forms without departing from the spirit thereof. Accordingly, other combinations, omissions, substitutions and modifications will be apparent to the skilled artisan in view of the disclosure herein.

Claims

WHAT IS CLAIMED:

1. An article of manufacture comprising a non-transitory memory storage device storing thereon a computer readable medium (CRM) for converting digital assets on a computer network having a plurality of nodes, the CRM comprising a set of executable instructions configured to, when executed by at least one processor, cause the at least one processor to perform the steps of: receiving a plurality of requests for conversion between digital assets; matching at least on pair of digital assets sought to be exchanged; assigning, a first node of the computer network for: receiving at least a portion of the first digital asset of the pair of digital assets sought to be converted from a first computerized device associated with the computer network; and exchanging the at least portion of the first digital asset of the pair of digital assets sought to be converted, with a first amount of a conversion token; and assigning a second node of the computer network for: receiving at least a portion of a second digital asset of the pair of digital assets sought to be converted from a second computerized device associated with the computer network; and exchanging the at least portion of the second digital asset of the pair of digital assets sought to be converted with a second amount of the conversion token data type, wherein the conversion token is associated with the computer network, and wherein the amount of conversion token associated with each of the first and second digital assets corresponds to an exchange rate between each digital asset.

2. The CRM of claim 1, wherein each digital asset in the pair of digital assets sought to be converted is associated with a digital-asset- specific token and wherein the amount of conversion token exchanged corresponds to an exchange rate between each digitalas set- specific token and the conversion token data type.

3. The CRM of claim 2, wherein the set of executable instructions is further configured to, when executed by at least one processor, cause the at least one processor to perform the steps of:

26 transferring, by the first node, the first amount of first digital-asset- specific token to the second computerized device associated with the computer network; receiving, by the first node, the second amount of the conversion token; transferring, by the second node, the second amount of the second digital-asset- specific token to the first computerized device associated with the computer network; and receiving, by the second node, the first amount of the conversion token.

4. The CRM of claim 1, wherein the computer network is associated with a decentralized blockchain network, and wherein all operations of the computer network are carried out automatically.

5. The CRM of claim 3, wherein each conversion from a digital-asset- specific token to a conversion token data type is registered on a separate blockchain network.

6. The CRM of claim 1, wherein the set of executable instructions is further configured to, when executed by at least one processor, cause the at least one processor to perform the steps of determining the exchange rate from each digital-asset-specific token to the conversion token.

7. The CRM of claim 5, wherein the exchange rate is time-limited.

8. The CRM of claim 1, wherein at least one operation of the computer network is carried out utilizing the processing power of computerized devices associated with the computer network.

9. The CRM of claim 1, wherein each node of the computer network is assigned to perform conversions for the digital-asset-specific token.

10. A computerized system for converting digital assets, the system comprising: a computer network with a plurality of nodes, whereby each computing node comprises at least one processor and is assigned to perform digital asset conversion for a digital-asset-specific token; and a plurality of data receivers, operable to receive requests from a plurality of computerized devices, each computerized device associated with the computer network, wherein the system further comprises a distributed processing module (DPM) having at least one processor, the DPM being in communication with each node on the computer network, and with a non-volatile memory storage device storing thereon a processor-readable medium with a set of executable instructions, configured, when executed to cause at least one of the at least one node processor, and the at least one DPM processor to: receive a plurality of requests for conversion between digital-asset-specific tokens; match at least on pair of digital assets sought to be exchanged; assign a first node of the computer network to: receive at least a portion of the first digital asset of the pair of digital assets sought to be converted from a first computerized device associated with the computer network; and exchange the at least portion of the first digital asset of the pair of digital assets sought to be converted, with a first amount of a conversion token; and assign a second node of the computer network to: receive at least a portion of a second digital asset of the pair of digital assets sought to be converted from a second computerized device associated with the computer network; and exchange the at least portion of the second digital asset of the pair of digital assets sought to be converted with a second amount of the conversion token data type, wherein the conversion token is associated with the computer network, and wherein the amount of conversion token associated with each of the first and second digital assets corresponds to an exchange rate between each digital asset.

11. The system of claim 10, wherein the amount of conversion token exchanged corresponds to an exchange rate between each digital-asset-specific token and the conversion token.

12. The system of claim 11, wherein the set of executable instructions, is further configured, when executed to cause the at least one processor associated with the first node to: transfer the first amount of first digital-asset- specific token to the second computerized device associated with the computer network; and receive the second amount of the conversion token.

13. The system of claim 11, wherein the set of executable instructions, is further configured, when executed to cause the at least one processor associated with the second node to: transfer the second amount of second digital-asset- specific token to the first computerized device associated with the computer network; and receive the first amount of the conversion token.

14. The system of claim 10, wherein each computing node of the computer network is associated with a single blockchain, and wherein each conversion from a digital-asset- specific token to a conversion token is registered on a separate blockchain network.

15. The system of claim 10, wherein at least one node of the computer network is operable to determine an exchange rate from each digital-asset-specific token to the conversion token.

16. The system of claim 14, wherein the exchange rate is time-limited.

17. The system of claim 10, wherein at least one operation of the computer network is carried out utilizing the processing power of at least one computerized device associated with the computer network.

18. The system of claim 10, wherein the computer network is associated with a decentralized blockchain network, and wherein all operations of the computer network are carried out automatically.

29