A computer network system for performing cryptographically protected token-based alternative management, and a method of using the system

Abstract

To provide a database-centered computer network system and a computer execution method for cryptographically protected distributed data management.SOLUTION: A distributed blockchain environment includes: a plurality of externally-owned presence (EOP) member nodes associated with a plurality of distributed entities; a cryptographically protected distributed ledger; a plurality of electronic wallets for holding data records of a distributed ledger collateral (DLC) token; and a plurality of self-contained type self-executing software containers (SESCs) including a first type SESC, a second type SESC, and a third type SESC. The DLC is utilized by a distributed blockchain environment. The first type SESC, the second type SESC, and the third type SESC are a distributed SESC. The DLC token includes at least one unique entity identification cryptographic hash.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] (Cross - Reference to Related Applications) This disclosure is a patent application claiming priority to U.S. Provisional Patent Application No. 62 / 668,144, entitled "CRYPTOGRAPHICALLY - SECURED, TOKEN - BASED DATA LIFECYCLE MANAGEMENT AND COMPUTER NETWORK SYSTEMS AND COMPUTER - IMPLEMENTED METHODS THEREOF", filed on May 7, 2018, the entire disclosure of which is incorporated herein by reference for all purposes.

[0002] Here, the present invention generally relates to a database - centric computer network system and a computer - implemented method for cryptographically - protected distributed data management.

Background Art

[0003] A computer network may include a group of computer systems and other computer hardware interconnected via communication channels to facilitate communication and resource sharing across a wide range of users.

Summary of the Invention

[0004] In some embodiments, and in any combination with the foregoing or following embodiments, at least some embodiments of the present disclosure provide an exemplary system including at least a distributed blockchain environment. The distributed blockchain environment includes (i) a plurality of externally - owned presence (EOP) member nodes associated with a plurality of distributed entities, each including one or more computers associated with at least one distributed entity, and (ii) one or more cryptographically - protected distributed ledgers storing a plurality of persistent data objects across one or more computers of the EOP member nodes. (iii) A plurality of electronic wallets (e-wallets) configured to hold data records of one or more decentralized ledger collateral (DLC) tokens, wherein a computer of an EOP member node is configured to manage a corresponding one or more of the plurality of electronic wallets, the plurality of electronic wallets, and (iv) A plurality of self - contained autonomous execution software containers (SESCs), and (1) One or more first - type SESCs, each first - type SESC comprising (a) Generating a plurality of persistent SESC data objects, the persistent SESC data objects storing distributed data items of at least one transaction among a plurality of entities in one or more cryptographically protected decentralized ledgers, the at least one transaction including one or more assets, and (b) Updating distributed data items of at least one transaction in one or more corresponding persistent SESC data objects The one or more first - type SESCs including a plurality of persistent software routines configured as such, and (2) One or more second - type SESCs, each of the one or more second - type SESCs including one or more persistent task - specific software routines, the persistent task - specific software routines being called by one or more persistent software routines of the first - type SESCs and updating one or more corresponding distributed data items of at least one transaction based on each corresponding task executed by one or more persistent software routines of the first - type SESCs having one or more corresponding distributed data items, the one or more second - type SESCs configured as such, and (3) One or more SESC of a third type, each of the one or more SESC of the third type includes one or more persistent token-specific software routines, and the persistent token-specific software routines are configured to manage DLC tokens in a distributed blockchain environment, and the DLC tokens are used by the distributed blockchain environment to substitute one or more first assets of at least one first party in at least one transaction for one or more second assets of at least one second party in at least one transaction, one or more SESC of the third type; A plurality of SESC including; One or more SESC of the first type, one or more SESC of the second type, and one or more SESC of the third type are distributed SESC, Each DLC token includes at least one unique entity identification cryptographic hash, For each corresponding transaction associated with the corresponding EOP member node, one or more computers of the corresponding EOP member node are configured to call (i) one or more SESC of the first type and (ii) one or more SESC of the third type to cryptographically manage each corresponding transaction in a distributed blockchain environment.

[0005] In some embodiments, and in any combination with the embodiments described above or below, at least some embodiments of the present disclosure provide exemplary methods. The exemplary method is, Managing, by one or more computers, a plurality of externally-owned presence (EOP) member nodes associated with a plurality of distributed entities; Managing, by one or more computers, one or more cryptographically protected distributed ledgers and storing a plurality of persistent data objects across a distributed blockchain environment of the EOP member nodes; Managing, by one or more computers, a plurality of electronic wallets (e-wallets) configured to hold data records of one or more distributed ledger collateral (DLC) tokens Managing, by one or more computers, a plurality of self - contained self - executing software containers (SESCs), where the plurality of SESC (1) One or more SESCs of a first type, where each SESC of the first type (a) Generates a plurality of persistent SESC data objects, where the persistent SESC data objects store distributed data items of at least one transaction among a plurality of entities in one or more cryptographically protected distributed ledgers, and where at least one transaction includes one or more assets (b) Updates distributed data items of at least one transaction in one or more corresponding persistent SESC data objects One or more SESCs of the first type, including a plurality of persistent software routines configured as such (2) One or more SESCs of a second type, where each of the one or more SESCs of the second type includes one or more persistent task - specific software routines, and where the persistent task - specific software routines are called by one or more persistent software routines of the first - type SESCs and are configured to update one or more corresponding distributed data items of at least one transaction based on each corresponding task executed by one or more persistent software routines of the first - type SESCs having one or more corresponding distributed data items. One or more SESCs of the second type (3) One or more SESC of a third type, each of the one or more SESC of the third type includes one or more persistent token-specific software routines, and the persistent token-specific software routines are configured to manage DLC tokens in a distributed blockchain environment, and the DLC tokens are used by the distributed blockchain environment to substitute one or more first assets of at least one first party in at least one transaction for one or more second assets of at least one second party in at least one transaction, one or more SESC of the third type, including managing a plurality of SESC, managing corresponding transactions in a distributed blockchain environment by one or more computers according to one or more SESC of a first type and one or more SESC of a third type called by a corresponding EOP member node. One or more SESC of a first type, one or more SESC of a second type, and one or more SESC of a third type are distributed SESC, Each DLC token includes at least one unique entity identification cryptographic hash.

[0006] In some embodiments, and in any combination with the foregoing or following embodiments, one or more SESC of the third type are (i) generating corresponding amounts of DLC tokens associated with one or more first assets and one or more second assets respectively, (ii) configured to store the corresponding amounts of DLC tokens in corresponding digital wallets of at least one first party and at least one second party.

[0007] In some embodiments, and also in any combination with the embodiments described above or below, for at least one transaction, a plurality of persistent software routines of one or more first-type SESCs call one or more third-type SESCs and are configured to lock at least a portion of each corresponding amount of DLC tokens in a corresponding digital wallet to form corresponding locked DLC tokens.

[0008] In some embodiments, and also in any combination with the embodiments described above or below, a plurality of persistent software routines of one or more first-type SESCs (i) call one or more third-type SESCs to substitute one or more first assets of at least one first party in at least one transaction for one or more second assets of at least one second party in at least one transaction, transfer corresponding locked DLC tokens between corresponding digital wallets, (ii) cryptographically record the substitution in one or more persistent SESC data objects associated with at least one transaction and are so configured.

[0009] In some embodiments, and also in any combination with the embodiments described above or below, at least one transaction is an asset buyback transaction.

[0010] In some embodiments, and also in any combination with the embodiments described above or below, one or more first assets of at least one first party and one or more second assets of at least one second party are collateral assets in an asset buyback transaction.

[0011] In some embodiments, and also in any combination with the embodiments described above or below, one or more first assets of at least one first party, and one or more second assets of at least one second party, are assets of a distributed type.

[0012] In some embodiments, and also in any combination with the embodiments described above or below, one or more first assets of at least one first party, and one or more second assets of at least one second party, are stored in corresponding hold-in-custody accounts of corresponding EOP member nodes.

[0013] In some embodiments, and also in any combination with the embodiments described above or below, corresponding digital wallets of at least one first party and at least one second party include corresponding hold-in-custody accounts.

[0014] In some embodiments, and also in any combination with the embodiments described above or below, one or more SESC of a third type are (i) configured to generate corresponding amounts of DLC tokens associated with one or more first assets and one or more second assets respectively, (ii) configured to store the corresponding amounts of DLC tokens in corresponding digital wallets of at least one first party and at least one second party.

[0015] In some embodiments, and also in any combination with the embodiments described above or below, a first digital wallet of at least one first party, a second digital wallet of at least one second party, or the first digital wallet and the second digital wallet store one or more corresponding amounts of DLC tokens received in at least one other transaction with at least one third party.

[0016] In some embodiments, and in any combination with the embodiments described above or below, when at least one other transaction occurs between at least one first party and at least one second party, at least one third party is one of at least one first party or at least one second party.

[0017] The present disclosure can be further described with reference to the accompanying drawings, and throughout several of the figures, like reference numerals refer to like structures. The figures shown are not necessarily to scale; rather, emphasis has generally been placed on illustrating the principles of the present disclosure. Accordingly, specific structural and functional details disclosed herein should not be construed as limiting, but merely as representative of various ways of using the invention to teach those skilled in the art.

Brief Description of the Drawings

[0018]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Best Mode for Carrying Out the Invention

[0019] In the disclosed advantages and improvements, other objects and advantages of the present disclosure may become apparent from the following description taken in conjunction with the accompanying drawings. Although detailed embodiments of the present disclosure are disclosed herein, it should be understood that the disclosed embodiments are merely exemplary of the present disclosure that may be embodied in various forms. Also, each example presented in connection with the various embodiments of the present disclosure is intended to be illustrative and not limiting.

[0020] Throughout this specification, the following terms take the meanings explicitly associated with this specification unless the context clearly indicates otherwise. As used herein, the phrases "in one embodiment" and "in some embodiments" do not necessarily refer to the same embodiment(s), although they may. Also, the phrases "in another embodiment" and "in some other embodiments" do not necessarily refer to different embodiments, although they may. Thus, as described below, various embodiments of the present disclosure can be readily combined without departing from the scope or spirit of the present disclosure.

[0021] Also, the term "based on" is not exclusive and, unless the context clearly indicates otherwise, may be based on additional elements not recited. In addition, throughout this specification, the articles "a," "an," and "the" include plural references in their meaning. "In" includes in and on in its meaning.

[0022] It is understood that at least one aspect or function in various embodiments described herein can be executed in real time and / or dynamically. As used herein, the term "real time" refers to an event or action that can occur instantaneously or nearly instantaneously when another event or action occurs. For example, "real-time processing," "real-time calculation," and "real-time execution" are all related to performing a calculation in real time as a related physical process (e.g., interaction of a user with an application on a mobile device) occurs, such that the result of the calculation can be used in the derivation of the physical process.

[0023] As used herein, the term "runtime" corresponds to any behavior that is determined dynamically during the execution of a software application or at least a portion of a software application.

[0024] As used herein, the term "dynamic(ally)" means that events and / or actions can be initiated and / or caused without human intervention. In some examples, and also in any combination with the examples described above or below, the occurrence of events and / or actions according to the present disclosure can be based on at least one of real time and / or a predetermined periodicity indicated by nanoseconds, a few nanoseconds, milliseconds, a few milliseconds, one second, a few seconds, one minute, a few minutes, one hour, a few hours, one day, a few days, one week, one month, etc.

[0025] In some embodiments, and in any combination with the embodiments described above or below, the electronic system of the present invention is associated with electronic mobile devices (e.g., smartphones, etc.) owned by users and servers (if any) within a distributed network environment, which communicate via a suitable data communication network (e.g., the Internet, etc.) and utilize at least one suitable data communication protocol (e.g., IPX / SPX, X.25, AX.25, AppleTalk®, TCP / IP (e.g., HTTP), etc.). In some embodiments, and in any combination with the embodiments described above or below, the number of concurrent users can be at least 100 (e.g., 100 to 999, etc.), at least 1,000 (e.g., 1,000 to 9,999, etc.), at least 10,000 (e.g., 10,000 to 99,999, etc.), at least 100,000 (e.g., 100,000 to 999,999, etc.), at least 1,000,000 (e.g., 1,000,000 to 9,999,999, etc.), at least 10,000,000 (e.g., 10,000,000 to 99,999,999, etc.), at least 100,000,000 (e.g., 100,000,000 to 999,999,999, etc.), at least 1,000,000,000 (e.g., 1,000,000,000 to 10,000,000,000, etc.), but is not limited thereto.

[0026] In some embodiments, and in any combination with the foregoing or following embodiments, the specially programmed computer system of the present invention, which includes associated devices, operates in a distributed network environment, communicates via a suitable data communication network (e.g., the Internet, etc.), and is configured to use at least one suitable data communication protocol (e.g., IPX / SPX, X.25, AX.25, AppleTalk®, TCP / IP (e.g., HTTP), etc.). It goes without saying that the embodiments described herein may be implemented using any suitable hardware and / or computer software language. In this regard, those skilled in the art are proficient in the types of computer hardware that can be used, the types of computer programming techniques that can be used (e.g., object-oriented programming), and the types of computer programming languages that can be used (e.g., Go, C++, Objective-C, Swift, Java®, Javascript®, Python, Perl, etc.). The above examples are, of course, illustrative and not limiting.

[0027] The components disclosed herein may be implemented in software or firmware or a combination thereof, or as instructions stored in a machine-readable medium that can be read and executed by one or more processors. A machine-readable medium may include any medium and / or mechanism that stores or transmits information in a form readable by a machine (e.g., a computer device). Examples of machine-readable media include, for example, read-only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media, flash memory devices, electrical propagation signals, optical propagation signals, acoustic propagation signals, or other forms of propagation signals (e.g., carrier waves, infrared signals, digital signals, etc.).

[0028] In another form, a non-transitory product such as a non-transitory computer-readable medium may be used with any of the above examples, or other examples except that it does not include the transient signal itself. This actually includes elements other than the signal itself that can temporarily hold data in a "transient" form such as RAM.

[0029] As used herein, the terms "computer engine" and "engine" refer to at least one software component and / or a combination of at least one software component and at least one hardware component that is designed or programmed to manage or control other software components and / or hardware components (libraries, software development kits (SDKs), objects, etc.).

[0030] Examples of hardware elements include processors, microprocessors, circuits, circuit elements (e.g., transistors, registers, capacitors, inductors, etc.), integrated circuits, application-specific integrated circuits (ASICs), programmable logic devices (PLDs), digital signal processors (DSPs), field-programmable gate arrays (FPGAs), logic gates, registers, semiconductor elements, chips, microchips, and chip sets, etc. In some embodiments, and also in any combination with the embodiments described above or below, the one or more processors may be implemented as a complex instruction set computer (CISC) processor or a reduced instruction set computer (RISC) processor, an x86 instruction set compatible processor, multi-core, or any other microprocessor or central processing unit (CPU). In various implementations, the one or more processors may be a dual-core processor (plural available), a dual-core mobile processor (plural available), etc.

[0031] Examples of software include software components, programs, applications, computer programs, application programs, system programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (APIs), instruction sets, computing code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof. The determination of whether to implement an embodiment using hardware elements and / or software elements may vary depending on any number of factors such as the desired computing speed, power level, heat tolerance, processing cycle budget, input data rate, output data rate, memory resources, data bus speed, and other design or performance constraints.

[0032] In one implementation, the multiprocessor system may include a plurality of processor chips, each including at least one I / O component designed to be directly connected to a photonic component for connecting to at least one I / O device. In some embodiments, and in any combination with the embodiments described above or below, the I / O device may be a standard interface such as a peripheral component interconnect express (PCIe), universal serial bus (USB), Ethernet, Infiniband, etc. In some embodiments, and in any combination with the embodiments described above or below, the I / O device may include a storage device.

[0033] In one implementation, the multiprocessor system may include a plurality of photonic components and an external memory. The external memory may be shared by two or more of the processor chips. The external memory may be directly connected to a single processor chip and shared with other processor chips using a global memory architecture implemented using an inter-processor approach. The multiprocessor system may further include a plurality of processor chips, each including one cache and at least one I / O component designed to be directly connected to the photonic component to communicate with one or more other processor chips. At least one I / O component in the at least one processor chip may be configured to use a directory-based cache coherence protocol. In some embodiments, also, in any combination with the embodiments described above or below, the cache in at least one of the processor chips may be configured to store directory information. In some embodiments, also, in any combination with the embodiments described above or below, the external memory may include DRAM. In some embodiments, also, in any combination with the embodiments described above or below, the directory information may be stored in the external memory and in the on-chip cache in at least one of the processor chips. In some embodiments, also, in any combination with the embodiments described above or below, the multiprocessor system may further include a directory subsystem configured to split the external memory data and the directory information onto two different external memories. In some embodiments, also, in any combination with the embodiments described above or below, the multiprocessor system may further include a directory subsystem that is part of a subsystem implemented on a high-performance chip that is part of a three-dimensional DRAM memory stack.In some embodiments, and in any combination with the embodiments described above or below, the multiprocessor system may further include a directory subsystem configured to support a variable number of sharers per memory block. In some embodiments, and in any combination with the embodiments described above or below, the multiprocessor system may further include a directory subsystem configured to support a variable number of sharers per memory block using caching. In some embodiments, and in any combination with the embodiments described above or below, the multiprocessor system may further include a directory subsystem configured to support a variable number of sharers per memory block using hashing of storage entries with different numbers of pointers to sharers. In some embodiments, and in any combination with the embodiments described above or below, the multiprocessor system may further include a directory subsystem configured to use hashing to reduce storage allocated to memory blocks with no sharers.

[0034] One or more aspects of at least one embodiment may be implemented by representative instructions stored on a machine-readable medium that, when read by a processor to represent various logic within the processor, cause the machine to create logic to perform the techniques described herein. Such representation elements, known as "IP cores," may be stored on a tangible machine-readable medium and loaded into a manufacturing machine that actually creates the logic or processor and supplied to various customers or manufacturing facilities.

[0035] In some embodiments, and in any combination with the embodiments described above or below, the present disclosure provides an exemplary cryptographically protected distributed ledger (blockchain) of the present invention, the cryptographically protected distributed ledger being configured as a single source having a cryptographically secure, authentic and immutable record for a network of a plurality of nodes. In some embodiments, and in any combination with the embodiments described above or below, the cryptographically protected distributed ledger of the present invention may be at least partially based on the Ethereum blockchain (Ethereum Foundation in Zug, Switzerland). In some embodiments, and in any combination with the embodiments described above or below, the cryptographically protected distributed ledger of the present invention may be at least partially based on Hyperledger technologies such as Hyperledger Fabric (Linux® Foundation in San Francisco, California). In some embodiments, and in any combination with the embodiments described above or below, the cryptographically protected distributed ledger of the present invention may be at least partially based on one or more methodologies described in Appendix A incorporated herein for any purpose.

[0036] In some embodiments, and in any combination with the embodiments described above or below, an exemplary cryptographically protected, database-centric computer system of the present invention is permission-based and is controlled by at least one administrative authority that may have read or write privileges and may request authentication of other members. In some embodiments, and in any combination with the embodiments described above or below, an exemplary, cryptographically protected, permissioned distributed database-centric computer system of the present invention may be implemented as a continuously changing membership among authenticated node members, referred to herein as externally owned presence nodes (EOP nodes). In some embodiments, and in any combination with the embodiments described above or below, an exemplary, cryptographically protected, distributed database-centric computer system of the present invention may have only administrative authorities as read or write nodes (i.e., administrative EOP member nodes), while other members or participants may have only read nodes (e.g., peer EOP member nodes), and / or may be programmed or configured to access the distributed ledger of the present invention via a dedicated graphical user interface (GUI), which may be, for example, an online web GUI and / or a mobile application GUI (e.g., via peer EOP member nodes of other members), but is not limited thereto. In some embodiments, and in any combination with the embodiments described above or below, an exemplary, cryptographically protected, distributed database-centric computer system of the present invention may use one or more digital signature cryptographic algorithms and may be programmed or configured such that members or participants can set trusted or authenticated EOP nodes, and the digital signature cryptographic algorithm may be, but is not limited to, an elliptic curve digital signature algorithm (ECDSA) based on a private key or public key pair.In some embodiments, and in any combination with the embodiments described above or below, the private key is stored only for the participants or members (peer EOP member nodes), and the administrative EOP member node cannot access the private key. For example, an exemplary cryptographically protected, permissioned distributed database-centric computer system of the present invention utilizes sharding to ensure that only data that non-admin members are authorized to view is viewable.

[0037] In some embodiments, and in any combination with the embodiments described above or below, the administrative authority facilitates the functions of the computer system by making it easier to create digital identification information for EOP-owned participants who can access an exemplary cryptographically protected, distributed database-centric computer system of the present invention via any suitable computer spot. The computer spot may be, for example, a mobile portal, an online portal or a web portal, and any other suitable similar interface(s), but is not limited thereto.

[0038] In some embodiments, and in any combination with the embodiments described above or below, an exemplary cryptographically protected, distributed database-centric computer system of the present invention can be programmed or configured to facilitate the setting up of self-contained, self-executing software containers (SESCs) that represent the state of specific data. Each SESC may include specific data and specific independent software code (ISC) that is executed on the specific data when specific transactions (e.g., data messages) are targeted at the specific SESC(s). In some embodiments, and in any combination with the embodiments described above or below, each SESC has a structure such as an Ethereum smart contract.

[0039] In some embodiments, and in any combination with the embodiments described above or below, an exemplary, cryptographically protected, distributed database-centric computer system of the present invention may be programmed or configured such that blockchain data existing in a distributed form across a plurality of nodes and / or only the reading of blockchain data existing in a storage device outside the blockchain is possible when an exemplary smart contract of the present invention is executed by the computer system. For example, a specific smart contract may verify the identification information of the caller and then obtain only the data for which the caller is authorized to receive, thereby ensuring the privacy and / or confidentiality of the data.

[0040] Exemplary use cases of SESC for the management of re-purchase agreements (also called REPO or repo) between n parties (e.g., between two parties)

[0041] Typically, a repurchase agreement is a form of short-term borrowing. For example, typically, a seller sells securities (plural) to a buyer (e.g., an investor) for a predetermined period (e.g., overnight) or an open time period, and at the end of the period or at a specific point in time during the open period, buys back the securities (plural) sold. For the side that agrees to sell the securities and buy them back in the future, it is a repurchase agreement. For the other side of this transaction, which agrees to buy the securities and sell them in the future, it is a reverse repurchase agreement (also called a reverse repo transaction). Typically, there are three types of repurchase agreements. (i) Third-party repurchase agreement (in this agreement, a clearing agent or a clearing bank holds the securities, ensuring that the seller receives cash at the start of the contract, the buyer transfers funds for the benefit of the seller, and delivers the securities at maturity, thereby conducting the transaction between the buyer and the seller and protecting their respective interests.) (ii) Specialized delivery REPO (This contract requires guaranteed bonds at the start and expiration of the contract.) (iii) Held-in-custody account REPO (HIC REPO) (In this contract, the seller receives cash for the sale of securities, but the cash is held in a custody account for the buyer. However, there is a risk that the seller may become insolvent and the borrower may not be able to access the collateral.)

[0042] In some embodiments, and in any combination with the embodiments described above or below, an exemplary, cryptographically protected, distributed database-centric computer system of the present invention may be (i) Financial commodity trading, (ii) Transaction settlement, (iii) Current holdings (i.e., current holdings in custody), (iv) Static price of securities, and (v) Trading accounts configured or programmed to obtain input data related to at least one of (e.g., via one or more dedicated APIs).

[0043] In some embodiments, and in any combination with the embodiments described above or below, an exemplary, cryptographically protected, distributed database-centric computer system of the present invention may be (i) Transaction settlement, (ii) Adjustment of holdings, transactions, and / or accounts, and (iii) Static price of securities configured or programmed to generate output data related to at least one of (e.g., via one or more dedicated APIs).

[0044] In some embodiments, and in any combination with the foregoing or following embodiments, an exemplary, cryptographically protected, distributed database-centric computer system of the present invention may be configured to ensure that there is only one copy of a transaction stored, for example, in a blockchain. In some embodiments, and in any combination with the foregoing or following embodiments, an exemplary, cryptographically protected, distributed database-centric computer system of the present invention may be configured to match transactions between parties (based on data input via corresponding nodes) and add or associate a unique identifier with each matched pair. For example, an exemplary, cryptographically protected, distributed database-centric computer system of the present invention may be programmed or configured to match transactions based on at least a portion of predetermined parameters and their order. For example, if a reference number is available, the reference number may be utilized as a first parameter and then matched by at least one of a party identifier, a product ID, a currency, a transaction quantity, a cash amount, a price, an exchange rate, and other similarly suitable parameters. For example, for a transaction in which only a portion is matched, an exemplary, cryptographically protected, distributed database-centric computer system of the present invention may be configured to subject the transaction to a repair mechanism or methodology and enter into a consensus process or a contract process. For example, transactions that cannot be matched, or transactions submitted by only one party, may be held individually and may not be stored in an exemplary blockchain of the present invention.

[0045] In some embodiments, and in any combination with the foregoing or following embodiments, an exemplary, cryptographically protected, distributed database-centric computer system of the present invention may be configured to be associated with an application or structure such as a digital wallet, and the application or structure may be programmed to store a running cash balance and provide it for cash transfers to a corresponding system (e.g., a system of member nodes) through a corresponding API interface.

[0046] In some embodiments, and in any combination with the foregoing or following embodiments, an exemplary, cryptographically protected, distributed database-centric computer system of the present invention may be configured to adjust the balance of a custody (HIC) account for corresponding custody API query results for corresponding account(s).

[0047] In some embodiments, and in any combination with the embodiments described above or below, an exemplary, cryptographically protected, distributed database-centric computer system of the present invention may be configured to tokenize assets in individual accounts. In some embodiments, and in any combination with the embodiments described above or below, an exemplary, cryptographically protected, distributed database-centric computer system of the present invention may be configured to allow a custodian (e.g., a third-party bank, etc.) to access or view its client's transactions, balances, and / or HIC account activities. In some embodiments, and in any combination with the embodiments described above or below, an exemplary, cryptographically protected, distributed database-centric computer system of the present invention may be configured to allow transfers to and from HIC accounts and transactions of asset tokens. In some embodiments, and in any combination with the embodiments described above or below, an exemplary, cryptographically protected, distributed database-centric computer system of the present invention may be configured to adjust the accounts in the chain to ensure the existence of assets against custodian balances.

[0048] In some embodiments, and in any combination with the foregoing or following embodiments, an exemplary, cryptographically protected, distributed database-centric computer system of the present invention may be configured to reduce the cost of transactions resulting from immobilization of collateral during and between transactions with trading partners. In some embodiments, and in any combination with the foregoing or following embodiments, an exemplary, cryptographically protected, distributed database-centric computer system of the present invention may be configured to reduce matching of failures by storing each transaction and all related approvals or data. In some embodiments, and in any combination with the foregoing or following embodiments, an exemplary, cryptographically protected, distributed database-centric computer system of the present invention may be configured to reduce the computer processing time required to record, track, and reconcile repurchase agreement transactions. For example, data management of repurchase agreement transactions via an exemplary blockchain-based methodology of the present disclosure is related to minimizing the memory resources that should be allocated by a computer to store and / or manage each repurchase agreement transaction.

[0049] In some embodiments, and in any combination with the foregoing or following embodiments, an exemplary, cryptographically protected, distributed database-centric computer system of the present invention (1) enable a party to agree to maintain custody as "in custody" or "segregated" at the current custody location (e.g., the borrower's electronic ledger or record) (HIC account(s)), (2) set the custody as a member node of the network, transfer the collateral via the blockchain, and (3) set up an account dedicated to repurchase agreements in the custody electronic system, may be configured to immobilize the collateral by executing one or more of the following commands.

[0050] FIG. 1 illustrates an example of a flowchart based on an exemplary, cryptographically protected, distributed database-centric computer system that may be configured based on one or more principles described herein. In some embodiments, and in any combination with the embodiments described above or below, the exemplary, cryptographically protected, distributed database-centric computer system of the present invention may be programmed as a distributed ledger platform having module components for identity information management, smart contracts, assurance, management state database, and distributed ledger (blockchain). In some embodiments, and in any combination with the embodiments described above or below, an exemplary network of nodes managed by the exemplary, cryptographically protected, distributed database-centric computer system of the present invention may include at least one assurance node, the assurance node being configured to validate transactions and assure these transactions for further processing. In some embodiments, and in any combination with the embodiments described above or below, an exemplary network of nodes managed by the exemplary, cryptographically protected, distributed database-centric computer system of the present invention may include at least one orderer node that orders transactions in the network to generate blocks. In some embodiments, and in any combination with the embodiments described above or below, an exemplary network of nodes managed by the exemplary, cryptographically protected, distributed database-centric computer system of the present invention may include at least one default Certificate Authority (CA) component or node, the default CA component or node issuing, for example, PKI-based authentication to network members and their users, but not limited thereto.In some embodiments, and in any combination with the embodiments described above or below, an exemplary network of the invention of nodes managed by an exemplary, cryptographically protected, distributed database-centric computer system may include software (e.g., Chaincode) operating in the distributed ledger of the invention, the software being configured to encrypt assets and transaction instructions for changing the assets. In some embodiments, and in any combination with the embodiments described above or below, an exemplary network of the invention of nodes managed by an exemplary, cryptographically protected, distributed database-centric computer system may include one or more channels that may be a private blockchain or a global blockchain that enables data separation and confidentiality. In some embodiments, and in any combination with the embodiments described above or below, an exemplary network of the invention of nodes managed by an exemplary, cryptographically protected, distributed database-centric computer system may include SESC, which is, for example, a function of a particularly modified chaincode and is configured to obtain a transaction proposal, and the transaction proposal subsequently passes through the flow of modules such as authentication, ordering, validation, execution, etc.

[0051] Figure 2 shows an illustration of an exemplary network topology of the invention having an exemplary, cryptographically protected, distributed database-centric computer system (201) of the invention, the computer system (201) managing a network of exemplary nodes (202 and 203) based on one or more principles described herein.

[0052] Figure 3 shows another illustration of an exemplary network topology of the present invention having an exemplary cryptographically protected, distributed database-centric computer system (201), the computer system having one or more channels, the channels being private blockchains or global blockchains managed using smart contracts (SESC1-6) based on one or more principles described in this disclosure. For example, an exemplary cryptographically protected, distributed database-centric computer system of the present invention can be configured such that each private channel can only notify and maintain distributed ledger data related to one or more specific participants. For example, a specific portion of the distributed ledger data may exist in corresponding nodes (s) of specific participant (s) who may participate in a specific repurchase contract transaction (s). In some embodiments, and also in any combination with the embodiments described above or below, the private control can be configured such that permission can be exercised at the smallest portion (smallest unit) of the distributed ledger data.

[0053] Figure 4 shows an illustration of a workflow for obtaining a bilateral repurchase contract in an exemplary distributed ledger of the present invention.

[0054] Figure 5 shows an illustration of a workflow for evaluating collateral. Figure 5 shows that such an evaluation can be invoked by a Cron job scheduled in advance, the Cron job being set to run periodically at fixed times, dates, and / or periods. Figure 5 shows that the smart contract (SESC1) of the repurchase contract deal has been programmed to call an evaluation service, the evaluation service delivering the current value of the collateral based on the calculation of the market-to-market (MTM).

[0055] Figure 6 shows an illustration of a workflow for substituting collateral.

[0056] FIG. 7 shows an illustration of a workflow for settling an exemplary repurchase agreement.

[0057] As described in this disclosure, the SESC can be programmed to track and execute both sides of a non - liquidating bilateral repurchase agreement (repo transaction). For example, a particular EOP node participant (e.g., but not limited to, one of the parties to an exemplary repurchase agreement transaction and / or the custodian of the securities (s) provided as collateral) may set up the corresponding SESC and obtain cryptographically protected takedowns, assets, substitutes (s), and / or consideration for collateral for at least a period.

[0058] As described herein, all SESCs (e.g., SESCs in the form of smart contracts) can be configured to perform certain functions (which may include, but are not limited to, obtaining the current state of data object(s), storing the current state, and / or maintaining an audit trail of previous states). In some embodiments, and in any combination with the embodiments described above or below, all SESCs can be configured to communicate with each other and update and / or query states. For example, as described herein, a SESC called "Repo Master Agreement" can be configured to request data regarding terms and conditions and / or determine parameter values of attributes of each contract between a borrower and a lender. For example, as described herein, a SESC called "Repo" can be configured to track the transaction life cycle of a repo contract by performing actions such as, for example, obtaining transaction details, increasing an attribute (amount), maintaining a state, and / or generating a settlement instruction for settlement processing, but the actions are not limited thereto. For example, as described herein, a SESC called "Multi-Party Approval" can be configured to execute an approval process by, for example, preventing a repo contract from being recorded in the blockchain distributed ledger of the present invention until both parties agree and except when both parties agree. For example, as described herein, a SESC called "Collateral Valuation" can be configured to value all collateral using market prices, for example, by accessing market prices from one or more electronic sources (e.g., stock exchanges), but the valuation method is not limited thereto.

[0059] Example of the use of the talk of the present invention in the management of a repo contract among multiple parties

[0060] In some embodiments, and in any combination with the embodiments described above or below, an exemplary, cryptographically protected, distributed database-centric computer system may be configured to utilize Distributed Ledger Collateral Tokens (DLC Tokens). In some embodiments, and in any combination with the embodiments described above or below, an exemplary, cryptographically protected, distributed database-centric computer system may be configured to generate DLC Tokens. In some embodiments, and in any combination with the embodiments described above or below, DLC Tokens may be issued by a designated issuing authority. In some embodiments, and in any combination with the embodiments described above or below, the corresponding DLC Token(s) may be issued when a specific real-world asset(s) is locked in by a participant (e.g., a custodian). In some embodiments, and in any combination with the embodiments described above or below, the description of the present invention herein refers to an account having all real-world locked-in asset(s), which account is referred to as a Segregated Custody account (lock-up account). In some embodiments, and in any combination with the embodiments described above or below, the description of the present invention herein refers to a token issuance process, which token issuance process is referred to as the process when the corresponding DLC Token(s) are generated together with the locked asset(s). In some embodiments, and in any combination with the embodiments described above or below, the description of the present invention herein refers to a token withdrawal process, which token withdrawal process is referred to as the process of unlocking the asset in the lock-up account when the existing DLC Token(s) having the asset(s) are withdrawn from the exemplary blockchain distributed ledger of the present invention.In some embodiments, and in any combination with the embodiments described above or below, the description of the invention herein refers to a token re-collateralization setting process, which is referred to as the process when one or more participants lend borrowed DLC tokens (plural) to other participants. In some embodiments, and in any combination with the embodiments described above or below, the locking of the balance and the issuance of DLC tokens may or may not use token re-collateralization settings.

[0061] Figure 8 shows an illustration of the workflow for the issuance and settlement of DLC tokens.

[0062] Figure 9 shows an illustration of the management of digital assets and DLC token issuance of the present invention.

[0063] Figure 10 shows an illustration of the token ownership transfer of the present invention.

[0064] Figure 11 shows an illustration of the token splitting of the present invention.

[0065] Figure 12 shows an illustration of the token withdrawal of the present invention.

[0066] Figure 13 shows an illustration of the partial deletion of tokens of the present invention.

[0067] In some embodiments, and in any combination with the embodiments described above or below, as described herein, an exemplary, cryptographically protected, distributed database-centric computer system can utilize DLC tokens to minimize the quantity and frequency of balance data transfer across a computer network while achieving maximum immobilization and instant settlement.

[0068] In some embodiments, and in any combination with the embodiments described above or below, an exemplary, cryptographically protected, distributed database-centric computer system of the present disclosure may be configured to manage DLC tokens using an electronic wallet or digital wallet (e-wallet) of the present disclosure. In some embodiments, and in any combination with the embodiments described above or below, an exemplary electronic wallet of the present disclosure also has a software component and an information component. In some embodiments, and in any combination with the embodiments described above or below, security and encryption may be provided for personal information and for actual transactions. In some embodiments, and in any combination with the embodiments described above or below, an exemplary electronic wallet of the present disclosure may be stored on the client side and / or server side and be self-sustaining.

[0069] In some embodiments, and in any combination with the embodiments described above or below, an exemplary electronic wallet of the present disclosure may be configured to perform at least the following three functions. (1) Lifecycle management of a bilateral buyback contract deal (2) Asset tokenization and management (3) In-chain settlement - transfer of asset tokens (between e-wallets) in the blockchain distributed ledger of the present invention

[0070] In some embodiments, and in any combination with the embodiments described above or below, an exemplary, cryptographically protected, distributed database-centric computer system of the present disclosure may be configured such that each participant can, by using the participant's own unique identification information issued to the exemplary system of the present invention, (1) view the state within the chain (e.g., the e-wallet(s) of the asset balance issued in the blockchain distributed ledger of the present invention), and / or (2) view only the existing balance.

[0071] In some embodiments, and in any combination with the embodiments described above or below, one or more SESC (e.g., smart contracts) may be configured to track ownership transfers such that a third party (e.g., a supervisory authority) can track asset ownership. For example, the exemplary settlement API of FIG. 8 can be programmed to cause an external system or API to effect an asset ownership transfer.

[0072] For example, one or more SESC (e.g., smart contracts) may include self-executing code directed to issuance verification rules (s), which may include, for example, (1) verifying that participants in the existing books and records have segregated custody accounts; (2) verifying that the participants issuing the assets always place and transfer the balances (assets) in a segregated custody account (e.g., a locked HIC account of the EOP member node); (3) verifying that participants can only issue an amount equal to the amount of the balance locked in the segregated custody account (e.g., a locked HIC account of the EOP member node), and / or (4) verifying the identification materials and signatures of the participants but are not limited thereto. For example, one or more SESC (e.g., smart contracts) may include self-executing code directed to settlement verification conditions, which may include, for example, (1) verifying whether DLC tokens with a given CUSIP and quantity are owned by the lender party and are available for acquisition, and / or (2) verifying whether the quantity of tokens available for acquisition is greater than the required amount and that the token amount can be split into two token sub-amounts as a non-limiting example but are not limited thereto.

[0073] For example, when the settlement API of the corresponding SESC (e.g., smart contract) is instructed regarding token transfer, such a function may, for example, request the current owner, CUSIP, and new owner details and quantity details. And, for example, the settlement API of the corresponding SESC may be configured to confirm the token availability by the current owner. Subsequently, if the available token quantity is greater than the requested token quantity, the settlement API of the corresponding SESC may be configured to instruct for token splitting. For example, if the exemplary amount of DLC tokens of the requested quantity is available, the settlement API of the corresponding SESC may be configured to call the token transfer SESC (e.g., smart contract) to change the ownership. For example, finally, the token transfer consumes the existing token state and generates a new token state with a new owner.

[0074] In some embodiments, and in any combination with the embodiments described above or below, the exemplary, cryptographically protected, distributed database-centric computer system of the present disclosure may be configured to process the redemption of DLC token(s) based on, but not limited to, the following example. For example, a participant has a long position of 100 million (100M) of CUSIP X in a segregated custody account, and the corresponding node issues an equivalent amount of DLC tokens in the blockchain distributed ledger of the present invention. In fact, the participant can transfer a portion (30M) of these tokens to other participants in the blockchain of the present invention as a settlement activity for a repurchase contract. As a result, the receiving participant owns 30M tokens in the chain, whereby the participant can redeem 30M tokens and release or unlock a long position of 30M from the segregated custody account that the participant owns. For example, the corresponding SESC may be configured to send a redemption instruction corresponding to the financial system and / or the client system and invalidate the corresponding DLC token by making the corresponding DLC token inactive. For example, as part of the adjustment process between the token ownership in the blockchain distributed ledger of the present invention and the token ownership in the segregated custody account, the corresponding SESC (e.g., smart contract) may be configured to perform an adjustment to set the long position to 70M for CUSIP X.

[0075] Example of using the tokens of the present invention without using a re-guarantee setting

[0076] In some embodiments, and in any combination with the embodiments described above or below, an exemplary, cryptographically protected, distributed database-centric computer system of the present disclosure may be configured such that a related SESC (e.g., a smart contract) of the present invention manages DLC tokens using a transaction type, an asset, and a token identifier, and a re-collateralization setting of the DLC tokens is not used by a third party and / or the same counterparty. For example, a participant can only lend or transfer their own HIC balance. For example, A can lend X tokens to B for a repurchase contract deal, but B cannot lend the same X tokens to A for another repurchase contract deal, nor can B lend the X tokens to C for another repurchase contract deal. FIGS. 14-21 provide examples of various stages of the life cycle of a DLC token without a re-collateralization setting that can be managed based on the principles of the present disclosure.

[0077] Example of using the token of the present invention with a re-collateralization setting

[0078] In some embodiments, and in any combination with the embodiments described above or below, an exemplary, cryptographically protected, distributed database-centric computer system of the present disclosure may be configured such that a related SESC (e.g., a smart contract) of the present invention manages DLC tokens using a transaction type, an asset, and a token identifier, and a re-collateralization setting of the DLC tokens is available for use by a third party and / or the same counterparty. For example, an exemplary, cryptographically protected, distributed database-centric computer system of the present disclosure may be configured such that a participant can transfer any token having a CUSIP given in the blockchain ledger of the present invention. FIGS. 22-25 provide examples of various stages of the life cycle of a DLC token with a re-collateralization setting that can be managed based on the principles of the present disclosure.

[0079] Example of using the data structure of the present invention

[0080] In some embodiments, and in any combination with the foregoing or following embodiments, an exemplary, cryptographically protected, distributed database-centric computer system of the present disclosure may operate based on one or more data structures (e.g., the data structure in SESC) that incorporate a nested JSON structure. For example, an exemplary, cryptographically protected, distributed database-centric computer system of the present disclosure may include an object "Repo Trade" (repurchase agreement) in which features are programmed as a compilation of JSON objects and each feature has a corresponding JSON object. Table 1 shows an exemplification of each feature of the object "Repo Trade".

[0081]

Table 1

[0082] An exemplary, cryptographically protected, distributed database-centric computer system of the present disclosure may utilize similar objects to manage collateral and tokens. Table 2 shows an exemplification of each feature of the DLC token object.

[0083] In some embodiments, and in any combination with the embodiments described above or below, the parameter of each DLC token representing the value of the owner's identification information (e.g., the unique identifier of the participant) may be in the form of a hashed value using the private sort shown in FIG. 26. In some embodiments, and in any combination with the embodiments described above or below, only the SESC (e.g., the smart contract) can generate this unique hash. In some embodiments, and in any combination with the embodiments described above or below, the SESC (e.g., the smart contract) that does not sequentially generate the unique identifier of a specific participant can only read and identify the token ownership. Therefore, such a technical solution can anonymize the ownership information, and any party choosing to read or steal the data cannot understand the generated data (e.g., the party and account numbers).

[0084]

Table 2

[0085] In some embodiments, and in any combination with the embodiments described above or below, the plurality of SESCs include a plurality of buyback contract SESCs, and each of the buyback contract SESCs is configured at least as follows, that is, For a specific buyback contract, obtain the current buyback contract data from at least one electronic source associated with at least one EOP member node, Perform at least one explicit policy criteria check on at least one of the at least one electronic source, the at least one EOP member node, and the current buyback contract data, Obtain electronic signatures from all parties to the specific buyback contract, Generate at least one buyback contract status hash representing the current buyback contract data, Store the at least one buyback contract status hash of the specific buyback contract and the current buyback contract data in at least one buyback contract persistent data object in at least one distributed database, Hold the at least one buyback contract status hash in the buyback contract SESC, Replace at least one first collateral used in the specific buyback contract with other collateral, Generate an output representing the current state of the specific buyback contract and is configured to

[0086] In some embodiments, and in any combination with the embodiments described above or below, at least some embodiments of the present disclosure provide an exemplary system including at least a distributed blockchain environment. The distributed blockchain environment includes (i) a plurality of externally owned presence (EOP) member nodes associated with a plurality of distributed entities, each including one or more computers associated with at least one distributed entity, (ii) one or more cryptographically protected distributed ledgers storing a plurality of persistent data objects across one or more computers of the EOP member nodes, (iii) a plurality of electronic wallets (e-wallets) configured to hold data records of one or more distributed ledger collateral (DLC) tokens, wherein the computers of the EOP member nodes are configured to manage corresponding one or more of the plurality of electronic wallets, (iv) a plurality of self - contained autonomous execution software containers (SESCs), (1) one or more first - type SESCs, where each first - type SESC (a) Generate a plurality of persistent SESC data objects, where the persistent SESC data objects store distributed data items of at least one transaction among a plurality of entities in one or more cryptographically protected distributed ledgers, and at least one transaction includes one or more assets. (b) Update the distributed data items of at least one transaction in one or more corresponding persistent SESC data objects. A plurality of persistent software routines configured as above, one or more SESCs of the first type, and (2) One or more SESCs of the second type, where each of the one or more SESCs of the second type includes one or more persistent task-specific software routines. The persistent task-specific software routines are called by one or more persistent software routines of the first type of SESC and are configured to update one or more corresponding distributed data items of at least one transaction based on each corresponding task executed by one or more persistent software routines of the first type of SESC having one or more corresponding distributed data items. One or more SESCs of the second type. (3) One or more SESCs of the third type, where each of the one or more SESCs of the third type includes one or more persistent token-specific software routines. The persistent token-specific software routines are configured to manage DLC tokens in a distributed blockchain environment. The DLC tokens are used by the distributed blockchain environment to substitute one or more first assets of at least one first party in at least one transaction for one or more second assets of at least one second party in at least one transaction. One or more SESCs of the third type. A plurality of SESCs including. One or more SESCs of the first type, one or more SESCs of the second type, and one or more SESCs of the third type are distributed SESCs. Each DLC token includes at least one unique entity identification cryptographic hash. For each corresponding transaction associated with a corresponding EOP member node, one or more computers of the corresponding EOP member node are configured to call (i) one or more first-type SESCs and (ii) one or more third-type SESCs to cryptographically manage each corresponding transaction in a distributed blockchain environment.

[0087] In some embodiments, and in any combination with the embodiments described above or below, at least some embodiments of the present disclosure provide exemplary methods. The exemplary method includes managing, by one or more computers, a plurality of externally-owned presence (EOP) member nodes associated with a plurality of distributed entities; managing, by one or more computers, one or more cryptographically protected distributed ledgers and storing a plurality of persistent data objects across a distributed blockchain environment of the EOP member nodes; managing, by one or more computers, a plurality of electronic wallets (e-wallets) configured to hold data records of one or more distributed ledger collateral (DLC) tokens; managing, by one or more computers, a plurality of self-contained, self-executing software containers (SESCs), the plurality of SESCs including (1) one or more first-type SESCs, each first-type SESC including (a) generating a plurality of persistent SESC data objects, the persistent SESC data objects storing distributed data items of at least one transaction among a plurality of entities in one or more cryptographically protected distributed ledgers, the at least one transaction including one or more assets; (b) updating distributed data items of at least one transaction in one or more corresponding persistent SESC data objects; one or more first-type SESCs including a plurality of persistent software routines configured as such; (2) One or more SESC of the second type, where each of the one or more SESC of the second type includes one or more persistent task-specific software routines. The persistent task-specific software routines are called by one or more persistent software routines of the first type of SESC and are configured to update one or more corresponding distributed data items of at least one transaction based on each corresponding task executed by one or more persistent software routines of the first type of SESC having one or more corresponding distributed data items, one or more SESC of the second type; (3) One or more SESC of the third type, where each of the one or more SESC of the third type includes one or more persistent token-specific software routines. The persistent token-specific software routines are configured to manage DLC tokens in a distributed blockchain environment. The DLC tokens are used by the distributed blockchain environment to substitute for one or more first assets of at least one first party in at least one transaction with one or more second assets of at least one second party in at least one transaction, one or more SESC of the third type; Managing a plurality of SESC including; Managing corresponding transactions in a distributed blockchain environment by one or more computers in response to one or more SESC of the first type and one or more SESC of the third type called by corresponding EOP member nodes. One or more SESC of the first type, one or more SESC of the second type, and one or more SESC of the third type are distributed SESC; Each DLC token includes at least one unique entity identification cryptographic hash.

[0088] In some embodiments, and in any combination with the embodiments described above or below, one or more SESC of the third type are (i) Generate corresponding amounts of DLC tokens associated with one or more first assets and one or more second assets respectively, (ii) It is configured to store the corresponding amounts of DLC tokens in the corresponding digital wallets of at least one first party and at least one second party.

[0089] In some embodiments, and in any combination with the embodiments described above or below, for at least one transaction, a plurality of persistent software routines of one or more first types of SESC call one or more third types of SESC and are configured to lock at least a portion of each corresponding amount of the DLC tokens in the corresponding digital wallet to form corresponding locked DLC tokens.

[0090] In some embodiments, and in any combination with the embodiments described above or below, a plurality of persistent software routines of one or more first types of SESC (i) Call one or more third types of SESC to substitute one or more first assets of at least one first party in at least one transaction with one or more second assets of at least one second party in at least one transaction, and transfer the corresponding locked DLC tokens between the corresponding digital wallets, (ii) Cryptographically record the substitution in one or more persistent SESC data objects associated with at least one transaction as configured.

[0091] In some embodiments, and in any combination with the embodiments described above or below, at least one transaction is an asset repurchase transaction.

[0092] In some embodiments, and in any combination with the embodiments described above or below, one or more first assets of at least one first party and one or more second assets of at least one second party are collateral assets in an asset buy-back transaction.

[0093] In some embodiments, and in any combination with the embodiments described above or below, one or more first assets of at least one first party and one or more second assets of at least one second party are distributed-type assets.

[0094] In some embodiments, and in any combination with the embodiments described above or below, one or more first assets of at least one first party and one or more second assets of at least one second party are distributed-type assets.

[0095] In some embodiments, and in any combination with the embodiments described above or below, one or more first assets of at least one first party and one or more second assets of at least one second party are stored in the corresponding custodian account of the corresponding EOP member node.

[0096] In some embodiments, and in any combination with the embodiments described above or below, the corresponding digital wallets of at least one first party and at least one second party include the corresponding custodian account.

[0097] In some embodiments, and in any combination with the embodiments described above or below, one or more third-type SESCs (i) generate corresponding-amount DLC tokens associated with one or more first assets and one or more second assets respectively, (ii) configured to store the corresponding DLC tokens of the corresponding amounts in the corresponding digital wallets of at least one first party and at least one second party.

[0098] In some embodiments, and in any combination with the embodiments described above or below, the first digital wallet of at least one first party, the second digital wallet of at least one second party, or the first digital wallet and the second digital wallet store one or more corresponding amount DLC tokens received in at least one other transaction with at least one third party.

[0099] In some embodiments, and in any combination with the embodiments described above or below, when at least one other transaction is conducted between at least one first party and at least one second party, at least one third party is one of at least one first party or at least one second party.

[0100] Although several embodiments of the present invention have been described, these embodiments are merely illustrative and thus not limiting, and it is understood that many modifications may be apparent to those skilled in the art. Further, the various steps may be performed in any desired order (and any desired step may be added and / or any desired step may be omitted).

Claims

1. A system comprising a distributed blockchain environment, wherein the distributed blockchain environment comprises (i) a plurality of externally-owned presence (EOP) member nodes associated with a plurality of distributed entities, each including one or more computers associated with at least one distributed entity, (ii) one or more cryptographically protected distributed ledgers storing a plurality of data objects across the one or more computers of the EOP member nodes, (iii) a plurality of data records associated with a plurality of distributed ledger collateral (DLC) tokens, wherein the computers of the EOP member nodes are configured to store corresponding one or more of the plurality of data records, (iv) a plurality of self-contained autonomous execution software containers (SESCS), (1) one or more SESCS of a first type, (a) generating a plurality of persistent data objects in one or more cryptographically protected distributed ledgers, the persistent data objects storing distributed data items of at least one transaction between a plurality of entities in the one or more cryptographically protected distributed ledgers, the at least one transaction including one or more assets, (b) updating the distributed data items of the at least one transaction in the one or more corresponding persistent data objects, the one or more SESCS of the first type including a plurality of persistent software routines configured to perform the above, (2) one or more SESCS of a second type including one or more task-specific software routines, the task-specific software routines being configured to update one or more corresponding distributed data items of the at least one transaction based on each corresponding task executed by one or more persistent software routines of the SESCS of the first type having the one or more corresponding distributed data objects. (3) One or more third - type SESCs including one or more token - specific software routines, wherein the token - specific software routines are configured to divide the DLC token in the distributed blockchain environment, and the DLC token is used by the distributed blockchain environment to substitute one or more first - type assets of at least one first party in the at least one transaction for one or more second - type assets of at least one second party in the at least one transaction, the one or more third - type SESCs; The plurality of SESCs including; including; The one or more first - type SESCs, the one or more second - type SESCs, and the one or more third - type SESCs are distributed SESCs; Each of the DLC tokens includes at least one unique entity - identifying cryptographic hash; For each corresponding transaction associated with the corresponding EOP member node, the one or more computers of the corresponding EOP member node are configured to call (i) the one or more first - type SESCs and (ii) the one or more third - type SESCs. A system.

2. The one or more third - type SESCs are; (i) Generating the DLC tokens of corresponding amounts respectively associated with the one or more first - type assets and the one or more second - type assets; (ii) Storing the DLC tokens of the corresponding amounts in the corresponding data records of the at least one first party and the at least one second party; The system according to claim 1, including.

3. For the at least one transaction, the plurality of persistent software routines of the one or more first - type SESCs are configured to call the one or more third - type SESCs and lock at least a part of each corresponding amount of the DLC tokens in the corresponding data records to form corresponding locked DLC tokens. The system according to claim 2.

4. The plurality of persistent software routines of the one or more first - type SESCs are; (i) Call the one or more SESC of the third type so that the one or more first assets of the at least one first party in the at least one transaction are used as an alternative to the one or more second assets of at least the one second party in the at least one transaction, transfer the corresponding locked DLC token during the corresponding data recording, (ii) Cryptographically record the substitution in one or more persistent SESC data objects associated with the at least one transaction The system according to claim 3, which is configured as described above.

5. The system according to claim 1, wherein the at least one transaction is an asset repurchase transaction.

6. The system according to claim 5, wherein the one or more first assets of the at least one first party and the one or more second assets of the at least one second party are collateral assets in the asset repurchase transaction.

7. The system according to claim 1, wherein the one or more first assets of the at least one first party and the one or more second assets of the at least one second party are distributed types of assets.

8. The system according to claim 6, wherein the one or more first assets of the at least one first party and the one or more second assets of the at least one second party are distributed types of assets.

9. The system according to claim 2, wherein the one or more first assets of the at least one first party and the one or more second assets of the at least one second party are stored in corresponding custody accounts of corresponding EOP member nodes.

10. The system according to claim 9, wherein the corresponding data records of the at least one first party and the at least one second party include the corresponding custody accounts.

11. When the one or more SESC of the third type are called by the one or more computers, (i) Generate the DLC tokens of the corresponding amounts respectively associated with the one or more first assets and the one or more second assets, (ii)The system according to claim 1, wherein the DLC tokens of the corresponding amounts are stored in the corresponding data records of the at least one first party and the at least one second party.

12. The system according to claim 1, wherein the first data record of the at least one first party, the second data record of the at least one second party, or the first data record and the second data record store the DLC tokens of one or more corresponding amounts received in at least one other transaction with at least one third party.

13. The system according to claim 12, wherein when the at least one other transaction is performed between the at least one first party and the at least one second party, the at least one third party is one of the at least one first party or the at least one second party.

14. Managing one or more cryptographically protected distributed ledgers by one or more computers associated with a plurality of externally owned presence (EOP) member nodes associated with a plurality of distributed entities, wherein the one or more cryptographically protected distributed ledgers store a plurality of data objects and a plurality of data records associated with distributed ledger collateral (DLC) tokens; By the one or more computers, (a) generating a plurality of persistent SESC data objects, the persistent SESC data objects storing distributed data items of at least one transaction between a plurality of entities in the one or more cryptographically protected distributed ledgers, the at least one transaction including one or more assets; (b) updating the distributed data items of the at least one transaction in one or more corresponding persistent SESC data objects such that a plurality of transaction-specific software routines of one or more first types of SESC are executed. Executing, by the one or more computers, one or more task-specific software routines of one or more second-type SESCs to update one or more corresponding distributed data items of the at least one transaction based on each corresponding task executed by one or more persistent software routines of the first-type SESCs having the one or more corresponding distributed data items; Executing, by the one or more computers, one or more persistent token-specific software routines of one or more third-type SESCs to split the DLC token in a distributed blockchain environment, wherein the DLC token is utilized to substitute one or more first assets of at least one first party in the at least one transaction for one or more second assets of at least one second party in the at least one transaction; comprising; the one or more first-type SESCs, the one or more second-type SESCs, and the one or more third-type SESCs are distributed SESCs; each said DLC token includes at least one unique entity identification cryptographic hash, a method.

15. The one or more third-type SESCs are (i) generating the DLC token of a corresponding amount associated with each of the one or more first assets and the one or more second assets, (ii) storing the DLC token of the corresponding amount in the corresponding data records of the at least one first party and the at least one second party configured as such, the method according to claim 14.

16. For the at least one transaction, the one or more persistent software routines of the one or more first-type SESCs are configured to call the one or more third-type SESCs and lock at least a portion of each corresponding amount of the DLC token in the corresponding data record to form a corresponding locked DLC token, the method according to claim 15.

17. The one or more persistent software routines of the one or more first type of SESCs are (i) calling the one or more third type of SESCs to substitute the one or more first assets of the at least one first party in the at least one transaction with the one or more second assets of at least the one second party in the at least one transaction, and transferring the corresponding locked DLC token during the corresponding data recording, (ii) cryptographically recording the substitution in one or more persistent SESC data objects associated with the at least one transaction The method according to claim 16, which is configured as described above. **Claim 18** The method according to claim 14, wherein the at least one transaction is an asset repurchase transaction. **Claim 19** The method according to claim 18, wherein the one or more first assets of the at least one first party and the one or more second assets of the at least one second party are collateral assets in the asset repurchase transaction. **Claim 20** The method according to claim 14, wherein the one or more first assets of the at least one first party and the one or more second assets of the at least one second party are distributed type assets. **Claim 21** The method according to claim 19, wherein the one or more first assets of the at least one first party and the one or more second assets of the at least one second party are distributed type assets. **Claim 22** The method according to claim 15, wherein the one or more first assets of the at least one first party and the one or more second assets of the at least one second party are stored in corresponding custody accounts of corresponding EOP member nodes. **Claim 23** The method according to claim 22, wherein the corresponding data records of the at least one first party and the at least one second party include the corresponding custody accounts. **Claim 24** The one or more third type of SESCs are (i) generating the DLC tokens of corresponding amounts respectively associated with the one or more first assets and the one or more second assets, (ii) storing the DLC tokens of the corresponding amounts in the corresponding data records of the at least one first party and the at least one second party The method according to claim 14, wherein it is configured as such.

25. The method according to claim 14, wherein the first data record of the at least one first party, the second data record of the at least one second party, or the first data record and the second data record store the DLC tokens of one or more corresponding amounts received in at least one other transaction with at least one third party.

26. The method according to claim 25, wherein when the at least one other transaction is conducted between the at least one first party and the at least one second party, the at least one third party is one of the at least one first party or the at least one second party.

Images